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.
Working on nslu2 would set SYSROOT and TGTROOT appropriately (for me, I
have a .screenrc that sets up this build environment).
This way I could simply use two different .screenrc's for two different
projects. The way I see it, this would allow me to tailor USE flags,
package.keywords, etc per project as opposed to per toolchain. Are
there any pitfalls I'm missing with this approach?
thx,
Jason.
--
[EMAIL PROTECTED] mailing list
