On Sat, Jul 10, 2010 at 9:23 AM, Frans Meulenbroeks <[email protected]> wrote: > 2010/7/8 Phil Blundell <[email protected]>: >> On Thu, 2010-07-08 at 08:49 +0200, Frans Meulenbroeks wrote: >>> The only concern I have is the name COMPATIBLE_TARGET >>> for me TARGET is the board so COMPATIBLE_TARGET for me more or less >>> equates to COMPATIBLE_MACHINE. >>> What about COMPATIBLE_ARCH or COMPATIBLE_ARCHITECTURE? >> >> I think the variable that you want to match against (in the specific >> case of cross.bbclass) is ${TARGET_SYS}. Having the matching variable >> be named COMPATIBLE_ARCH would imply that it's going to match >> ${HOST_ARCH}, which obviously isn't what you want. >> >> I would have thought that confusion with ${MACHINE} should be minimal >> since that nomenclature is already quite well established in OE. But >> you could name it COMPATIBLE_TARGET_SYS if you wanted to make the name >> completely explicit. >> > Patch posted. I named it COMPATIBLE_TARGET_SYS and compare with TARGET_SYS. > Tested it, and for me it works like a charm. > > However just after posting I noticed we also have TARGET_ARCH. > I'm a little bit lost wrt the differences between these. > Let me know if I need to move to *ARCH
TARGET_ARCH is the architecture e.g. arm. mips etc. TARGET_SYS is canonical name like arm-oe-linux-uclibceabi or mips-oe-linux etc. > > Frans > > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel > _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
