> The live CD is only the runtime environment, and the entire root filesystem > is in an initrd which is mounted r/w. The build environment is an Ubuntu > 8.10 desktop install, but that's mostly irrelevant since nothing from Ubuntu > is actually used in building fltk or my app. > > See, Buildroot is building it's own toolchain (everything - compiler, all the > libraries, etc. from scratch...) -- the only thing the Ubuntu toolchain is > used for is building the Buildroot toolchain. Deep within the buildroot > make it's then building the fltk package and my package using that toolchain > and environment variables it's configuring for each package. Ultimately, > the result is an ISO image which has the generated live CD. >
I'm not familiar with Buildroot, never having used it, but I had the impression that it was mainly useful for building cross-compilation targets and so forth... e.g for using an x86 host to build an arm or mips or whatever OS image...? If so, what host platform are you targeting? Maybe that makes a difference? Don't know. If it is just an x86 target as well, then I can't help feeling that the stock Fedora or Ubuntu live-cd tools would be an awful lot simpler than what you are describing, so I assume you must be porting to something more obscure? I'm interested to know what. I got myself a beagleboard the other day, actually, to add to my ever growing collection, but haven't got round to doing anything more than booting Angstrom on it to see that the h/w is actually OK, yet... -- Ian _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
