Yes that's very good in the theoretical, but I was looking for actual
commands to get this done.
Solution was from Leo Sandoval,
COMPATIBLE_HOST = "null"
inside of the chromium_52.0.2743.76.bbappend
On 06/13/2017 02:56 PM, Burton, Ross wrote:
The canonical solution here is to write
On 13 June 2017 at 20:26, Jimi Damon wrote:
> 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 he
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 possibl
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
On Tue, 2017-06-13 at 11:32 -0700, Jimi Damon wrote:
> 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 resu
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
--
___
yocto mailing list
yocto
