Re: [gentoo-dev] BUILDROOT concept (was Re: [gentoo-dev] ROOT variable)

[Paul Smith]

%% david@×××××××××.com writes:

  d> see catalyst snapshots model.  Specify whatever custom portage tree
  d> you want to your hearts content.

Catalyst is very interesting, but I feel that the chroot model, which is
what Catalyst is based on, is fundamentally not the correct choice for
cross-compilation setups.  As I mentioned in a previous message,
requiring chroot means that you have to figure out a way to put hosted
tools into your target image, including a complete host-based base
operating system with glibc, shells, make, and an entire common command
set since most makefiles invoke many different UNIX commands, and that's
not even mentioning the actual cross-compiler itself.

Using a chroot model is probably the most expedient way to handle
creating an embedded filesystem FOR THE SAME ARCHITECTURE, but it's not
flexible enough (IMO) to handle creating a completely general embedded
system.


I fully realize that Portage flexibility is only one part, some might
even say a small part, of the complexity of this project (as Paul points
out).

Nevertheless, it is in many ways the _first_ part, since without this
you can't really get anywhere.  I was hoping we could tackle solving
this basic problem first.

-- 
-------------------------------------------------------------------------------
 Paul D. Smith <psmith@××××××××××××××.com>   HASMAT--HA Software Mthds & Tools
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
   These are my opinions---Nortel Networks takes no responsibility for them.

--
gentoo-dev@g.o mailing list