i2p/haiku-beta6
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Make the "build" build profile action more intelligent

Browse Source 
If additional parameters are specified, only those targets are built,
but under the influence of the build profile. E.g. "jam @alpha-raw build
haiku.hpkg" builds the package with SSL support, while "jam haiku.hpkg"
would build it without (unless explicitly enabled in UserBuildConfig).
This commit is contained in:
Ingo Weinhold
2013-10-04 00:20:53 +02:00
parent efd7a43c66
commit dfd6a5c973
2 changed files with 11 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
build/jam/UserBuildConfig.ReadMe
+4
View File
@@ -242,6 +242,10 @@ switch $(HAIKU_BUILD_PROFILE) {
# -> Equivalent to running "jam -q haiku-image" with the settings for the
# "disk" profile. "build" is the default action, so it could even be
# omitted.
# jam -q @alpha-raw build haiku.hpkg
# -> Build's haiku.hpkg under the influence of the "alpha-raw" profile. This
# is is different to "jam -q haiku.hpkg" in that the build profile may
# enable certain build features that might not be enabled by default.
# jam -q @vmware update kernel
# -> Equivalent to running "jam -q update-vmware-image kernel" with the
# settings for the "vmware" profile.