aight into D?
>
> Thank you,
>
> Davis
> --
> ___
> bitbake-devel mailing list
> bitbake-de...@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/bitbake-devel
>
--
Christopher Larson
kergoth at gmail dot com
Founder - BitBake
embedded/meta-python "
> BBLAYERS += " ${BSPDIR}/sources/meta-openembedded/meta-filesystems "
> BBLAYERS += " ${BSPDIR}/sources/meta-qt5 "
> BBLAYERS += " ${BSPDIR}/sources/meta-hon-grip "
> BBLAYERS += " ${BSPDIR}/sources/meta-java "
&g
orce --no-archive --prefix=%s \
> --inputfile=%s/i18n/locales/%s --charmap=%s %s" \
> % (treedir, datadir, locale, encoding, name)
> --
> ___
> bitbake-dev
On Mon, Nov 13, 2017 at 7:10 PM, Christopher Larson
wrote:
>
>
> On Mon, Nov 13, 2017 at 11:17 AM, Martyn Welch
> wrote:
>
>> From: Fabien Lahoudere
>>
>> Sometimes we wish to ensure that packages don't install files or
>> directories somewhere th
[1:].startswith(p) and ((file[1:] != p) or
> exactmatch) :
> +msg = "%s is in a prohibited path.\n" % file[1:]
> +package_qa_handle_error("prohibited-path", msg,
> d)
>
Unless I’m missing
/home/bianchi/poky/openembedded-core/conf/layer.conf: [Errno 2] file
> > /home/bianchi/poky/openembedded-core/conf/layer.conf not found
> >
> >
> > Thanks,
> >
> > Riko
> >
>
>
> --
> ___________
> yocto mai
imply any particular layer..
--
Christopher Larson
kergoth at gmail dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Senior Software Engineer, Mentor Graphics
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
e is also in the
oe-core layer, so the patch should ideally go to the openembedded-core
mailing list. Thanks again!
See http://openembedded.org/wiki/Commit_Patch_Message_Guidelines.
--
Christopher Larson
kergoth at gmail dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Senior Software Enginee
On Fri, Feb 17, 2017 at 3:39 PM, Christopher Larson
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',
>> +
just
using arguments?
That is, why `layer-compat-layer.py -l layerpath` rather than
`layer-compat-layer.py layerpath`. If you change the call to
`parser.add_argument(‘layer’, …)` it’d change to the latter behavior.
--
Christopher Larson
kergoth at gmail dot com
Founder - BitBake, Open
lly 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, OpenEmbedd
pm/ 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
kergoth at gmail dot com
Foun
nager if you use packages for update distribution (though I
wouldn’t advise use of packages for update distribution at all, that’s a
different discussion :).
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Enginee
> PV="1.0.10"
> PR="-beta"
>
> Is there anyway to grab that information from Makefile and setting PV & PR
> according to it? At compilation time? So that I only have to change at one
> place?
>
bitbake wants to know pv/pr at parse time, long before
h, 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@yoctoproject.org
https://lists.yoctoproject.
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
--
__
d in via
RRECOMMENDS, so I can use BAD_RECOMMENDATIONS to exclude it for images that
don’t need it (dtrace is the only thing in systemtap that needs python3).
https://github.com/openembedded/meta-openembedded/compare/master...kergoth:lirc-python-3
does
the same for lirc.
--
Christopher Larson
clarson
> 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
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
to sanitize 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
yoc
On Fri, Jun 17, 2016 at 2:42 PM, Christopher Larson
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 leaking into python’s build pro
the automake packages. 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
From: Christopher Larson
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 going to happen just now. The
tbake 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 well.
--
Christopher
n a
> “read-only” image is specified by the build script?
>
>
>
> Thanks.
>
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
--
Christopher Larson
clarson at ker
s git repo is up to date. All the examples of
>> python module recipes I can find uses PyPI:
>>
>
> Just change the SRC_URI to a git URI, that's all you need to do.
And S to ${WORKDIR}/git, set SRCREV, and depending on whether you're
tracking a branch or a tag, add SRCP
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
Mainta
le update". Any idea how to do
>> it in a comon way?
>>
>
> Use the gitsm: fetcher, which will do that for you.
>
> Ross
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject
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, OpenZaurus
Maintainer
On Tue, May 3, 2016 at 3:31 PM, Mark T 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 com
Founder - BitBake, OpenEmbed
urity 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
--
__
s a reasonable place in the code, yes. You can inspect a certain
amount of information in the signature data files, but I'm not sure it
drills down to the level you desire.
My 'bb' tool's 'show' subcommand can show not just a variable but also its
dependencies, perhaps tha
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
into
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"
> > > and have it such t
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 I
> notice that when I li
es 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, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Men
On Thu, Mar 17, 2016 at 9:48 AM Matt Hoosier wrote:
> On Thu, Mar 17, 2016 at 10:48 AM, Christopher Larson
> wrote:
>
>>
>>
>> On Thu, Mar 17, 2016 at 8:47 AM Christopher Larson
>> wrote:
>>
>>> On Thu, Mar 17, 2016 at 8:43 AM Matt Hoosier
>
On Thu, Mar 17, 2016 at 8:47 AM Christopher Larson
wrote:
> On Thu, Mar 17, 2016 at 8:43 AM Matt Hoosier
> wrote:
>
>> On Wed, Mar 16, 2016 at 4:46 PM, Matt Hoosier
>> wrote:
>>
>>>
>>>
>>> On Wed, Mar 16, 2016 at 4:40 PM, Christopher Larso
On Thu, Mar 17, 2016 at 8:43 AM Matt Hoosier wrote:
> On Wed, Mar 16, 2016 at 4:46 PM, Matt Hoosier
> wrote:
>
>>
>>
>> On Wed, Mar 16, 2016 at 4:40 PM, Christopher Larson
>> wrote:
>>
>>> On Wed, Mar 16, 2016 at 2:32 PM, Matt Hoosier
>&g
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,
otherwise I'd wait for changes
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
> automatically.
>
> It looks
On Mon, Mar 14, 2016 at 10:56 AM Daniel. wrote:
> Hi all,
>
> I was wondering how OE/Yocto would respond if the same task is appended
> twice.
>
> If I have a .bbclass that already creates a do_install_append() and I
> inherit this class at my recipe, will my do_install_append be aplied:
>
> - Be
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
>> http://downloads.yoctoproject.org/releases/uninative/0.95/x86_64-nativesdk-lib
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 g...@mlbassoc.com>> wrote:
> >
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
> another shell like dash?
>
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 wrote:
>
>> I must admit, I'm su
On Thu, Feb 18, 2016 at 9:48 PM Vivek Per wrote:
> Does any one know which package produces "ss" utility in yocto. i
> tried iproute2 reciepe which is not present.
>
iproute2 is in oe-core, look again.
http://layers.openembedded.org/layerindex/recipe/5516/
--
_
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 supposed to be put together.
>
> I
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 = "${@newpv()}"
>
>
> The
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 base. The
> hardware TI am 335
tent 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
e 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 a
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 wrote:
> > > When I run bitbake using layers that are not GIT re
>
> 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 rec
nt 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" mailing list
>
Typo. Openem
H (the layer paths)
to find 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.yoct
u 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("something_shell&quo
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
> wrote:
>
>>
>>> I've just posted patches to the opkg-devel list which should fix this. I
>>> had
>>&
On Sat, Oct 24, 2015 at 12:19 PM, Paul Barker wrote:
> On Sat, Oct 24, 2015 at 06:54:16PM +0000, 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.
> > On Sat, Oct 24, 2015
but that's my understanding).
>
> 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, 201
On Tue, Oct 20, 2015 at 10:14 AM, Christopher Larson
wrote:
>
> On Sun, Oct 18, 2015 at 2:57 AM, Paul Barker
> wrote:
>
>> On Fri, Oct 16, 2015 at 07:38:19PM +, Ahsan, Noor wrote:
>> > On Oct 16, 2015, at 5:47 AM, Ahsan, Noor > noor_ah...@mentor.com>>
ring 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 c
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. Re
; ntpdate is NOT 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
On Fri, Oct 2, 2015 at 11:22 AM, Daniel. 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 Larson
clarson at kergoth
mething 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, OpenZaurus
Maintainer - Tslib
On Fri, Oct 2, 2015 at 8:58 AM, Fred Ollinger
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, OpenEmbedded, OpenZaurus
Maintainer - T
t the job done:
1. Do a build of all your supported machines 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
fferent from 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 eve
It just 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
lf. 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
--
_
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:
> Thi
/import to actually
> let the full certificate checking happen.
I think the better bet is to fix it so it actually finds the certs from
ca-certificates rather than bypassing certificate checking, personally, but
I can see how that would be a useful workaround. :)
--
Christopher Larson
cl
was looking for some certificates in /usr/lib/ssl/certs
> but that directory is missing.
>
> Anyone know what I might be missing (or have misconfigured)?
>
At least in the past, we’ve been highly inconsistent in certificate store
configuration in various recipes, some pointing at a
Richard fixed this in master and fido after I opened a Yocto bug about it.
I don't recall the commit offhand, but you may be able to cherry-pick it.
On Sat, May 16, 2015 at 4:16 AM Christian Magnusson wrote:
> I also stumbled into this problem.
>
> We are using a BSP from Phytec. It’s using poky
tization/normalization probably..
>>> def dirsplit(p):
... return os.path.dirname(p), os.path.basename(p)
...
>>> dirsplit('/usr/bin/foo')
('/usr/bin', 'foo')
>>> dirsplit('/usr/bin/')
('/usr/bin', &#
recipe, your image,
whatever) will tell you why the sstate wasn't used, by finding the ones
that are in SSTATE_DIR which most closely match the current configuration,
and displaying a detailed delta between the two. You might need
https://gist.github
, nor anything special about it. It's just a convention to let the
user 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
--
an
AND relationship -- 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
--
__
do_configure[depends] += "virtual/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
t is the best
> way (if any) to share any newly created objects 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
o_something does not contain the definition of foo-bar_do_something.
>
- isn't a valid character in a shell function, so while potentially
irritating, it's not surprising :)
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenE
n host system's /etc
> directory. How can I avoid it and do_install function can use /etc
> directory of rootfs?
>
Read the makefiles of the project you're building. Specifically, modify
them to stop running ldconfig.
--
Christopher Larson
clarson at kergoth dot com
Founder - Bi
e-image-base have 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 pro
On Thu, Aug 21, 2014 at 5:08 PM, Seth Bollinger 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 at
; become broken links and the update-alternatives script can't
> run).
>
One option for that might be to try the C 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 ext
ear 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
--
___
yocto mailin
RDEPENDS can
reference, e.g. backwards-incompatible changes going into the layer, not
the version of the layer's layer.conf specifically. _SET is a weird way to
indicate an expected value, also, I'd called it _REQUIRED or something, but
that's minor. In general, I agree that things are
me
(2010) to have a single m4 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
s://github.com/MentorEmbedded/meta-ro-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
On Fri, Jul 18, 2014 at 11:55 AM, Robert P. J. Day
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 v
On Fri, Jul 18, 2014 at 11:45 AM, Robert P. J. Day
wrote:
>
> > On 2014-07-18 10:49, Christopher Larson wrote:
> > >
> > > On Fri, Jul 18, 2014 at 9:26 AM, Gary Thomas > > <mailto:g...@mlbassoc.com>> wrote:
> > >
> > > 've al
might be value in differentiating between cases like
this in the documentation, if we don't already.
--
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
t;. If the recipe didn't use ?=, then your
IMAGE_INSTALL += would have had no effect at all. To append to
IMAGE_INSTALL directly without using CORE_IMAGE_EXTRA_INSTALL you could
have used IMAGE_INSTALL_append, since that's a postponed operation that
happens at the end of the recipe parsing.
--
Christopher
he subject "[RFC PATCH 0/2] Add
/etc/os-release". It's definitely something we should have, in my opinion.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
__
om
> 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?
--
d that some folks seem to find it a
useful way of looking 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
uild in toaster context, afaik. I haven't spent much time playing
with it, but it does seem like it's intended to answer just these sort of
questions.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer,
On Saturday, May 17, 2014, Chris Morgan wrote:
>
> On May 17, 2014 3:58 PM, "Christopher Larson"
> >
> wrote:
> >
> >
> >
> > On Saturday, May 17, 2014, Chris Morgan
> > >
> wrote:
> >>
> >> Hello.
> >>
&
modules
> 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
--
__
1 - 100 of 119 matches
Mail list logo
