[coyotos-dev] Build tree input wanted

[Jonathan S. Shapiro]

On Thu, 2008-02-21 at 13:23 -0800, Charles Landau wrote:
> At 4:03 PM -0500 2/21/08, Jonathan S. Shapiro wrote:
> >3. Output files go into
> >
> >      $(COYOTOS_ROOT)/host  -- stuff for the build host machine
> >      $(COYOTOS_ROOT)/usr   -- stuff for the target machine
> >
> >   2. Does anybody have a better proposal for how to organize this?
> 
> I don't claim it's better, but in CapROS the target files go into 
> directories such as
> 
> $(EROS_ROOT)/lib/$(EROS_TARGET)/

Doing something like this as a way to support a single platform having
multiple instruction set architectures (e.g. amd64) makes quite a bit of
sense.

That is not the problem we are trying to solve here. The problem we are
trying to solve here is multiple *targets*. For example, we want to be
able to generate completely independent builds for two different boards
requiring different board support packages that use the same processor.

Also, I'm not clear whether you intend that arch-neutral files should
NOT go in these subdirectories. If they do not, it invites the
likelihood that output from one target build will be incorrectly used by
the next target build, with the result that builds might become
non-reproducible or build errors might go undiscovered.


shap