From: Christopher Larson chris_lar...@mentor.com
bitbake handles immediate expansions of LAYERDIR for us automatically.
Signed-off-by: Christopher Larson chris_lar...@mentor.com
---
conf/layer.conf | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/conf/layer.conf b/conf
From: Christopher Larson chris_lar...@mentor.com
bitbake handles immediate expansions of LAYERDIR for us automatically.
Signed-off-by: Christopher Larson chris_lar...@mentor.com
---
conf/layer.conf | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/conf/layer.conf b/conf
From: Christopher Larson chris_lar...@mentor.com
bitbake handles immediate expansions of LAYERDIR for us automatically.
Signed-off-by: Christopher Larson chris_lar...@mentor.com
---
conf/layer.conf | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/conf/layer.conf b/conf
From: Christopher Larson chris_lar...@mentor.com
bitbake handles immediate expansions of LAYERDIR for us automatically.
Signed-off-by: Christopher Larson chris_lar...@mentor.com
---
conf/layer.conf | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/conf/layer.conf b/conf
From: Christopher Larson chris_lar...@mentor.com
bitbake handles immediate expansions of LAYERDIR for us automatically.
Signed-off-by: Christopher Larson chris_lar...@mentor.com
---
conf/layer.conf | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/conf/layer.conf b/conf
From: Christopher Larson chris_lar...@mentor.com
bitbake handles immediate expansions of LAYERDIR for us automatically.
Signed-off-by: Christopher Larson chris_lar...@mentor.com
---
conf/layer.conf | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/conf/layer.conf b/conf
From: Christopher Larson chris_lar...@mentor.com
bitbake handles immediate expansions of LAYERDIR for us automatically.
Signed-off-by: Christopher Larson chris_lar...@mentor.com
---
conf/layer.conf | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/conf/layer.conf b/conf
From: Christopher Larson chris_lar...@mentor.com
bitbake handles immediate expansions of LAYERDIR for us automatically.
Signed-off-by: Christopher Larson chris_lar...@mentor.com
---
conf/layer.conf | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/conf/layer.conf b/conf
From: Christopher Larson chris_lar...@mentor.com
bitbake handles immediate expansions of LAYERDIR for us automatically.
Signed-off-by: Christopher Larson chris_lar...@mentor.com
---
conf/layer.conf | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/conf/layer.conf b/conf
From: Christopher Larson chris_lar...@mentor.com
bitbake handles immediate expansions of LAYERDIR for us automatically.
Signed-off-by: Christopher Larson chris_lar...@mentor.com
---
conf/layer.conf | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/conf/layer.conf b/conf
Read layer.conf in each layer. See the BBFILES variable.
--
Christopher Larson
On Monday, January 9, 2012 at 5:51 PM, James Abernathy wrote:
I'm trying to understand how bitbake parses the poky directory tree a little
better.
The best I can figure all .bb files are NOT included. Just
Ensure that your layer is before the other in BBLAYERS.
--
Christopher Larson
On Tuesday, January 24, 2012 at 3:47 AM, Joshua Immanuel wrote:
Hello all,
What is the preferred way of overriding an existing class in the 'meta'
layer. I tried to add the existing class (say image_types.bbclass
On Tuesday, January 24, 2012 at 9:17 AM, Paul Eggleton wrote:
On Tuesday 24 January 2012 07:32:47 Christopher Larson wrote:
I'd also say, what is in the classes is intended to work for everyone, so if
there's something in the core classes that is not working well for your
situation
Nope. Recipes cannot modify the metadata of other recipes or the configuration
metadata, ever. In particular cases, we emit content to tmpdir and read it back
in elsewhere, but in general you should just not do what you're trying to do,
and find a better solution.
--
Christopher Larson
See the cooker.log.* files in the tmp (or build) directory.
--
Christopher Larson
On Monday, April 9, 2012 at 5:01 PM, James Abernathy wrote:
On Mon, Apr 9, 2012 at 6:15 PM, Darren Hart dvh...@linux.intel.com
(mailto:dvh...@linux.intel.com) wrote:
On 04/09/2012 01:33 PM
are interested in musl
http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/musl
Congrats on the progress :)
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
it. There'd be duplication in local disk space, but you'd
avoid the NFS locking issues.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
___
yocto
would make sense and be welcomed (pending it's implementation of course).
See gitsm.py.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
On Saturday, May 17, 2014, Chris Morgan chmor...@gmail.com wrote:
On May 17, 2014 3:58 PM, Christopher Larson
clar...@kergoth.comjavascript:_e(%7B%7D,'cvml','clar...@kergoth.com');
wrote:
On Saturday, May 17, 2014, Chris Morgan
chmor...@gmail.comjavascript:_e(%7B%7D,'cvml','chmor
of
questions.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo
at it.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
this bit from
that directory tree. This surprised me, so I thought I would pass it along
in case it saves anyone else some time.
Ah, yes, I've hit this in the past too, thanks for bringing it up, we'll
have to resolve that -- perhaps have bitbake chmod g-s ${TMPDIR} when it's
created?
--
Christopher
should have, in my opinion.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
___
yocto mailing list
yocto@yoctoproject.org
https
a postponed operation that
happens at the end of the recipe parsing.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
___
yocto mailing list
yocto
.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Fri, Jul 18, 2014 at 11:45 AM, Robert P. J. Day rpj...@crashcourse.ca
wrote:
On 2014-07-18 10:49, Christopher Larson wrote:
On Fri, Jul 18, 2014 at 9:26 AM, Gary Thomas g...@mlbassoc.com
mailto:g...@mlbassoc.com wrote:
've always used 'IMAGE_INSTALL += xyz' in my
On Fri, Jul 18, 2014 at 11:55 AM, Robert P. J. Day rpj...@crashcourse.ca
wrote:
On Fri, 18 Jul 2014, Christopher Larson wrote:
I really don't think this was ever safe, as it completely depended
on how the image recipe added its bits to IMAGE_INSTALL, which could
easily vary from image
-rootfs#usage it should work fine
for you.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
___
yocto mailing list
yocto@yoctoproject.org
https
recipe that was capable of building every m4
version that existed. It was mostly to see if it could be done :)
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
an expected value, also, I'd called it _REQUIRED or something, but
that's minor. In general, I agree that things are rather inconsistent with
regard to variable naming, but that's true everywhere, not just for these
variables :)
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake
emailing a multi-purpose list like yocto@, so it's clear what exactly it's
patching before reading the email :)
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
implementation of alternatives
that's provided in chkconfig, rather than cworth's shell version. I haven't
tested it in that context, but I doubt it runs so many external tools.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software
On Thu, Aug 21, 2014 at 5:08 PM, Seth Bollinger seth.b...@gmail.com wrote:
Our device requires two images to be built. Is there any way to have the
first image depend on the second image?
do_rootfs[depends] += some-other-image:do_rootfs would probably do.
--
Christopher Larson
clarson
Bluez4, but i want to use Bluez5.
How can i remove default Bluez4 from core-image-base?
PREFERRED_PROVIDER_bluez4 ?= bluez5
and have 'bluetooth' in DISTRO_FEATURES
Afaik bluez5 is not a provider of bluez4, so oe-core doesn't provide a way
to swap between the two at this time.
--
Christopher
a valid character in a shell function, so while potentially
irritating, it's not surprising :)
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
so that my
other builds can make use of them?
I doubt there's a best on that. Personally I either use a shared
filesystem path (e.g. nfs) or hook up rsync.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer
-- both apply, not an OR relationship, where you can
choose which to use.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
___
yocto mailing list
/kernel:do_shared_workdir
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
override the package to be used for that functionality.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
___
yocto mailing list
yocto@yoctoproject.org
/')
('/usr/bin', '')
dirsplit('/usr/bin')
('/usr', 'bin')
dirsplit('/bin')
('/', 'bin')
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
. You might need
https://gist.github.com/kergoth/3713d779c14dc8b98f36.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
___
yocto mailing list
yocto
-certificates rather than bypassing certificate checking, personally, but
I can see how that would be a useful workaround. :)
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
misconfigured)?
At least in the past, we’ve been highly inconsistent in certificate store
configuration in various recipes, some pointing at a dir, some a file, and
the paths vary. I don’t know if anyone ever fixed that, however — this is
from memory.
--
Christopher Larson
clarson at kergoth dot
nderstanding).
>
> Also, please open a bug report for opkg on
> https://bugzilla.yoctoproject.org to track the issue.
>
> > *From:*kerg...@gmail.com [mailto:kerg...@gmail.com] *On Behalf Of
> > *Christopher Larson
> > *Sent:* Tuesday, October 20, 2015 10:20 PM
> &
On Sat, Oct 24, 2015 at 12:19 PM, Paul Barker <p...@paulbarker.me.uk> wrote:
> On Sat, Oct 24, 2015 at 06:54:16PM +, Christopher Larson wrote:
> > Not likely to help. The problem is the filename length, which will be the
> > same whether it's a file or a symlink.
>
>
> Why the change?
>
I believe we need https://github.com/kergoth/meta-mentor/commit/2125799
applied to oe-core, haven't had a chance to submit it yet, but it looked to
me like an accidental loss of the stderr capture/suppression when the
metadata_scm functions were reworked recently.
--
ring the resources
> to implement them.
>
> We did discuss list proliferation, filtering patches, etc and still
> decided the best solution was a new list.
>
> Philip
>
>
> Forwarded Message
> Subject: Welcome to the "Openemebdded-architecture" ma
On Tue, Nov 17, 2015 at 11:02 AM, Paul Eggleton <
paul.eggle...@linux.intel.com> wrote:
> On Tuesday 17 November 2015 08:39:55 Christopher Larson wrote:
> > On Tue, Nov 17, 2015 at 8:33 AM, Gary Thomas <g...@mlbassoc.com> wrote:
> > > When I run bitbake using laye
On Mon, Nov 2, 2015 at 8:25 AM, Nicolas Dechesne <
nicolas.deche...@linaro.org> wrote:
> On Mon, Oct 26, 2015 at 12:46 AM, Christopher Larson <clar...@kergoth.com>
> wrote:
>
>>
>>> I've just posted patches to the opkg-devel list which should fix this. I
>
yntax wrong?
>
Not doable, no. You could make a python do_something which calls both
`whatever` and your shell `something_shell`, though. i.e.
python whatever () {
pass
}
do_something_shell () {
:
}
python do_something () {
bb.build.exec_func("whatever", d)
bb.build.exec_func(&quo
on the host during rootfs creation.
>
> OPKG_ARGS = "--cache-dir=/tmp/opkg"
>
> I'll submit a patch to opkg to add this option.
>
This will only shorten the full path, not the filename length, so I doubt
this'll solve it. That said, I can't actually successfully test this
On Tue, Oct 20, 2015 at 10:14 AM, Christopher Larson <clar...@kergoth.com>
wrote:
>
> On Sun, Oct 18, 2015 at 2:57 AM, Paul Barker <p...@paulbarker.me.uk>
> wrote:
>
>> On Fri, Oct 16, 2015 at 07:38:19PM +, Ahsan, Noor wrote:
>> > On Oct 16,
OT there.
> bash is also missing from core-image-base . is that to be expected? Should
> I add it as a CORE_IMAGE_EXTRA_INSTALL or as an EXTRA_IMAGE_FEATURE ?
>
Yes, that's expected, busybox is used by default. Add bash yourself if you
want it, or use a different imag
setting
>
> ALLOW_EMPTY_${PN}-dbg = "1"
> ALLOW_EMPTY_${PN}-dev = "1"
>
> in sources/poky/meta/conf/bitbake.conf solved their issues. But these are
> already set in my case.
>
lmsensors emits a ton of binary packages, you'll have to see which ones you
need.
and configurations with
BB_GENERATE_MIRROR_TARBALLS=1 to ensure you have current, not out of date
scm tarballs.
2. Set up builds of all your supported machines and configurations, using a
new DL_DIR, with PREMIRRORS pointing to the old DL_DIR.
3. Either clean up the old DL_DIR b
On Fri, Oct 2, 2015 at 11:22 AM, Daniel. <danielhi...@gmail.com> wrote:
> Where can I find this recipetool!? It seems a nice tool to have :)
>
It's in oe-core/scripts or poky/scripts in any recent release. It'll be in
the PATH after sourcing the setup scripts.
--
Christopher La
install folder,
> something like:
>
> do_install_append() {
> cp ${S}/myjournald.conf ${D}/propper/path/to/journald.conf
> }
Which is precisely what recipetool appendfile will do for you :)
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZa
On Fri, Oct 2, 2015 at 8:58 AM, Fred Ollinger <fred.ollin...@seescan.com>
wrote:
> I'm trying to change my /etc/systemd/journald.conf file.
>
recipetool appendfile sounds like exactly what you want here.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake,
It's installed into /boot on the rootfs with the zImage prefix, and
update-alternatives creates a symlink to the correct path so uboot can find
it. Not sure why this indirection exists, but it does work.
On Thu, Sep 24, 2015 at 4:52 AM Colin Helliwell <
colin.helliw...@ln-systems.com> wrote:
>
ed or required, only the recipe itself. So you'll need to
bbappend every recipe that includes foo-hwbringup-image.bb in this case.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
ust doesn't contain the graphics support.
>
> Is there a better way to add your custom components to "core-image" I
> guess…..
>
You could always define custom features for use in IMAGE_FEATURES and add
them to your images via EXTRA_IMAGE_FEATURES in local.conf, or bbappend
om bbappend foo-hwbringup-image?
>
> If you follow the original post one more generation,
> foo-hwbringup-image.bb "inherit core-image"
>
It isn't. You asked how to add custom components to a core-image, that's
one way to do it, append every image involved. W
recipe anew when
running each task, after the up front parse which is used to generate the
runqueue. *shrug*. It's a downside of showing messages in anything but task
execution context.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Se
cto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
her you're
tracking a branch or a tag, add SRCPV to PV :)
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
en a
> “read-only” image is specified by the build script?
>
>
>
> Thanks.
>
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
--
Christopher Lar
s rather less trivial, since bitbake generates
signatures/checksums at parse time.
Alternatively, would it be possible to contact the server via the json API
at parse time as long as BB_NO_NETWORK isn't set? Of course, unless there's
a way to support the BB_NO_NETWORK case, that would be problematic as
On Fri, Jun 17, 2016 at 2:42 PM, Christopher Larson <clar...@kergoth.com>
wrote:
> On Fri, Jun 17, 2016 at 8:31 AM, Jolley, Stephen K <
> stephen.k.jol...@intel.com> wrote:
>
>> ·There is a multilib issue related to the layout of the host
>> libraries le
From: Christopher Larson <chris_lar...@mentor.com>
We need to obey LDFLAGS to get the correct hash style for external toolchains.
The ideal way to deal with this would be for the build to be like the qt4
build, obeying the OE_QMAKE_ variables as defined in qmake_base, but that's
not
ckages. Then we might need to patch
FindPythonLibs in cmake to do the same. I'm testing the automake change
locally now.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer,
ze that path so it aligns with the expected
value of BBFILES.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
___
yocto mailing list
yocto@yoctopr
https://github.com/MentorEmbedded/meta-mentor/blob/master/meta-mel/conf/include/drop-toolchain-from-sdk.inc
may
be of interest to you.
On Wed, Feb 10, 2016 at 9:01 AM Thomas Kaufmann
wrote:
> Hi
>
>
>
> I started porting an existing linux system to the latest yocto
def foo(d):
# Do something
FOO = "${@foo(d)}"
On Wed, Feb 10, 2016 at 12:02 PM Xi Zhou Zhou
wrote:
> Hi,
>
> I want to manipulate a variable with inline python function in a recipe.
> The code is something like this.
>
> python newpv() {
> return 999
> }
>
> PV
On Fri, Feb 12, 2016 at 2:47 AM Thomas Kaufmann
wrote:
> Hi Christopher
>
>
>
> thanks for this hint, this prevented a lot of packages from being built.
>
> However I still face an additional issue. in the last step of
> do_populate_sdk, when the sdk is actually
This is the sort of case where it'd be nice if bitbake provided a plugin
mechanism, pure python, no metadata parsing. Something to think about in
the long term..
On Fri, Feb 26, 2016 at 1:59 PM Burton, Ross wrote:
>
> On 26 February 2016 at 20:16, Philip Balister
content in shared state?
>
>
>
> We are currently based on the Fido/1.8.1 tag for this exercise.
>
My guess is you didn't add SRCPV to your PV, so changes to SRCREV aren't
changing PV, and do_fetch's checksum isn't changing.
--
Christopher Larson
clarson at kergoth dot com
Founder - B
package qa bits which caused later messages to
suppress earlier due to teh use of a dictionary for the messages (the wrong
structure for this, no idea why it was done that way). There have been one
or more patches on teh list for this recently.
--
Christopher Larson
clarson at kergoth dot com
Founde
On Mon, Mar 14, 2016 at 6:55 AM Martin Jansa wrote:
> On Mon, Mar 14, 2016 at 02:44:58PM +0100, Gary Thomas wrote:
> > On 03/14/2016 01:51 PM, Gary Thomas wrote:
> > > On 03/14/2016 01:46 PM, Burton, Ross wrote:
> > >>
> > >> On 14 March 2016 at 12:41, Gary Thomas
On Mon, Mar 14, 2016 at 5:50 AM Burton, Ross wrote:
> On 14 March 2016 at 03:10, Gary Thomas wrote:
>
>> I just started a new build and saw a message that's new to me:
>> NOTE: Fetching uninative binary shim from
>>
On Tue, Mar 15, 2016 at 2:06 PM Chris Tapp wrote:
> I’ve got an X11 application which uses Pulseaudio. Everything works as
> expected when built under “daisy” (Pulseaudio 5), but the same system built
> under “jethro” (Pulseaudio 6) fails as Pulseaudio doesn’t start
>
On Tue, Mar 15, 2016 at 3:56 PM Chris Tapp wrote:
> Should I use master or master-next to track 2.1 release progress?
>
master-next is rebased. I wouldn't recommend using it unless you need to
test something specific which is on that branch and isn't yet on master,
On Thu, Mar 17, 2016 at 8:47 AM Christopher Larson <clar...@kergoth.com>
wrote:
> On Thu, Mar 17, 2016 at 8:43 AM Matt Hoosier <matt.hoos...@gmail.com>
> wrote:
>
>> On Wed, Mar 16, 2016 at 4:46 PM, Matt Hoosier <matt.hoos...@gmail.com>
>> wrote:
>>
On Thu, Mar 17, 2016 at 8:43 AM Matt Hoosier <matt.hoos...@gmail.com> wrote:
> On Wed, Mar 16, 2016 at 4:46 PM, Matt Hoosier <matt.hoos...@gmail.com>
> wrote:
>
>>
>>
>> On Wed, Mar 16, 2016 at 4:40 PM, Christopher Larson <clar...@kergoth.com>
>
On Thu, Mar 17, 2016 at 9:48 AM Matt Hoosier <matt.hoos...@gmail.com> wrote:
> On Thu, Mar 17, 2016 at 10:48 AM, Christopher Larson <clar...@kergoth.com>
> wrote:
>
>>
>>
>> On Thu, Mar 17, 2016 at 8:47 AM Christopher Larson <clar...@kergoth.com>
>
t know if it addresses the reloc issue or not, but it's a
substantial improvement over master. See
https://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=mgh/meta-mingw
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, Op
The default *system* shell (/bin/sh) or the default shell for users, or for
root? Folks often conflate them, but they're not the same.
On Fri, Mar 4, 2016 at 7:01 AM Oliver Graute
wrote:
> Hello,
>
> how can I change the default shell on the yocto target from bash to
>
t touched it in ages,
but in theory it should work.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
No, libdir is /usr/lib on the target. We never write to the host system
outside the build directory. do_install installs a lib into ${D}${libdir},
and then the contents of ${D} get split up into individual binary packages,
and those packages are then installed in a root filesystem and archived
nfig metadata
access recipe metadata, by design. I'd recommend enabling buildhistory and
using the buildhistory-collect-srcrevs script, which dumps SRCREV_pn- lines
for recipes, for use in a .conf/.inc/.bbclass.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZauru
ranch will get bug fixes and security updates after the
release. If you don't want it to change at all, use the tag or tarballs,
not the branch.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
__
On Tue, May 3, 2016 at 3:31 PM, Mark T <mtl1nux...@gmail.com> wrote:
> Hi Christopher,
>
> Thanks. What is the command option to specify the tag and is there a list
> or tags available ?
>
https://git-scm.com/book/en/v2
--
Christopher Larson
clarson at kergoth dot
On Mon, Apr 18, 2016 at 5:50 PM Khem Raj wrote:
>
> On Apr 18, 2016 3:51 PM, "Richard Purdie" <
> richard.pur...@linuxfoundation.org> wrote:
> >
> > On Mon, 2016-04-18 at 10:35 -0700, Khem Raj wrote:
> > > Can we have a possibility to select field like "affected version"
> >
On Thu, Apr 14, 2016 at 10:39 AM Sid Price wrote:
> Hello, I am new to Yocto and relatively new to Linux. I am working my way
> through the “Getting Started” guide and I have met a problem. I am trying
> to run the “environment-setup …” script for the arm platform. First
On Fri, Feb 17, 2017 at 3:39 PM, Christopher Larson <kerg...@gmail.com>
wrote:
> On Fri, Feb 17, 2017 at 2:26 PM, Aníbal Limón <
> anibal.li...@linux.intel.com> wrote:
>
>> +parser.add_argument('-l', '--layer', metavar='LAYER_DIR',
>> +help='Layer
> I see at my tmp/deploy/rpm/ folder both of my machines folders aside
> of cortex-arm-v6-hf-... folder. How can I make the package goes to the
> specific machine that was used in build instead of the cortex-arm-...
> one?
>
PACKAGE_ARCH = “${MACHINE_ARCH}”
--
Christopher Larson
for machine or distro, but it doesn’t actually tell
them that, and displaying the changed checksums isn’t of a great deal of
use on its own either, I’d suggest at least capturing the changed variables
via bitbake-diffsigs or bitbake -S printdiff.
--
Christopher Larson
kergoth at gmail dot com
Founder - BitBake,
able release branches.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
s
> files. i'm puzzled by the above.
>
You’re right to be puzzled, as that addition is pointless and will do
nothing useful.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
__
e
shallow-external branch, if you’re curious.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
___
yocto mailing list
yocto@yoct
> method:
>
> python () {
> if '${MACHINE}' == 'myMachineName':
> bb.build.addtask('do_mycustomtask', 'do_compile', 'do_configure',
> d)
> }
>
> I personally find that nicer than the if check in the function itself,
> because the tasks will only show up in bu
1 - 100 of 110 matches
Mail list logo