>I too use a Gentoo host for Gumstix development, although I am still=20
>running the Gumstix "buildroot" environment rather than the "native"=20
>Gentoo cross-development chain. I think you're overly optimistic about=20
>Portage on Cygwin, though. I've pulsed the gentoo-cygwin mailing list a
>few times over the past year or so and gotten no encouragement
I don't have a windows host to try portage/cygwin on, I'm only basing
this on an entry I've read on the Gentoo wiki. If you think this is
unlikely then fair enough.
>Are you looking at the complete Gentoo cross-development toolchain? Are
>you on the Gentoo-embedded mailing list?
Yes, I'm using crossdev to produce my toolchain. I'm currently limited
to gcc 3.4.6 as 4.1.x fails to build uclibc. Yes, I'm subscribed to the
Gentoo Embedded list - it's not very busy. :-)
>The ability to make "tbz2" binary packages is built into Portage and=20
>they can be emerged just like a source package, etc. There is also=20
>Catalyst. Catalyst is Gentoo's release engineering tool set. It can
>LiveCDs, but it also can make a "stage4" tarball. That's essentially a=20
>whole OS -- you boot a minimal Linux into ramdisk, partition the
>with the filesystems the way you want them, unpack the tarball to the=20
>filesystems, chroot into the filesystems and you're in Gentoo, Portage=20
My aim is to not require a stage tar-ball at all, but to allow users to
simply do an "emerge system" to build up a basic root filesystem. I'm
not sure about the tbz2 binary packages Gentoo produces; I believe they
only contain the package. You need portage to install them and I'd
rather not include portage on the gumstix (It has a rather heavy-weight
dependency tree). If you need a build-host to install a package, you
might as well just stick to source packages.
I glanced at Catalyst when I started, however I don't think it's
suitable for cross-development.
>I would think a Gentoo LiveCD would be hopelessly slow for a
cross->development machine, as would a VMware Gentoo running on a
Windows box. I >don't do much of any kind of development on Windows, so
I don't know what >the "right answer" is. That's why we have scripting
I'm currently using a minimal Gentoo image which I chroot into on a
Fedora Core host, which I use to generate root filesystem images for x86
targets. It works pretty well, although it can get a bit confusing as
I'm basically using 3 root filesystems: The host system (Fedora core in
my case), a build system (the small Gentoo system I chroot into) and the
target system (Embedded Gentoo that actually ends up on the target).
There's no drop is build speed, although I'm sure there would be if you
started using vmware or a ram-disk based liveCD instead.