[oe] [RFC] ANGSTROM_MODE -> SYSTYPE

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul Sokolovsky schreef:
> Hello Openembedded-devel,
> 
>    ANGSTROM_MODE config variable has proven to be very useful and
> successful feature during the Angstrom evolution. IMHO, it is worth
> generalization of its meaning and naming to become a generic
> additional OE distro configuration parameter. 
> So, I'd like to propose
> it to be renamed to SYSTYPE, with the description "Select particular
> system variant of a distribution which supports such feature, e.g.,
> underlying libc type."

How will a user know if that flag is supported for the distro he/she
wants to use?
should we enhance insane.bbclass to crosscheck TARGET_OS with
SYSTYPE_FOO for the uclibc vs glibc case? And if so, how would it check
between glibc and eglibc?
Having an *easier* OE-blessed way for switching C library would be nice,
but let's make sure people don't shoot themselves in the foot by setting
SYSTYPE_FOO with a distro that has no knowledge of it.

regards,

Koen


>   Obviously, it wouldn't be limited to libc type, but intended to be a
> generic sub-parameter of a distro, it could be debug/release type,
> size type (minimal/standard/extended), whatever. The usage idea is to
> have standard name for such generic parameter, plus semantically it
> should be expected that a distro allows to build different SYSTYPE's
> side-by-side in the same build dir (like Angstrom does for libc
> variants).
> 
> 


- --
koen at dominion.kabel.utwente.nl will go go away in december 2007, please
use k.kooi at student.utwente.nl instead.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHY7EoMkyGM64RGpERAh1uAJ9/QUGnhZ+4/zKUeOZSgIgMNyuwUACfYb3a
gy3s4p4svQ8M8rbFxThH+9I=
=3c7/
-----END PGP SIGNATURE-----