Hi there, I'm quite sorry to annoy you, but I'm quite new to Gentoo, and the Embedded Handbook (which appears to be the best information source for what I want to do) does not make it clear for me. I hope you'll be able to help me a little.
I have a base host system, which is a x86 hardened-profiled Gentoo 10.0. I would like to use it to build target systems with the most control Gentoo can offer. I first looked at Catalyst but Cross-dev things seemed more accurate for what I want to do. Let's say I want to make a "example-v1" target system. I want my host to build on a "example-v1-build" directory everything needed to build and emerge binaries for my target system. I want my host to build with "example-v1-build" files and toolchain a "example-v1-target" directory which would contain emerged system. "example-v1-target" would contain a very minimal system, with no gcc, emerge or dev things. It just have to be able to run C/C++ binaries for a given arch. I would like to use crossdev because I want to specify which version of glibc/gcc/etc I will use for one given target. Furthermore, I would like my toolchain to build "hardened" binaries, as those we get by using an hardened stage3. I don't get the process from the Embedded Handbook. Do I have to set some CHOST, CTARGET, ROOT or PORTAGE_CONFDIR env vars or crossdev will handle that some way ? How can I tell to crossdev : "build the cross toolchain to my example-v1-build directory" ? How can I then tell to emerge "emerge and build from my example-v1-build directory to example-v1-target" ? Do I have to chroot in "example-v1-build" ? In this case wouldn't I lost all emerge capabilities ? Many thanks in advance for your help. Sorry I can't figure it all by myself despite the good docs. -- Pierre. "Sometimes when I'm talking, my words can't keep up with my thoughts. I wonder why we think faster than we speak. Probably so we can think twice." - Bill Watterson
