rust-embedded / rust-embedded/meta-rust-bin

meta-rust-bin prepends itself to BBPATH

Open
#205 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
BitBake
Stars
124
Forks
92
Avg merge
6h 54m
Merged PRs (30d)
2

Description

I noticed this while trying to mitigate #204. The current conf/layer.conf has the following line:

BBPATH =. "${LAYERDIR}:"

According to the BitBake documentation =. means to prepend a string without a space. Meaning that meta-rust-bin puts itself in front of other layers, even though the user may have ordered these layers differently.

Yocto still has no proper mechanism to patch/override .bbclass files, so we're stuck having to create a layer and put it at the top of bblayers.conf. https://yocto.yoctoproject.narkive.com/qcV9UXm4/overriding-a-class-in-custom-layer

Looking at previous issues, this seems to have been done in order to get things working for Honister: https://github.com/rust-embedded/meta-rust-bin/issues/108. https://github.com/rust-embedded/meta-rust-bin/pull/123

Would it be possible to change things back to the default BitBake has for layer.conf files?

BBPATH .= ":${LAYERDIR}"

https://docs.yoctoproject.org/5.1.2/bsp-guide/bsp.html#layer-configuration-file

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with conf/layer.conf and inspect the BBPATH assignment discussed in the issue, then compare it with BitBake's documented layer configuration behavior. Done means the layer no longer prepends itself to BBPATH and follows the default append form; no test or additional entry point is named.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
build-system
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.