Bug 12023

Summary: "bitbake-layers show-layers" doesn't show layer if it doesn't append itself to BBFILE_COLLECTIONS
Product: [Build System, Metadata & Runtime] BitBake Reporter: caio.oliveira
Component: bitbakeAssignee: Unassigned <unassigned>
Status: RESOLVED NOTABUG QA Contact:
Severity: minor    
Priority: Medium+ CC: caio.oliveira, jay.shen.teoh, mshah, poky.bs.watcher, poky.watcher, randy.macleod, rebecca.swee.fun.chang
Version: unspecified   
Target Milestone: 3.4 M3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know

Description caio.oliveira 2017-08-31 23:45:31 UTC
If I create a layer with recipes, but without adding BBFILE_COLLECTIONS (and a corresponding BBFILE_PATTERN_name), bitbake -s shows the recipes as expected, but "bitbake-layers show-layers" do not show the layers. "bitbake show-recipes" shows the recipes but with a layer as "?".

I'm a bit unsure whether this is expected behavior or not.

Tested with git at "main: Attempt to gain bitbake.lock rather than just waiting" 8a60106c6f7d586c793b965c5e9460b6016fab15.
Comment 1 Rebecca Chang 2017-10-31 06:27:12 UTC
(In reply to comment #0)
> If I create a layer with recipes, but without adding BBFILE_COLLECTIONS (and
> a corresponding BBFILE_PATTERN_name), bitbake -s shows the recipes as
> expected, but "bitbake-layers show-layers" do not show the layers. "bitbake
> show-recipes" shows the recipes but with a layer as "?".
> 
> I'm a bit unsure whether this is expected behavior or not.
> 
> Tested with git at "main: Attempt to gain bitbake.lock rather than just
> waiting" 8a60106c6f7d586c793b965c5e9460b6016fab15.

Ideally, it is recommended to use bitbake-layers command to create a layer. It will help you to populate all the required configurations that you will need in your meta layer layer.conf file.
Comment 2 mshah 2021-04-08 05:16:26 UTC
Is there any work to do for this bug?

-- Milan Shah
Comment 3 Teoh Jay Shen 2021-08-17 04:05:56 UTC
Seems like there's no workaround for this issue. Developers are recommended to use bitbake-layers command to create a new layer with a basic directory structure to avoid any unexpected behavior.