On Friday 19 October 2007, Jason wrote: > If I have two projects which use the same toolchain, is it sufficient to > do the following? > > crossdev --target armeb-softfloat-linux-gnu > SYSROOT=/usr/armeb-softfloat-linux-gnu > > Set up SYSROOT with make.globals, and so on > > mkdir /usr/armeb-softfloat-linux-gnu-nslu2 > cp -ax /usr/armeb-softfloat-linux-gnu/* \ > /usr/armeb-softfloat-linux-gnu-nslu2/ > > Then repeat for the second armeb project.
mmm not quite ... the SYSROOT is for the system packages which implies no tailoring should really be done. TGTROOT is where all customization should be done. if you want to do the customization in the SYSROOT, then it'd be better to have separate sysroots ... so something like: /usr/armeb-booga1_softfloat-linux-gnu/ /usr/armeb-booga2_softfloat-linux-gnu/ these are tuples that'll work with crossdev: crossdev --target armeb-booga1_softfloat-linux-gnu -mike
signature.asc
Description: This is a digitally signed message part.
