On Fri, 2008-06-27 at 00:54 +0200, Beber wrote: > Le samedi 21 juin à 08:33:57, « Ned Ludd » à écrit : > > > Mike, > > > > Ok with how you have SYSROOT + ROOT + PORTAGE_CONFIG working I think > > I've been able to come up with a decent set of cross compile wrappers > > that should be usable by everybody for the ideal cross compile setups. > > No more of the 'xmerge' foo. This should do it right. > > > > I want you to review.. And then tell me if it should be apart of > > crossdev or another pkg. > > > > Thanks in advance. > > > > http://dev.gentoo.org/~solar/embedded/cross-wrappers-20080621.tar.bz2 > > That's really nice. I started something like that some days ago, and > found the idea of integrating this in crossdev is something I smell > fine :) > > Also, I've a regret, which take me a lot to think about is the > separation of SYSROOT for DEPENDS and RDEPENDS. > > Here, SYSROOT is always /usr/${CHOST} which is fine to build system but > not to have an image of what you'll get (Or if you want build multiple > different system with same CHOST, different config, packages, debug > level or anything else). Yes, you can apply filter when building > initrd/fs/whatever, but that could benefic to don't have to. Same note > for PORTAGE_CONFIGROOT. > > Any plan to achieve this ? > > Any interesment of what I did to "wrap" that ?
Thats how the my old wrappers behaved more or less. But SYSPOOP kinda locks us into using it. Thus having unique ROOT's with unique USE= flags is a bit of a pita. But when following the SYSROOT system everything worse pretty well. It's kinda a trade off. -- [email protected] mailing list
