From: Matt Wood <mattwood2000@gmail.com>
To: Jose Quaresma <quaresma.jose@gmail.com>, yocto@lists.yoctoproject.org
Subject: Re: [yocto] append recipe to multiconfig build from top-level local.conf
Date: Wed, 17 Jan 2024 17:43:59 -0500 [thread overview]
Message-ID: <ae61cfb3-ff00-4847-8fcc-5940cc31152f@gmail.com> (raw)
In-Reply-To: <CANPvuR=1KADuvR6Hym5YAW4sWOAdLzp7ww+S1d5yo0KaRsZTLQ@mail.gmail.com>
Hi Jose,
On 1/16/24 04:34, Jose Quaresma wrote:
>
>
> Matt Wood <mattwood2000@gmail.com <mailto:mattwood2000@gmail.com>> escreveu (segunda, 15/01/2024 à(s) 19:44):
>
> Hi,
>
> I was wondering if the IMAGE_INSTALL:append syntax could work in multiconfig environment from the top-level local.conf file?
>
> For example, I have a meta-layer that defines the muitconfig (main.conf and initramfs.conf). From my build directory, I was hoping to append the IMAGE_INSTALL list only for the main configuration similar to how it can be done from local.conf in a standard build. I wanted to avoid having to modify the meta-layer files.
>
> I tried the following from local.conf but neither worked:
>
> IMAGE_INSTALL:append:mc:main = " pkg"
> IMAGE_INSTALL:mc:main:append = " pkg"
>
>
> To have multiconconig you need to have more than one machine configurations so It should work with something like:
>
> IMAGE_INSTALL:append:main = " pkg1"
> IMAGE_INSTALL:append:initramfs = " pkg2"
>
> Jose
I have two configurations for a multiconfig in my meta-layer (conf/multiconfig/main.conf and conf/multiconfig/initramfs.conf)
Unfortunately, adding IMAGE_INSTALL:append:main = " nano" to conf/local.conf for example did not work.
But, adding IMAGE_INSTALL:append = " nano" to conf/multiconfig/main.conf does work and nano gets built.
Any other suggestions to have append a multiconfig IMAGE_INSTALL list from the top level conf/local.conf?
Thanks, Matt.
>
>
>
> Is there syntax for this or would I have to put this in an image recipe or the multiconfig .conf file?
>
> Thanks, Matt.
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#62161): https://lists.yoctoproject.org/g/yocto/message/62161 <https://lists.yoctoproject.org/g/yocto/message/62161>
> Mute This Topic: https://lists.yoctoproject.org/mt/103747116/5052612 <https://lists.yoctoproject.org/mt/103747116/5052612>
> Group Owner: yocto+owner@lists.yoctoproject.org <mailto:yocto%2Bowner@lists.yoctoproject.org>
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub <https://lists.yoctoproject.org/g/yocto/unsub> [quaresma.jose@gmail.com <mailto:quaresma.jose@gmail.com>]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
>
> --
> Best regards,
>
> José Quaresma
prev parent reply other threads:[~2024-01-17 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 19:44 append recipe to multiconfig build from top-level local.conf mattwood2000
2024-01-16 9:34 ` [yocto] " Jose Quaresma
2024-01-17 22:43 ` Matt Wood [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ae61cfb3-ff00-4847-8fcc-5940cc31152f@gmail.com \
--to=mattwood2000@gmail.com \
--cc=quaresma.jose@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).