linux/poky.git/meta/conf/bitbake.conf, branch halstead/hashclient

bitbake.conf: remove comment about oldincludedir

2024-04-12T16:36:52+00:00

oldincludedir was removed by 506c91cbc6a604a84e37e53ccff430436369802e (From OE-Core rev: 0228ab43e9b659771f4f59944897aec6879f8209) Signed-off-by: Peter Marko Signed-off-by: Richard Purdie

archiver.bbclass: Drop tarfile module to improve performance

2023-12-23T08:46:01+00:00

* The tarfile module doesn't support xz options or environment varible XZ_DEFAULTS, this makes do_ar_patched incrediblely slow when the file is large, for example, chromium-x11 is about 3GB: - "bitbake chromium-x11 -car_patched" hasn't been done after 3 hours on my host, I checked the partial tar.xz file is only 1.5GB, so maybe more than 6 hours is required to complete the task. - Now only less than 4 minutes is needed on the same host. * Need add xz to HOSTTOOLS when archiver.bbclass is enabled and compression is xz. (From OE-Core rev: 6548354f049b173e8d443bc547d35c9d9fc05259) Signed-off-by: Robert Yang Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

nativesdk: don't unset MACHINE_FEATURES, let machine-sdk/ set it

2023-12-23T08:46:00+00:00

There is actually a use for nativesdk MACHINE_FEATURES; for example qemu-usermode being supported, as this is needed to build profile-guided optimised code. We shouldn't use the target MACHINE_FEATURES for this because the target and the SDK can be entirely different, so instead set the MACHINE_FEATURES in nativesdk.bbclass to SDK_MACHINE_FEATURES (which defaults to "") and let the conf/machine-sdk/*.conf files set that as appropriate. (From OE-Core rev: 14571764b7e046507f81bbe589a9f42c5b16665a) Signed-off-by: Ross Burton Link: https://lore.kernel.org/r/20231221170159.1995650-2-ross.burton@arm.com Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

ipk: Switch to using zstd compression

2023-12-23T08:46:00+00:00

Converts IPK package generation to use zstd instead of xz. zstd has a much larger compression/speed tradeoff range allowing users to choose what suits them best, and fast decompression speeds. It also continues to support parallel compression as xz did. A new variable called ZSTD_DEFAULTS is provided to set the defaults for places that want to use zstd for compression; the zst image conversion command is also modified to use this. Finally, in order for this to function properly, opkg must include zstd support, so it is enabled all the time with no PACKAGECONFIG to turn it off. (From OE-Core rev: 1bc3e9bbaa670b6128c74c76b4b5264e60ce3463) Signed-off-by: Joshua Watt Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

bitbake.conf: Add runtimedir

2023-12-20T07:47:00+00:00

Adds the path to the runtime state directory (/run). In particular, systemd units need to have the correct path to the runtime directory because RequiresMountsFor doesn't follow symbolic links. This means that if a unit calls out a directory in /var/run (a symbolic link to /run), it may actually start before /run is mounted. The fix is to have the unit specify a directory in /run instead. (From OE-Core rev: 90bc18108230f6d41a50cebc8348444e119e95bf) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie

bitbake.conf: Add gsutil as hosttool for gcp fetcher.

2023-12-02T17:18:57+00:00

The gcp fetcher uses gsutil to check if the file exists before fetching. This change ensures the tool is included as a nonfatal hosttool so that it's included in the build environment when available. (From OE-Core rev: d5e481bbd96210e608fa0aa5f7b54c1398c7d273) Signed-off-by: Charlie Johnston Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

bitbake.conf: Log events by default using BB_DEFAULT_EVENTLOG

2023-11-23T12:12:00+00:00

By setting this, event data from during the build is saved out. This can be used for analytic including toaster to allow builds to be examined later. This will use some disk space but it is worth it for the ability to look into what happened during the build. Users can set the value to something else in local.conf to override if they wish. (From OE-Core rev: 4719b68bb9e3cccb85aed55350e53a439360abcb) Signed-off-by: Richard Purdie

bitbake.conf: drop ${PE} and ${PR} from -f{file,macro,debug}-prefix-map

2023-11-20T15:30:52+00:00

* ${EXTENDPE} and ${PR} was already dropped from ${WORKDIR} in: https://lists.openembedded.org/g/openembedded-core/message/185818 adjust -fmacro-prefix-map and -fdebug-prefix-map similarly. As we don't depend on PR in WORKDIR maybe we don't need it in /usr/src/debug paths as well anymore. * add TARGET_DBGSRC_DIR variable with "/usr/src/debug/${PN}/${PV}" because there is quite a few places where this location is being used in various recipes * The interesting side-effect of this is that for DISTROs which still use PR (e.g. webOS OSE), the difference in -fdebug-prefix-map causes all binaries to be slightly different when rebuilt with different PR (due to this path, even when otherwise they are binary reproducible) and when the number of digits in PR changes (e.g. from r9 to r10) it also results in slightly bigger binaries (and more unnecessary changes in buildhistory diffs). For example this foo binary, the difference between "new" and "old" is extra patch applied in SRC_URI (which doesn't affect the foo binary, but was the reason for PR bump). And the binary is bigger with r10, identical with r6 and slightly different due to debug-prefix-map between r6 and r7: $ ls -la 1.0.0-175-*/image/usr/sbin/foo -rwxr-xr-x 1 bitbake bitbake 30182460 Nov 8 08:29 1.0.0-175-new-r10/image/usr/sbin/foo -rwxr-xr-x 1 bitbake bitbake 30182224 Nov 8 08:02 1.0.0-175-new-r6/image/usr/sbin/foo -rwxr-xr-x 1 bitbake bitbake 30182224 Nov 8 07:49 1.0.0-175-new-r7/image/usr/sbin/foo -rwxr-xr-x 1 bitbake bitbake 30182224 Nov 8 07:39 1.0.0-175-old-r6/image/usr/sbin/foo $ md5sum 1.0.0-175-*/image/usr/sbin/foo 8e3ab67d596f8cc2f9c6320dab10af01 1.0.0-175-new-r10/image/usr/sbin/foo f6ff1e64fe6affb9ba0d8f278cf7ed79 1.0.0-175-new-r6/image/usr/sbin/foo 6469a0b10aac233911e63c5ea97b03c0 1.0.0-175-new-r7/image/usr/sbin/foo f6ff1e64fe6affb9ba0d8f278cf7ed79 1.0.0-175-old-r6/image/usr/sbin/foo (From OE-Core rev: c84c8ba295eeaa0e0b7592364b0978f17a44c70b) Signed-off-by: Martin Jansa Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

bitbake.conf: Drop oldincludedir

2023-11-20T15:30:52+00:00

Autoconf defines this as: "The directory for installing C header files for non-GCC compilers." Whilst this is something autoconf does allow changing, I find it hard to believe it has much use in the wild now and that headers don't get split like this in reality, it would probably only be useful on really old unixes.. The values are the same in our configuration anyway. Drop the value and just use includedir everywhere. (From OE-Core rev: 506c91cbc6a604a84e37e53ccff430436369802e) Signed-off-by: Richard Purdie Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

bitbake.conf: remove ${CCACHE} from FORTRAN compiler

2023-10-30T08:50:46+00:00

ccache used to support FORTRAN (versions 3.3-3.6) but no longer does (From OE-Core rev: 0cc2c0a9ec16fceeb19e01cd47af8c0743168030) Signed-off-by: david d zuhn Signed-off-by: Richard Purdie