| 1 |
On Saturday 21 June 2008, Ned Ludd wrote: |
| 2 |
> Ok with how you have SYSROOT + ROOT + PORTAGE_CONFIG working I think |
| 3 |
> I've been able to come up with a decent set of cross compile wrappers |
| 4 |
> that should be usable by everybody for the ideal cross compile setups. |
| 5 |
> No more of the 'xmerge' foo. This should do it right. |
| 6 |
|
| 7 |
for pkg-config, you may want to merge many of the things ive done here: |
| 8 |
http://blackfin.uclinux.org/gf/project/uclinux-dist/scmsvn/?action=browse&path=%2Ftrunk%2Ftools%2Fstaging-pkg-config&revision=5937&view=markup |
| 9 |
|
| 10 |
for the configure tests, ive been meaning to investigate switching over to a |
| 11 |
config.site rather than exporting them through the environment ... |
| 12 |
|
| 13 |
you should change the shebang to #!/bin/bash for all of those since they arent |
| 14 |
POSIX ... easier that way too |
| 15 |
|
| 16 |
for the CHOST, how about checking $0 ? so people can symlink like: |
| 17 |
x86_64-pc-linux-gnu-emerge |
| 18 |
and then they can just run that without needing anything set in the |
| 19 |
environment ... that's how i generally multiplex my cross scripts for |
| 20 |
multiple targets. |
| 21 |
|
| 22 |
we could have crossdev manage the symlinks automatically as well so they get |
| 23 |
the ...-emerge and ...-pkg-config by default. and setup the |
| 24 |
PORTAGE_CONFIGROOT too ... |
| 25 |
|
| 26 |
> I want you to review.. And then tell me if it should be apart of |
| 27 |
> crossdev or another pkg. |
| 28 |
|
| 29 |
crossdev should be fine i think |
| 30 |
-mike |
Archives