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