On Sat, 2010-07-10 at 18:19 +0200, Frans Meulenbroeks wrote: > This patch introduces COMPATIBLE_TARGET_SYS > It is similar to COMPATIBLE_MACHINE but where COMPATIBLE_MACHINE > is used to specify that a certain recipe is for a certain machine > COMPATIBLE_TARGET_SYS can be used to specify that a certain recipe > is for a certain architecture. > > Signed-off-by: Frans Meulenbroeks <[email protected]>
Per our IRC discussion, I am still not totally comfortable with introducing this extra overhead to all users of base.bbclass. In the vast majority of cases (i.e. essentially all packages apart from toolchain ones), TARGET_SYS == HOST_SYS and hence checking both of them is just a waste of time. But I do take your point about wanting to mop up both cross and regular gcc. I think I would prefer to see the TARGET_SYS check placed in some common place which can be included by all toolchain recipes (and, possibly, a general ongoing effort to reduce the number of non-cross recipes which refer explicitly to TARGET_xx when HOST_xx would do). But I don't have a very strong view on the matter and, if there is a general consensus in favour of putting this in base.bbclass, I will go along with that. p. _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
