[haiku-development] Re: question on planned build system feature -- 'generated' folder naming scheme
- From: Matt Madia <mattmadia@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 2 Feb 2009 09:33:44 -0500
On Sat, Jan 31, 2009 at 1:30 PM, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
> I don't see why we can't add one or two sentences to the usage text
> explaining how non-default output directories work.
>
I'll gladly concede to that. How's the attached diff look? Would you
prefer this created as a ticket?
> I'm fine with working on a more comfortable
> solution for this use case,
--snip--
> After François mentioned that selecting the output directory by build profile
> would be nice, I thought a bit about it, and it could be solved by
> introducing an optional EarlyUserBuildConfig, which would be included very,
> well, early. Early enough at least that it could changed HAIKU_OUTPUT_DIR.
> Depending on what one personally prefers one could do that by build profile
> or by some additional parameter (e.g. "x86gcc2").
Does this seem like what you mean?
Note, I haven't tested this yet, so there might be some syntax or
similar errors.
haiku_src/Jamrules:
# Main directories used by the build.
...
# include EarlyUserBuildConfig
{
local earlyUserBuildConfig
= [ GLOB $(HAIKU_BUILD_RULES_DIR) : EarlyUserBuildConfig ] ;
if $(earlyUserBuildConfig) {
include $(earlyUserBuildConfig) ;
}
}
# Cache files for header scanning and jamfile caching
...
haiku_src/configure:
remove the existng HAIKU_OUTPUT_DIR from the cat << EOF > $outputDir/Jamfile
cat << EOF > $(HAIKU_TOP)/build/EarlyUserBuildConfig
HAIKU_OUTPUT_DIR = ${outputDir}
EOF
--mmadia
Other related posts:
