| 1 |
Hi everyone, |
| 2 |
|
| 3 |
I've set up a 'build root' that I can chroot into for cross development. |
| 4 |
There is also a directory of targets to compile for, and for each |
| 5 |
target, a series of different configurations. |
| 6 |
|
| 7 |
When I chroot into my buildroot my 'enter_chroot' script will |
| 8 |
automatically mount -o bind each of the sysroot, binpkgs, and overlay |
| 9 |
directories for a specified configuration, as well as mount -o bind the |
| 10 |
portage tree itself. |
| 11 |
|
| 12 |
So my directory structure looks something like this: |
| 13 |
|
| 14 |
gentoo-crossdev-buildroot/ |
| 15 |
enter_chroot.sh |
| 16 |
(mounts proc, mounts -o bind portage/sysroot/binpkg/overlay etc) |
| 17 |
portage/ |
| 18 |
... (the portage tree) |
| 19 |
buildroot/ |
| 20 |
... (all cross compilation tools and a stage1 filesystem) |
| 21 |
targets/ |
| 22 |
arm-9tdmi-linux-gnu/ |
| 23 |
cross-toolchain/ |
| 24 |
configurations/ |
| 25 |
reference/ |
| 26 |
overlay/ |
| 27 |
binpkgs/ |
| 28 |
sysroot/ |
| 29 |
client1/ |
| 30 |
... |
| 31 |
client2/ |
| 32 |
... |
| 33 |
arm-9tdmi-linux-uclibc/ |
| 34 |
cross-toolchain/ |
| 35 |
configurations/ |
| 36 |
reference/ |
| 37 |
overlay/ |
| 38 |
binpkgs/ |
| 39 |
sysroot/ |
| 40 |
client1/ |
| 41 |
... |
| 42 |
client2/ |
| 43 |
... |
| 44 |
|
| 45 |
What I'm hoping to do is leverage the power of portage overlays here, |
| 46 |
and make it possible to have different package customizations for each |
| 47 |
client and each platform that my company deals with. |
| 48 |
|
| 49 |
It doesn't take a lot to see that this is a great way to minimize |
| 50 |
maintenance. |
| 51 |
|
| 52 |
My problem though, is that when doing cross development (I use the |
| 53 |
xmerge scrypt and set a SYSROOT variable), I have noticed that when I |
| 54 |
set new flags in $SYSROOT/etc/portage/package.use, it's not noticed |
| 55 |
properly during emerge. |
| 56 |
|
| 57 |
I'm hoping that portage can be flexible enough to acknowlege those use |
| 58 |
flags. The xmerge script (taken from one of the gentoo cross development |
| 59 |
guides online) properly sets the PORTAGE_CONFIGROOT variable, ROOT, etc, |
| 60 |
so I don't understand why it doesn't acknowlege the changes in |
| 61 |
$SYSROOT/etc/portage/package.use. |
| 62 |
|
| 63 |
Any suggestions? |
| 64 |
|
| 65 |
|
| 66 |
Regards, |
| 67 |
|
| 68 |
~/Chris |
| 69 |
-- |
| 70 |
gentoo-embedded@g.o mailing list |
Archives