[haiku-development] Re: development paths
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Wed, 20 Jul 2011 20:18:33 +0200
Oliver Tappe <zooey@xxxxxxxxxxxxxxx> wrote:
> On 2011-07-20 at 01:12:23 [+0200], Ingo Weinhold <ingo_weinhold@xxxxxx>
> > wrote:
> > We could even go further and introduce a /boot/common/develop/lib as
> > well
> > and change the linker library search paths to no longer include
> > /boot/common/lib.
> I'd like that, since keeping the link-time libraries separate from
> the
> runtime libraries is a good idea, IMHO.
Agreed (even though they'll probably all end up being symlinks anyway).
> > Thinking this even further it can be questioned whether
> > we want /boot/system/develop at all. If /boot/system is supposed to
> > contain
> > only the core system -- i.e. a fully self-contained minimal Haiku
> > -- then
> > the development stuff, which is optional, should go into
> > /boot/common
> > anyway.
> I don't think that /boot/system should only contain the minimal Haiku,
> but it
> should contain everything that is part of Haiku or at least very
> closely
> coupled. I consider the system (and compiler) headers to be so closely
> coupled to the system that I'd favour having them in /boot/system,
> the same
> goes for the link-time libraries.
Sounds good; I was a bit torn before, but you convinced me.
Bye,
Axel.
Other related posts:
