On Saturday 21 June 2008, Ned Ludd wrote: > 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.
for pkg-config, you may want to merge many of the things ive done here: http://blackfin.uclinux.org/gf/project/uclinux-dist/scmsvn/?action=browse&path=%2Ftrunk%2Ftools%2Fstaging-pkg-config&revision=5937&view=markup for the configure tests, ive been meaning to investigate switching over to a config.site rather than exporting them through the environment ... you should change the shebang to #!/bin/bash for all of those since they arent POSIX ... easier that way too 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. 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 ... > I want you to review.. And then tell me if it should be apart of > crossdev or another pkg. crossdev should be fine i think -mike
signature.asc
Description: This is a digitally signed message part.
