1 |
On Friday 19 October 2007, Jason wrote: |
2 |
> If I have two projects which use the same toolchain, is it sufficient to |
3 |
> do the following? |
4 |
> |
5 |
> crossdev --target armeb-softfloat-linux-gnu |
6 |
> SYSROOT=/usr/armeb-softfloat-linux-gnu |
7 |
> |
8 |
> Set up SYSROOT with make.globals, and so on |
9 |
> |
10 |
> mkdir /usr/armeb-softfloat-linux-gnu-nslu2 |
11 |
> cp -ax /usr/armeb-softfloat-linux-gnu/* \ |
12 |
> /usr/armeb-softfloat-linux-gnu-nslu2/ |
13 |
> |
14 |
> Then repeat for the second armeb project. |
15 |
|
16 |
mmm not quite ... the SYSROOT is for the system packages which implies no |
17 |
tailoring should really be done. TGTROOT is where all customization should |
18 |
be done. if you want to do the customization in the SYSROOT, then it'd be |
19 |
better to have separate sysroots ... so something like: |
20 |
/usr/armeb-booga1_softfloat-linux-gnu/ |
21 |
/usr/armeb-booga2_softfloat-linux-gnu/ |
22 |
these are tuples that'll work with crossdev: |
23 |
crossdev --target armeb-booga1_softfloat-linux-gnu |
24 |
-mike |