Preventing a package from building
Hi,
I tried using the PACKAGE_EXCLUDE = "chromium" in my local.conf file but I'm finding that my build it is still trying to build this package.
Is there a way to prevent this build stage from occurring ?
Thanks
Quoted 7 lines · Jimi Damon
Hi,
I tried using the
PACKAGE_EXCLUDE= "chromium" in my local.conf file but I'm finding that my build it is still trying to build this package.
is it on your image? at the end, this variable is to exclude the package on the resulting image/rootfs.
Quoted 13 lines
Is there a way to prevent this build stage from occurring ?
Thanks
Signature · 4 lines
_______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
This package is being built on the host side during a bitbake using a Boundary Devices Yocto build (
* MACHINE=nitrogen6x DISTRO=fslc-x11 . setup-environment build *
+
* bitbake boundary-eval-image-xfce *
) .
I was looking for an easy way to disable even building this into the image since the compilation takes quite a long time for Chromium.
Quoted 24 lines · Leonardo Sandoval
Quoted 7 lines · Jimi Damon
Hi,
I tried using the
PACKAGE_EXCLUDE= "chromium" in my local.conf file but I'm finding that my build it is still trying to build this package.is it on your image? at the end, this variable is to exclude the package on the resulting image/rootfs.
Quoted 12 lines
Is there a way to prevent this build stage from occurring ?
Thanks
Signature · 4 lines
_______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
A message that is not in the archive (sent off-list or not yet received): [email protected]
Is there a way to apply this ( or something like it ) inside the current bblayers.conf file ?
I've already built most of this image and I don't want to accidentally lose all of that work by changing a global configuration file nor do I wish to change the global recicpe itself if that's possible.
Thanks
Quoted 49 lines · Leonardo Sandoval
Quoted 4 lines · Jimi Damon
This package is being built on the host side during a bitbake using a Boundary Devices Yocto build (
Quoted 8 lines
MACHINE=nitrogen6x DISTRO=fslc-x11 . setup-environment build
+
bitbake boundary-eval-image-xfce
try
a bit hacky but you can also use the
COMPATIBLE_HOST= "null" variable inside the chromium recipe,
not really sure that works (never tried)leo
Quoted 28 lines
) .
I was looking for an easy way to disable even building this into the image since the compilation takes quite a long time for Chromium.
Quoted 18 lines · Leonardo Sandoval
Quoted 7 lines · Jimi Damon
Hi,
I tried using the
PACKAGE_EXCLUDE= "chromium" in my local.conf file but I'm finding that my build it is still trying to build this package.is it on your image? at the end, this variable is to exclude the package on the resulting image/rootfs.
Quoted 7 lines
Is there a way to prevent this build stage from occurring ?
Thanks
Quoted 10 lines · Jimi Damon
This package is being built on the host side during a bitbake using a Boundary Devices Yocto build (
* MACHINE=nitrogen6x DISTRO=fslc-x11 . setup-environment build *
+
* bitbake boundary-eval-image-xfce *
The canonical solution here is to write your own image recipe that doesn't include chromium. Copy the evaluation image, and edit it as required.
Ross
Yes that's very good in the theoretical, but I was looking for actual commands to get this done.
Solution was from Leo Sandoval,
Quoted 1 line
COMPATIBLE_HOST= "null"
inside of the chromium_52.0.2743.76.bbappend
Quoted 4 lines · Ross
The canonical solution here is to write your own image recipe that doesn't include chromium. Copy the evaluation image, and edit it as required.
Ross