Ticket #3433: SharedUserBuildConfig_ReadMe.diff
File SharedUserBuildConfig_ReadMe.diff, 2.6 KB (added by , 15 years ago) |
---|
-
.ReadMe
old new 1 # UserBuildConfig ReadMe1 # SharedUserBuildConfig ReadMe 2 2 # ---------------------- 3 3 4 # UserBuildConfig can be used to customize the build according to your needs.4 # SharedUserBuildConfig can be used to customize the build according to your needs. 5 5 # If existent it is included by the build system, but it is ignored by svn. 6 # In addition to SharedUserBuildConfig, the build system supports LocalUserBuildConfig. 7 # LocalUserBuildConfig resides in your HAIKU_OUTPU_DIR, typically generated/. 8 # Values in LocalUserBuildConfig will over-write those in SharedUserBuildConfig. 6 9 # This file documents a few examples, what can be done. Don't just rename it 7 # to UserBuildConfig -- you don't want all the things to happen, that are8 # specified here. Rather create an empty UserBuildConfig and copy the lines9 # you really want, or start out with UserBuildConfig.sample.10 # to SharedUserBuildConfig -- you don't want all the things to happen, that are 11 # specified here. Rather create an empty SharedUserBuildConfig and copy the lines 12 # you really want, or start out with SharedUserBuildConfig.sample. 10 13 # Of course, noone reads ReadMe files, so they will just get an error here 11 14 # when copying it and jamming: 12 Exit You must NOT copy UserBuildConfig.ReadMe directly but use parts of it! ;15 Exit You must NOT copy SharedUserBuildConfig.ReadMe directly but use parts of it! ; 13 16 14 17 15 18 # Adjusting Build Variables 16 19 17 20 # The following variables can be configured per subdirectory (or subtree) or 18 21 # even per object file: 19 22 # 20 23 # CCFLAGS C++FLAGS DEBUG DEFINES HDRS LINKFLAGS OPTIM OPTIMIZE SYSHDRS … … switch $(HAIKU_BUILD_PROFILE) { 224 227 # jam -q @vmware update kernel 225 228 # -> Equivalent to running "jam -q update-vmware-image kernel" with the 226 229 # settings for the "vmware" profile. 227 230 # jam -q @crash mount 228 231 # -> Enters the bfs_shell mounting the image specified by the "crash" profile. 229 232 # 230 233 # Note, that the build system will automatically define the build profiles 231 234 # "image", "vmware-image", and "install", unless they are already defined in 232 # the UserBuildConfig. They correspond to the respective build profile types235 # the SharedUserBuildConfig. They correspond to the respective build profile types 233 236 # and use the values of the variables HAIKU[_VMWARE]_IMAGE_NAME, 234 237 # HAIKU_IMAGE_DIR, HAIKU_INSTALL_DIR, respectively their default values. 235 238 # "jam -q @image" will therefore be equivalent to "jam -q haiku-image". 236 239 237 240 238 241 # Creating Sourceable Shell Scripts 239 242 240 243 # If you use shell scripts (e.g. for testing) that need to access targets or