On 9/17/20 1:39 AM, gr embeter wrote: > Just for the sake of knowing, how do you reference multiconfig directories? > Do you copy them manually to $BUILDDIR/conf after setup-env is done? > I mean when I run `bitbake multiconfig:configA:core-image-minimal' > there should be "$BUILDDIR/conf/multiconfig/configA.conf" file, right?
My layer contains: my_layer/conf/multiconfig/multiconfig1.conf my_layer/conf/multiconfig/multiconfig2.conf my_layer/conf/multiconfig/multiconfig3.conf my_layer/conf/multiconfig/multiconfig4.conf My build directory: conf/bblayers.conf contains: BBLAYERS ?= " \ /scratch1/fray/xilinx/poky/meta \ /scratch1/fray/xilinx/poky/meta-poky \ /scratch1/fray/xilinx/poky/meta-yocto-bsp \ /scratch1/fray/xilinx/my_layer \ " conf/local.conf contains: BBMULTICONFIG = "multiconfig1 multiconfig2 multiconfig3 multiconfig4" ... The user is responsible for providing their own BBMULTICONFIG. However, if you want to provide a default one, you can already including the BBMULTICONFIG for the setting in your layer set. --Mark > On Thu, Sep 17, 2020 at 12:42 AM Mark Hatle > <mark.ha...@kernel.crashing.org> wrote: >> >> In my configurations, we refernce the multiconfig directories inside of our >> many >> layers. I definitely don't want the copied into the conf/* directory >> structure, >> since I don't want users modifying the prebuilt ones. >> >> --Mark >> >> On 9/16/20 12:08 PM, gr embeter wrote: >>>> Why copy this from TEMPLATECONF when they can be supplied by any layer in >>>> your BBLAYERS? >>> >>> At the stage of creating build directory I think it is logically to >>> use TEMPLATECONF both for "local.conf" and "multiconfig" >>> >>> >>> >>> >>> >>> >>> >>> >>>
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#142638): https://lists.openembedded.org/g/openembedded-core/message/142638 Mute This Topic: https://lists.openembedded.org/mt/76889431/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
