A bit of a mixed bag: one bugfix, move to Bootstrap 3 for the frontend,
some minor features and significant work on how update tasks for the
other distro comparison functionality works.
The following changes since commit 3aa6bf964d81a04b652499069f0454c546a5e296:
import_layer.py: add -t option
I have an iMX6 board with meta-freescale.
I'm using yocto sumo with meta-security and I want to try to add
meta-selinux (without meta-virtualization) to do some experiments.
However, while building I receive this error:
ERROR: e2fsprogs-native-1.43.8-r0 do_patch: Command Error: 'quilt --quiltrc
Yes, that's it.
On Wed, 19 Sep 2018 at 21:07, Fabian Sturm wrote:
>
> Hmm I guess I was way overthinking this. The idea seems to just create
> a secong image definition like this it seems:
>
>
> core-image-minimal-dev.bb:
>
> require core-image-minimal.bb
>
> DESCRIPTION = "A small image
Hmm I guess I was way overthinking this. The idea seems to just create
a secong image definition like this it seems:
core-image-minimal-dev.bb:
require core-image-minimal.bb
DESCRIPTION = "A small image just capable of allowing a device to
boot and \
is suitable for development
If you're targeting just x86 then you can build an image with the
tools-sdk IMAGE_FEATURE defined, and use something like systemd-nspawn
(insert your preferred container system) to get a shell in it.
Ross
On Wed, 19 Sep 2018 at 18:14, Fabian Sturm wrote:
>
> Hi,
>
> no this is not what I am
Hi,
no this is not what I am searching for. What I want is gcc cmake and
other tools to be installed inside of the Yocto image, so that I can
compile natively in Yocto without having to hack build scripts to work
with a cross compiler.
But of course I don'T want to deliver gcc and others with
Dell - Internal Use - Confidential
> On Wed, 19 Sep 2018 12:33:37 +0100
> "Burton, Ross" wrote:
>
> > On Tue, 18 Sep 2018 at 22:21, Seebs wrote:
> > > > Are the databases supposed to be shareable between different build
> > > > machines? IIRC, the answer is no. Could you store the native
On Wed, 19 Sep 2018 12:33:37 +0100
"Burton, Ross" wrote:
> On Tue, 18 Sep 2018 at 22:21, Seebs wrote:
> > > Are the databases supposed to be shareable between different build
> > > machines? IIRC, the answer is no. Could you store the native inode
> > > type as a sqlite BLOB? Not necessarily a
Please remember to reply to the list.
On Wed, 19 Sep 2018 at 13:08, Mohamed Youseif
wrote:
> Thanks, Ross for replying, I had changed the recipe and tried to get the
> source code of ninvaders package from SourceForge with .tar extension,
> so the new recipe created was different than the old
On Tue, 18 Sep 2018 at 22:21, Seebs wrote:
> > Are the databases supposed to be shareable between different build
> > machines? IIRC, the answer is no. Could you store the native inode
> > type as a sqlite BLOB? Not necessarily a good idea Just an idea.
>
> I think coercing the values into
The problem is most likely that you're not using automake but the
generated recipe (would have been useful to include that) is using the
autotools class, which assumes correct use of both autoconf and
automake. Specifically, your hand-written Makefile doesn't handle
out-of-tree builds.
Change
Hi, I want to add the invaders game package to my image that I had built before
and tested, so I used the command "recipetool create -V 1.0
https://github.com/TheZ3ro/ninvaders.git; to make my custom recipe, then I had
to append this package to my image by appending the package name to
I think what you are looking for is a Yocto generated SDK for your image?
bitbake -c populate_sdk
Alex
2018-09-18 23:00 GMT+02:00 Fabian Sturm :
> Hi,
>
> I am wondering, there does not seem to be any information about native
> compile of projects in a Yocto docker container. It seems that
13 matches
Mail list logo
