Closed natlor closed 7 months ago
Reproducibility of the setup: the goal of kas is that everyone with the config in hands, the kas tool installed and either all official deps installed or using the kas container is able to build things as well.
There is currently a proposal under discussion to address the buildtools use case (https://groups.google.com/d/msgid/kas-devel/20230220122607.1504653-1-alexandre.belloni%40bootlin.com).
That feature was never completed, and this request had no follow-up. Feel free to reopen or follow up on the mailing list if there is still a need.
@jan-kiszka I have exactly the same problem as @natlor: The layer meta-spdxscanner adds tools to HOSTTOOLS that are not available as system packages, but installed in /usr/local/bin in my case (but I could put them anywhere). I'd like to discuss possible solutions. How do you propose to continue? Reopen this request (I don't have rights to do so), add a new one, or discuss on the mailing list?
It is probably best to start a new discussion as we should focus on how to enable a manageable and reproducible support for HOSTTOOLS
. Discussions usually take place on the mailing list, but issues can help to pin a topic.
Hi, I noticed libkas.py is overwriting
PATH
environment when callingsource oe-init-build-env/isar-init-build-env
. Is there any reason to changePATH
instead of using the userPATH
?I am using an
HOSTTOOLS
installed bypip
in/usr/local/bin
but Yocto cannot resolve theHOSTTOOLS
location asPATH
doesn't contain anymore/usr/local/bin
. So, I had to patchlibkas.py
to giveenv=None
torun_cmd()
.