Skip to content

style(doc): bitbake fix doc and release note #517

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 27, 2022
Merged

style(doc): bitbake fix doc and release note #517

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e6fd2e5
style(doc): bitbake fix doc and release note
stevebillings Jan 25, 2022
44eae26
Merge branch 'sb_bitbakeMultiLayerRecipes' into docForIDETECT-2925
stevebillings Jan 27, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/markdown/packagemgrs/bitbake.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,10 +17,10 @@ script (by default: oe-init-build-env), and executes BitBake commands to collect
The BitBake detector generates one codelocation for each given package (target image) name by performing the following steps:
1. Determines the build directory path by sourcing the given build environment setup script and determining the resulting working directory.
1. Runs 'bitbake --environment' to determine the currently-configured target machine architecture and licenses directory path.
1. Runs 'bitbake-layers show-recipes' to derive the list of layers and collect recipe layer information.
1. For each given package (target image) name:
* If the user requested that build dependencies be excluded, [solution_name] locates and reads the license.manifest file for the given package (target image) and the currently-configured target machine architecture. This provides a list of recipes that are included in the target image (the non-build dependencies).
* Runs 'bitbake -g {package}' to generate task-depends.dot, and reads recipes and dependency relationships from it.
* Runs 'bitbake-layers show-recipes' to derive each recipe's layer. The first layer listed for each recipe is used as the layer field of the KB externalID [solution_name] generates for the recipe.
* If the user requested that build dependencies be excluded: [solution_name] excludes recipes not declared in license.manifest, as well as native recipes. [solution_name] always excludes virtual recipes (recipes with names prefixed with "virtual/").
* [solution_name] adds at the root level of the graph for the package (target image) each recipe found in task-depends.dot that is not excluded as described above.
* Child (transitive) relationships are created from those root dependencies to their children (as specified in task-depends.dot).
Expand Down
3 changes: 3 additions & 0 deletions docs/markdown/releasenotes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,9 @@
* The Go Mod Cli Detector no longer uses the "-u" flag when running **go list -m all**. This results in significantly faster scan times against Go Mod projects.
* Deprecated the `detect.pnpm.dependency.types` property in favor of `detect.pnpm.dependency.types.excluded` for property consistency.

### Resolved issues
* (IDETECT-2925) Resolved an issue that could cause the Bitbake detector to incorrectly identify the layer of a dependency recipe.

## Version 7.10.0

### New features
Expand Down