On Thu, 2008-07-03 at 09:45 -0400, Christopher Friedt wrote: > Hi Ned & Mike, > > I like the fix_la_files() and fix_pkgconfig_files() functions in > cross-fix-root. > > Prefixing emerge with CHOST- might be better because of tab completion - > i.e. using x86_64-pc-linux-gnu-[tab] would give you several results > including gcc, emerge, etc. At least it would be more uniform in any > case and uniformity makes it much easier to incorporate into other code. > > If your changes were incorporated into crossdev, so that the wrappers > were automatically generated per-toolchain (or even if symlinks were > made and $0 was checked), that would be awesome.
Here is the updated version which does all that. http://dev.gentoo.org/~solar/embedded/crossdev-wrappers-20080622.ebuild > Chris > > Mike Frysinger wrote: > > On Sunday 22 June 2008, Ned Ludd wrote: > >> On Sat, 2008-06-21 at 23:29 -0400, Mike Frysinger wrote: > >>> On Saturday 21 June 2008, Ned Ludd wrote: > >>> for the configure tests, ive been meaning to investigate switching over > >>> to a config.site rather than exporting them through the environment ... > >> I'll see what I can snag from here. > >> https://dev.openwrt.org/browser/trunk/include/site (hate traq) > >> Any tips/links to some others? > > > > it's just an idea i had floating around. havent actually looked into > > implementation details. but if another project is already maintaining the > > site files, then we should push our little differences to them and then > > just > > start using their work ;). > > > >>> for the CHOST, how about checking $0 ? so people can symlink like: > >>> x86_64-pc-linux-gnu-emerge and then they can just run that without > >>> needing anything set in the > >>> environment ... that's how i generally multiplex my cross scripts for > >>> multiple targets. > >> I have it right now as emerge-CHOST. > >> I figured the logic there that CHOST-* should be mostly > >> reserved for the toolchain, plus it's easier for me to emerge-\t\t and > >> pull in the right wrapper foo for whatever I'm working on. > > > > i think having it all be CHOST- prefixed rather than suffixed is better for > > consistency. or just provide both :). > > > >> When you run emerge-wrapper --init > >> it sets up all the symlink love which would probably be run a > >> pkg_postinst(). > > > > i mean when you do `crossdev FOO`, it'll create symlinks in /usr/bin/ to > > the > > wrappers already ... no need for the user to run any other commands in the > > default case ... > > > > cant really divine what targets need what love from a pkg_postinst() > > > >>> we could have crossdev manage the symlinks automatically as well so they > >>> get the ...-emerge and ...-pkg-config by default. and setup the > >>> PORTAGE_CONFIGROOT too ... > >> Yep that's what it does. I'll move the pkg over to usr/share/crossdev/ > >> Got a crossdev in cvs/svn some place so I can create a ./wrappers > >> subdir? > > > > ive been lazy and maintaining crossdev in $FILESDIR ... if you want to ask > > robbat2 for a crossdev git or svn, we can transition to that. > > -mike -- [email protected] mailing list
