linux/poky.git/meta/classes/icecc.bbclass, branch master

classes/recipes-devtools: Drop icecc from OE-Core

2025-06-05T10:02:22+00:00

There are reports this class has been broken since mickledore which suggests there are limited numbers of users. It doesn't have any automated testing and it would be hard to setup and maintain a testing environment for it. The original users/manintainers aren't using it now. For those reasons, drop from OE-Core as we're not in a good position to maintain it. I'd suggest anyone wanting to use it creates a dedicated layer with maintainers who are in a position to test/develop it appropriately since it is standalone code. (From OE-Core rev: ecf8c386cf83ea235bdc4ee0da6671a395a4c358) Signed-off-by: Richard Purdie

icecc: don't use KERNEL_CC during set_icecc_env

2024-12-13T12:26:01+00:00

The KERNEL_CC variable usage was introduced by commit d2fcaeb153fd ("icecc: Don't generate recipe-sysroot symlinks at recipe-parsing time, 2018-12-20") and is set once a recipe pulls the kernel-arch.bbclass. There are a few packages, e.g. u-boot, barebox, devicetree, perf which pull this class and for such packages the get_cross_kernel_cc() return None because icecc_is_kernel() fail. Fix this for now by replacing the KERNEL_CC check with the icecc_is_kernel() helper, which is also used by the get_cross_kernel_cc(). That said it's still not very robust to determine a compiler based on a variable or inherited class but at least it fixes the issue for now. (From OE-Core rev: 5e3c6a6384fcdc4a2269172012caae14e5f327ca) Signed-off-by: Marco Felsch Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

icecc: convert set_icecc_env to python prefuncs

2024-12-13T12:26:01+00:00

Since bitbake commit f24bbaaddb36 ("data: Add support for new BB_HASH_CODEPARSER_VALS for cache optimisation") the icecc fails with [1]: ERROR: /Yocto/poky/meta/recipes-core/meta/target-sdk-provides-dummy.bb: no-pn NULL prefix WARNING: /Yocto/poky/meta/recipes-core/meta/target-sdk-provides-dummy.bb: Exception during build_dependencies for set_icecc_env The reason for this is the bb.fatal() within the icecc_version(). icecc_version() is called during the "${@}" python variable expansion while bitbake is running the build_dependencies() for the set_icecc_env() function. To avoid this behaviour set_icecc_env() should be converted into a python function which gets called during task[prefuncs] [2], which is done by this commit. [1] https://lists.yoctoproject.org/g/yocto/topic/icecc_support_broken/103429714 [2] https://lists.openembedded.org/g/openembedded-core/topic/110009272 (From OE-Core rev: 444445c5793aaf831ff0293b62a000f8ab7d40bb) Signed-off-by: Marco Felsch Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

icecc: enable the network only when ICECC_DISABLED is not set

2023-02-24T17:05:24+00:00

Enabling the network uncondictional is not need for some use cases. Such use case is usefull to reuse the sstate-cache of the build and it requires the icecc inherit in all of the builds. The real control control of the icecc is in the variable ICECC_DISABLED so this patch change the logic to enable the network when the icecc is in use. (From OE-Core rev: 0fd3a9c13a30a67ccef6619627efd9613755a0c3) Signed-off-by: Jose Quaresma Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

icecc.bbclass: fix filename of recipe in comment

2022-09-17T06:47:07+00:00

The character '%' is not a valid part of a recipe filename and has been used here only to suggest a wildcard regarding the recipe's version, see reply [1] in a companioned thread. Correct that by using the current recipe version instead. [1] https://lists.yoctoproject.org/g/docs/message/3165 (From OE-Core rev: cf8835b53cb5ce3ff13f97fcf2d22b97a9f1ede4) Signed-off-by: Ulrich Ölmann Signed-off-by: Richard Purdie

icecc.bbclass: delete 'rm' command

2022-09-07T20:28:41+00:00

The removed command was explicitly marked as transitional in commit [1] roughly three years ago, so finally clean up. [1] 40d74cb1d0dd ("icecc: Export ICECC_CC and friends via wrapper-script") (From OE-Core rev: 4459e970c7c1c43f4061b1cb6229d7a3643e1bbc) Signed-off-by: Ulrich Ölmann Signed-off-by: Richard Purdie

icecc.bbclass: fix typos

2022-09-07T20:28:41+00:00

(From OE-Core rev: 7fd33565df5dfaa962bcafd842162a2f504c59e7) Signed-off-by: Ulrich Ölmann Signed-off-by: Richard Purdie

classes: Add SPDX license identifiers

2022-08-12T10:58:01+00:00

As stated in our top level license files, the license is MIT unless otherwise stated. Add SPDX identifers accordingly. Replace older license statementa with the standardised syntax. Also drop "All Rights Reserved" expression as it isn't used now, doesn't mean anything and is confusing. (From OE-Core rev: 081a391fe09a21265881e39a2a496e4e10b4f80b) Signed-off-by: Richard Purdie

classes: Add copyright statements to files without one

2022-08-12T10:58:01+00:00

Where there isn't a copyright statement, add one to make it explicit. Also drop editor config lines where they were present. (From OE-Core rev: 880c1ea3edc8edef974e65b2d424fc36809ea034) Signed-off-by: Richard Purdie

icecc.bbclass: enable networking in all tasks

2022-03-02T18:43:24+00:00

The icecc.bbclass needs network access to work properly. Currently I build with icecc inside a container with network isolation and my icecc daemon runs outside of the build container in my host. The only thing I need to do for using the icecc inside my build container is mounting the unix socket /var/run/icecc/iceccd.socket inside the container. I think we need something like this mount functionality to have access to some sockets connections inside the tasks that runs on the new namespace created with unshare system call. This patch is not a the real solution for the problem and is more like an hack so we can use the icecc.bbclass again. (From OE-Core rev: 25ea276a13a6ac2342c2b0945c8fafe878d56095) Signed-off-by: Jose Quaresma Signed-off-by: Richard Purdie