On Fri, Jan 23, 2009 at 01:56:38PM +0100, Juan Jose Pablos wrote:
> > 
> > I did look at buildroot, and this is what I have found so far.
> > 
> 
> What about sing a virtual machine'
> some users on this list suggested to use Virtualbox.

>From the problems that I've seen on the list, the main issues seem to be 
>related to the tool-chain and that the 
build system interacts with the host system that everything is being built on.  
Currently, some things are 
downloaded and built while other parts are used from what happens to be on the 
build system.  If all of the 
exact host requirements are met, from what I hear it just works.  However, if 
your libraries mismatch, etc. it 
doesn't work.  (That is probably why there were reports of things working just 
fine on an etch system, but not 
once it was upgraded to lenny.)

Having using a virtual machine is one way to isolate the build system for 
unattended from the host system that 
is being used.  However, you then need to provide the entire tool chain.  One 
solution would be to build a 
script that would construct a virtual system based on something like Debian.  
Then you could have a known 
system for the rest of the stuff to work in.

Another potential solution is to take some of the information from 
www.linuxfromscratch.org and 
buildroot.uclibc.org and fix the current scripts to better isolate the build 
from the host system.

> I am pretty new to the virtual stuff, but I am happy to create a virtual 
> image that can be downloaded and used in several platforms.

The advantage of the virtual image route is that it can be used on multiple 
platforms, not necessarily just 
Linux.  However, there are already others that provide this sort of thing.  
Since we don't actually run 
anything in this system once unattended is built, it might not be necessary.

My gut feeling at this moment is that the basic idea of the build script that 
is currently used is the correct 
way to go.  However, some changes to fix the "tool-chain problem" are 
necessary.  How to fix it has been solved 
by buildroot and linuxfromscratch.

If someone wants to build on Windows, they could use one of the available 
virtual linux machines and then just 
build the script like anyone else.

Allan.

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
unattended-devel mailing list
unattended-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unattended-devel

Reply via email to