On Mon, Feb 28, 2011 at 17:54, Phil Blundell <[email protected]> wrote: > On Mon, 2011-02-28 at 17:04 +0000, Otavio Salvador wrote: >> We have a set of products that reuse a common distro definition but >> has different needs on a small set of packages. To avoid having them >> all rebuild we set those to DISTRO_ARCH and the ones that depends on >> machine and distro to MACHINE_DISTRO_ARCH avoiding a lot of rebuilding >> and CPU time. > > That sounds to me like you're using ${DISTRO} for a purpose that was not > really intended. I do have some sympathy for the scenario you mention > but I'm not convinced that adding these new ARCHS for everyone is the > right answer. > > Obviously you're welcome to bash PACKAGE_ARCHS any way you want in your > own DISTRO.conf file and I think that's probably the right place for > this sort of thing rather than putting it in the global bitbake.conf and > causing extra complexity for everyone. Or maybe you could consider > using ${MACHINE}, which is already a PACKAGE_ARCH, to discriminate > between the different packages.
Adding it to my distro seems to solve my problem. The problem of using MACHINE is that I need it to be rebuild if DISTRO changes, hence MACHINE_DISTRO_ARCH. -- Otavio Salvador O.S. Systems E-mail: [email protected] http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
