Make the "build" build profile action more intelligent
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:
parent
efd7a43c66
commit
dfd6a5c973
@ -398,7 +398,13 @@ rule DefineBuildProfile name : type : path {
|
||||
|
||||
switch $(HAIKU_BUILD_PROFILE_ACTION) {
|
||||
case "build" : {
|
||||
JAM_TARGETS = $(buildTarget) ;
|
||||
# If parameters are specified, only build those targets (under the
|
||||
# influence of the build profile).
|
||||
if $(HAIKU_BUILD_PROFILE_PARAMETERS) {
|
||||
JAM_TARGETS = $(HAIKU_BUILD_PROFILE_PARAMETERS) ;
|
||||
} else {
|
||||
JAM_TARGETS = $(buildTarget) ;
|
||||
}
|
||||
}
|
||||
|
||||
case "update" : {
|
||||
|
@ -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.
|
||||
|
Loading…
Reference in New Issue
Block a user