[haiku-development] Re: question on planned build system feature -- 'generated' folder naming scheme
- From: Ingo Weinhold <ingo_weinhold@xxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Fri, 30 Jan 2009 17:36:45 +0100
On 2009-01-30 at 16:54:56 [+0100], Matt Madia <mattmadia@xxxxxxxxx> wrote:
> On Fri, Jan 30, 2009 at 9:27 AM, Stephan Assmus <superstippi@xxxxxx> wrote:
> > Are you aware of the fact that you can create any folder, cd into that
> > folder and invoke the top level configure script from within that folder
> > by
> > relative path? And that way you can separate these things and already do
> > what you want to achieve. Unless I am missing something, of course.
>
> Nope, didn't know that. Though I'd still like to implement my idea
> as part of the build system.
There is a rather simple way to use an arbitrary output directory, which
works just the way it is known from auto tools based build systems. I don't
see the point of implementing the same feature another way.
Regarding the naming of the default name of the output directory. If you
encode target architecture and gcc version into the directory name, as is
jamming from the source tree won't be possible anymore. The build system
would have to find the output directory by trying all architecture and gcc
version combinations. Which might not result in the desired behavior, if one
has several output directories.
CU, Ingo
Other related posts:
