bitbake tool

I found a problem where using "%" in the PREFERRED_VERSION field sometimes product unexpected behavior. I expected this to always find the latest version of the package in the "%" range, but this did not always happen. So, to improve this, I added this code to ensure that the "%" range consistently found the latest version that matched the search criteria.

Same issue can be found here: https://patchwork.openembedded.org/patch/108877/

Quote:

I have two recipes within a single layer:

stblinux_3.14-1.7.bb stblinux_3.14-1.8.bb

If PREFERRED_VERSION_stblinux is set to "3.14%", then I would expect the version 3.14-1.8 recipe to be selected, however 3.14-1.7 gets selected instead.

Reversing the order of files stored in pkg_pn[pn] seems to help. Is it a reasonable solution?

I took a different way to solve the issue so that there should be no side effects.

Use Open Embedded environment variable BUILDDIR (if set) to extend the search path and locate f.e. bblayers.conf even if current working

directory is outside of build directory.

There might be a reason why this is a bad idea; I originally only wanted to start a discussion if this could be changed the way I did. I never really could figure out why the current working directory must be within the build directory (for Yocto or Open Embedded sourcing oe-init-build-env should be enough in my opinion) but I only started using it a few weeks ago... Is there a reason why issue-tracking is disabled and could you add some README file to point out how to contribute o this project and where to file issues (or send me a short e-Mail with this information and I write it down...).

I found several issues in the documentation. The following bugs are fixed with this pull request:

Bugfixes

• Fixed a mixture of DocBook 4 and DocBook 5. You don't need the DocBook 5 namespace inside DB4 documents

• Used throughout the document version 4.5. This is the latest release and there is no reason to use the very old 4.2 anymore. Version 4.5 is backward compatible with 4.2.

• Moved XInclude namespace from root element into the xi:include element itself. Avoids validation errors.

• Added several missing para elements inside note and tip elements. You can't start text with note, you always need a para element.

• Checked validation with the following command:

  $ xmllint --noout --xinclude --postvalid doc/bitbake-user-manual/bitbake-user-manual.xml
  

Recommendations

I would recommend several other things which is not covered with this pull request (as it may be further discussion):

• Use screen or programlisting instead of literallayout. The latter is more useful for lyrics instead of text for computer inputs and outputs.
• Don't indent the content of literallayout. This is a bad idea as indendation can be added by stylesheets. Always start at column one.
• Don't mix block element and inline elements. The para element should only contain text and inline elements (like filename or links). Block elements like lists, admonitions, etc. should be placed outside of para.
• Use option for options. :grin:
• Always(!) validate your document with the above command to avoid any rendering issues.

Have fun!

While trying to cross-compile a few nodejs projects devtool broke badly when encountering projects with @-signs in the project name. This work-around solved it for me, at least - devtool broke badly when pulling in a long number of npm-dependencies, the cause was this project:

devtool add "npm://registry.npmjs.org;name=@types/sleep;version=0.0.7"

Added a new repo Fetcher section in the same spirit as the existing sections for other supported fetchers. Changes included the new section, removal of the bulleted item that mentioned this fetcher as an "additional" fetcher, and the creation of a new variable in the glossary named REPODIR.

Signed-off-by: Nicolas Cornu [email protected]

I could apply the label "release_1.0" to a super project that contains many sub projects. If my recipes have SRC_URI's that use that label but grab different sub-folders, than there's a bug where the cached localfile (tar.gz) will not be unique and reused at the wrong times.

SRC_URI = "p4://perforce::1234@//depot/SuperProject/MiniProjectAAA/...;label=release_1.0
p4://perforce::1234@//depot/SuperProject/MiniProjectBBB/...;label=release_1.0"

This change fixes the problem with output which ends only with '\r' instead of "\r\n" or "\n". Such case I found for S3 fetcher and its aws-cli output for "cp" command: https://github.com/aws/aws-cli/blob/develop/awscli/customizations/s3/results.py#L520

when network is unstable, bitbake do_fetch will throw an error and stop the whole project building, it will waste a lot of time when the network is bad, so add retry mechanism in runfetchcmd to make project building more stable.