How would a newcomer get started?
Is there an FAQ or Wiki that gives a developer overview of the project, patch
submission process, etc.?
It’s hard to jump on to the moving train…
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Stephen K Jolle
annot find satisfactory explanation on how packages are
generated, we can file a bug against the docs and get a good explanation in
there.
Hope this helps,
Scott
On Wed, Mar 13, 2019 at 9:21 AM Steve Scott mailto:ssc...@san.rr.com> > wrote:
Hi:
I’ve been trying to get a better unde
Hi:
I've been trying to get a better understanding of how packages are generated
by recipes. I found a fairly good explanation in an old OpenEmbedded User's
Manual
(https://dominion.thruhere.net/koen/OE/OE-usermanual.html#recipes_packages).
The manual is hard to find, and doesn't appear to be a
SRC_URI = "file://${TOPDIR}/../local_mirror/example-1.0.0.src.tar.gz" should
work, without need for do_unpack.
What error are you getting?
> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Edmund Nadolski
> Sent: Wednesday,
Hi all:
I am using the jethro (2.0.1) version of yocto.
I added a shared library (foo.so) to our native sdk build by putting
BBCLASSEXTEND = "nativesdk"
in the foo.bb recipe, then
TOOLCHAIN_HOST_TASK_append += " nativesdk-foo nativesdk-foo-dev "
in our rootfs image recipe.
This had the
d=78e
> > ca8242ea5397c4dc0654d62244453b4260151)
> > works on sumo.
> >
> > Stefano's suggestion unfortunately didn't work.
> >
> > Maybe, it is time to create the sumo branch?
> >
> > On 10/18/2018 9:48 AM, Steve Scott wrote:
> >> I di
I did not try it on sumo.
From: Stefano Cappa [mailto:stefano.cappa.k...@gmail.com]
Sent: Wednesday, October 17, 2018 11:15 PM
To: ssc...@san.rr.com
Cc: Sinan Kaya ; yocto@yoctoproject.org
Subject: Re: [yocto] [selinux] sumo compilation
Exactly the same issue since September.
Here is
nativesdk
>
> On Sat, 6 Oct 2018 at 06:18, Steve Scott wrote:
> > I am able to generate a standard SDK with native and target sysroots.
> > The target sysroot has header files for my custom libraries. The
> > header files are generally installed in
> > /usr/include/
&g
.
However, I cannot grok how to get these files into the SDK's native
tree. It seems related to
BBCLASSEXTEND = "native nativesdk"
but I'm just chasing my tail trying to figure out the magic incantation.
Does anyone know how to do this? Or is there a
