| 1 |
On Sunday 22 June 2008, Ned Ludd wrote: |
| 2 |
> On Sat, 2008-06-21 at 23:29 -0400, Mike Frysinger wrote: |
| 3 |
> > On Saturday 21 June 2008, Ned Ludd wrote: |
| 4 |
> > for the configure tests, ive been meaning to investigate switching over |
| 5 |
> > to a config.site rather than exporting them through the environment ... |
| 6 |
> |
| 7 |
> I'll see what I can snag from here. |
| 8 |
> https://dev.openwrt.org/browser/trunk/include/site (hate traq) |
| 9 |
> Any tips/links to some others? |
| 10 |
|
| 11 |
it's just an idea i had floating around. havent actually looked into |
| 12 |
implementation details. but if another project is already maintaining the |
| 13 |
site files, then we should push our little differences to them and then just |
| 14 |
start using their work ;). |
| 15 |
|
| 16 |
> > for the CHOST, how about checking $0 ? so people can symlink like: |
| 17 |
> > x86_64-pc-linux-gnu-emerge and then they can just run that without |
| 18 |
> > needing anything set in the |
| 19 |
> > environment ... that's how i generally multiplex my cross scripts for |
| 20 |
> > multiple targets. |
| 21 |
> |
| 22 |
> I have it right now as emerge-CHOST. |
| 23 |
> I figured the logic there that CHOST-* should be mostly |
| 24 |
> reserved for the toolchain, plus it's easier for me to emerge-\t\t and |
| 25 |
> pull in the right wrapper foo for whatever I'm working on. |
| 26 |
|
| 27 |
i think having it all be CHOST- prefixed rather than suffixed is better for |
| 28 |
consistency. or just provide both :). |
| 29 |
|
| 30 |
> When you run emerge-wrapper --init |
| 31 |
> it sets up all the symlink love which would probably be run a |
| 32 |
> pkg_postinst(). |
| 33 |
|
| 34 |
i mean when you do `crossdev FOO`, it'll create symlinks in /usr/bin/ to the |
| 35 |
wrappers already ... no need for the user to run any other commands in the |
| 36 |
default case ... |
| 37 |
|
| 38 |
cant really divine what targets need what love from a pkg_postinst() |
| 39 |
|
| 40 |
> > we could have crossdev manage the symlinks automatically as well so they |
| 41 |
> > get the ...-emerge and ...-pkg-config by default. and setup the |
| 42 |
> > PORTAGE_CONFIGROOT too ... |
| 43 |
> |
| 44 |
> Yep that's what it does. I'll move the pkg over to usr/share/crossdev/ |
| 45 |
> Got a crossdev in cvs/svn some place so I can create a ./wrappers |
| 46 |
> subdir? |
| 47 |
|
| 48 |
ive been lazy and maintaining crossdev in $FILESDIR ... if you want to ask |
| 49 |
robbat2 for a crossdev git or svn, we can transition to that. |
| 50 |
-mike |
Archives