Re: slight different confirurations for a package

[Philip Balister <philip@balister.org>]

[-- Attachment #1: Type: text/plain, Size: 2379 bytes --]

C Michael Sundius wrote:
> I'd like to be able to build several different configurations of the same
> package and I'm wondering if the community might have some good input on the
> best way to organize this. My project has several images that are built for
> various products and customers and hardware. Generally all of the software
> is the same save a few key packages. (really even the kernel is constant
> across all platforms). and right now I have a different disto.conf file that
> corresponds to an image recipe for each platform.
> 
> I want to be able to build all of the platforms together within the same out
> dir. (so I don't have to rebuild the bulk of the software wasting disk space
> and time).
> 
> I've thought about defining separate recipes:
>      (foo-config1.bb, foo-config2.bb)
> or simply using a variable to define ${PN} from within the recipe:
> 
>     PN = ${DISTRO_CONFIG}
> 
>  I suppose these could work, but I'm wondering if I can create a whole new
> directory under work and staging like when I set PACKAGE_ARCH =
> ${MACHINE_ARCH} for the kernel and drivers.
> 
> as I said, right now I have a separate distro/*.conf file for each image
> (and thus configuration) I build, really the difference between these is the
> configuration of just a few packages all other software is built w/ the same
> recipe and configs. Is there a way anyone can think of to consolidate these
> so I can build everything without
> changing the local.conf (DISTRO variable).

It seems like you are misunderstanding how to use DISTRO. Basically, set 
the common stuff in DISTRO and creat an image.bb file for each image you 
need.

In short, if you are creating a new distro/*.conf you are most likely 
making a mistake :)

Philip

> 
> I realize this is a nebulous question, but if anyone has an experience
> similar where they have had to organize various builds and found a clean or
> better way to build them all for both development and production or you have
> some opinions about how you made your decisions to do things one way or
> another , I'd love to hear your comments.
> 
> Thank you
> Mike
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]