1 #
   2 # Copyright (c) 2013, 2015, Oracle and/or its affiliates. All rights reserved.
   3 # DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
   4 #
   5 # This code is free software; you can redistribute it and/or modify it
   6 # under the terms of the GNU General Public License version 2 only, as
   7 # published by the Free Software Foundation.  Oracle designates this
   8 # particular file as subject to the "Classpath" exception as provided
   9 # by Oracle in the LICENSE file that accompanied this code.
  10 #
  11 # This code is distributed in the hope that it will be useful, but WITHOUT
  12 # ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
  13 # FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
  14 # version 2 for more details (a copy is included in the LICENSE file that
  15 # accompanied this code).
  16 #
  17 # You should have received a copy of the GNU General Public License version
  18 # 2 along with this work; if not, write to the Free Software Foundation,
  19 # Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
  20 #
  21 # Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
  22 # or visit www.oracle.com if you need additional information or have any
  23 # questions.
  24 #
  25 
  26 #####################################################################################
  27 #                                                                                   #
  28 # This properties file allows for a developer to override various properties used   #
  29 # when building JavaFX. Any settings you configure in the gradle.properties file    #
  30 # will have precedence over any values specified in the build script itself.        #
  31 #                                                                                   #
  32 #####################################################################################
  33 
  34 # By default, the build will 'fail fast' if the version of gradle is incompatible.
  35 # Set this flag to false to have it print a warning and try to build anyway.
  36 
  37 #GRADLE_VERSION_CHECK = false
  38 
  39 # These properties give developers the chance to skip building WebKit and/or
  40 # GStreamer. WebKit takes a fair amount of time to build (more than 50% of the
  41 # overall full build time is taken by WebKit), so allowing a developer to
  42 # selectively enable building of WebKit is important. To build WebKit or
  43 # GStreamer, uncomment the appropriate lines below.
  44 
  45 #COMPILE_WEBKIT = true
  46 #COMPILE_MEDIA = true
  47 
  48 #To disable building support for JRockit Flight Recorder, uncomment the line below
  49 
  50 #COMPILE_JFR = false
  51 
  52 # The building of JavaDoc takes time. By default we disable the building of JavaDoc
  53 # so as to speed up the time in incremental builds. Uncomment this flag in order to
  54 # build all the JavaDoc
  55 
  56 #BUILD_JAVADOC = true
  57 
  58 # The building of the javafx-src bundle takes time. By default we disable the
  59 # building of javafx-src so as to speed up the time in incremental builds.
  60 # Uncomment this flag in order to build javafx-src.zip
  61 
  62 #BUILD_SRC_ZIP = true
  63 
  64 # Specifies whether to build SDK for running unit tests
  65 # By default, it is set to true and the tests are running of the fresh-built SDK
  66 # If set to false, this flag removes main sources complication tasks and building
  67 # the whole SDK and jfxrt.jar and jars from TEST_SDK are used
  68 # Setting TEST_SDK is recommended
  69 
  70 #BUILD_SDK_FOR_TEST = false
  71 
  72 # Specifies SDK for running tests with when BUILD_SDK_FOR_TEST is set to false
  73 # By default, it is set to JDK_HOME
  74 # Developer builds are preferred, in other case systemTests would fail to compile and run
  75 # jfxrt.jar should be located at $TEST_SDK/rt/lib/ext/jfxrt.jar or $TEST_SDK/jre/lib/ext/jfxrt.jar
  76 # ant-javafx.jar and javafx-mx.jar should be located at $TEST_SDK/lib/
  77 
  78 #TEST_SDK = /path/to/sdk
  79 
  80 # Specifies whether to do a full test run or a "smoke test" run. By default we
  81 # do a smoke test run which excludes all tests that show a window or play media.
  82 # Certain long running tests might also be excluded when this is not set.
  83 
  84 #FULL_TEST = true
  85 
  86 # Specifies whether to enable robot-based visual tests when running a full test.
  87 # This flag is ignored if FULL_TEST is false.
  88 
  89 #USE_ROBOT = true
  90 
  91 # Specifies whether to run system tests that depend on AWT.
  92 # This flag is ignored if FULL_TEST is false.
  93 
  94 #AWT_TEST = false
  95 
  96 # Specifies whether or not the results of the packager tests should be
  97 # retained.  If not they will be automatically deleted.
  98 
  99 #RETAIN_PACKAGER_TESTS = false
 100 
 101 # Specifies whether or not Packager DMG tests should be run.
 102 # Mac OSX 10.7 tends to hang on automated builds with hdiutil is run,
 103 # hence the default is false.
 104 
 105 #TEST_PACKAGER_DMG = false
 106 
 107 # Specify the COMPILE_TARGETS when performing cross compiles. A Cross-Compile is
 108 # when you build for a platform other than the one you are building on. For example,
 109 # to build for Apple iOS, you would specify ios as one of the COMPILE_TARGETS.
 110 # The case is not significant. Valid cross build targets for each OS include:
 111 #
 112 #   OS             Target
 113 #  ------------------------------
 114 #   Mac             mac
 115 #   Mac             ios
 116 #   Mac             swt
 117 #   Mac             android
 118 #   Linux           linux
 119 #   Linux           armv6hf
 120 #   Linux           armv6sf
 121 #   Linux           swt
 122 #   Linux           android
 123 #   Windows         win
 124 #   Windows         swt
 125 #   Window          android
 126 #
 127 # The compile targets are listed as a comma separated list. Alternatively,
 128 # you can set COMPILE_TARGETS to "all" and every appropriate compile target
 129 # for your current machine configuration will be used. We will look up and
 130 # determine whether, for example, you have the Android tools installed and
 131 # only build Android if those tools are installed.
 132 #
 133 # If you manually specify a compile target which cannot be built, then the
 134 # build will fail. If you specify "all" then only those targets which can
 135 # be built will be attempted. For example, if your system is missing the
 136 # required toolchains for embedded builds, then armv6 builds would not
 137 # even be attempted when "all" is set.
 138 
 139 #COMPILE_TARGETS = all
 140 
 141 # The JDK_HOME must either be specified or will be inferred based on the JDK / JRE used to
 142 # execute Gradle. From the JDK_HOME are derived the JAVA, JAVAC, JAVAH, JAVADOC, and STUB_RUNTIME
 143 # properties, although each of these may be specified individually. In addition, the LIBRARY_STUB
 144 # property is derived from STUB_RUNTIME. Normally the gradle build
 145 # will work based on whatever "java" is being used to run gradle. It does this by looking for
 146 # a JDK relative to the bin/java location. However if you want to build with a different JDK than
 147 # what is used to execute Gradle, or to fix a failed attempt by the build script to locate the
 148 # JDK_HOME, you may want to specify it manually here.
 149 
 150 #JDK_HOME = /path/to/the/jdk
 151 #JAVA = /path/to/the/jdk/bin/java
 152 #JAVAC = /path/to/the/jdk/bin/javac
 153 #JAVAH = /path/to/the/jdk/bin/javah
 154 #JAVADOC = /path/to/the/jdk/bin/javadoc
 155 #STUB_RUNTIME = /path/to/the/jdk/jre
 156 #LIBRARY_STUB = /path/to/the/jdk/jre/xxx (different location depending on platform)
 157 
 158 # The generated JavaDocs contain many references to core JDK classes such as java.lang.String
 159 # and java.util.concurrent.Executor. These references are resolved via the JDK_DOCS property,
 160 # which should point to the JDK API documentation. You can override which JDK to point to here.
 161 # This follows the rules specified in the JavaDoc tool documentation. Examples are below.
 162 
 163 #JDK_DOCS = https://docs.oracle.com/javase/8/docs/api
 164 #JDK_DOCS = file:///Library/Java/JavaVirtualMachines/jdk1.8.0/Content/Home/docs/api
 165 #JDK_DOCS = relative/path/to/docs/api
 166 
 167 # Specify the build configuration: Release, Debug, or DebugNative. The default setting is Debug.
 168 
 169 #CONF = Release
 170 
 171 # Enables the use of the "use depend" feature. This speeds up incremental builds, but at the
 172 # cost of accuracy. Under normal circumstances, if you modify a single source file in the
 173 # "base" project, a near-complete recompile of the entire project is required for correctness
 174 # since that change *may* have caused other files to no longer compile / link correctly.
 175 # However, in many cases this is just additional compilation overhead because you may have
 176 # only added comments or performed some other work that didn't change the public API in any
 177 # way. By setting "use depend" to true, the build system will do more extensive analysis to
 178 # only recompile those classes directly impacted by your change. In some cases this will miss
 179 # compiling some classes that really do require recompilation and your build will be faulty.
 180 # This flag is enabled by default for command line builds. Uncomment to turn it off "use depend"
 181 
 182 #USE_DEPEND = false
 183 
 184 # Specify compiler LINT arguments. These values are defined by the javac compiler. You can
 185 # study the list of available options here https://docs.oracle.com/javase/7/docs/technotes/tools/solaris/javac.html
 186 # If LINT is empty, then no warning are generated. Otherwise, LINT should be a space or comma separated
 187 # list of names. If the name is prefixed with a '-' then that warning is removed (not used). For example:
 188 #
 189 # LINT = static try -varags
 190 #
 191 # This command would turn on the "static" and "try" warnings, but turn off the "varargs" warnings. The
 192 # special values "all" and "none" are used to turn on all recommended warnings, or turn them all off, respectively.
 193 # The default (for now) is "none" but as we clean up our warnings, we will likely change this to "all".
 194 
 195 #LINT = all
 196 
 197 # The following flag specifies whether to generate code coverage
 198 # statistics when running tests
 199 
 200 #JCOV = true
 201 
 202 # Define the number of threads to use when compiling native code. This value must be
 203 # > 0, or the build system will default to 1. If not specified, the number of compile
 204 # threads is determined based on the number of CPU cores on the machine. If this value
 205 # is too high, the amount of time servicing the threads will start slowing down your
 206 # build. Likely the optimal value is somewhat larger than the number of cores on the
 207 # machine, and playing with this value may improve build time performance.
 208 
 209 #NUM_COMPILE_THREADS = 12
 210 
 211 # When you are working from behind a proxy and attempting to access public libraries, you need
 212 # to set the proxy host and port.
 213 
 214 #systemProp.http.proxyHost=proxy.my.com
 215 #systemProp.http.proxyPort=80
 216 
 217 # In order to enable Android builds, you must specify the paths to the Android SDK and NDK.
 218 # Uncomment the two lines below and configure them to point to the right location on your system
 219 
 220 #ANDROID_SDK = /path/to/android/sdk
 221 #ANDROID_NDK = /path/to/android/ndk
 222 
 223 # The COMPILE_FLAGS_FILES defines the native compilation flags to use. Each native project
 224 # defines a pair of flags, XXX_CC_FLAGS and XXX_LINK_FLAGS as defined below:
 225 #
 226 #   Project         Flags
 227 #  -----------------------------------
 228 #   Glass           GLASS_CC_FLAGS, GLASS_LINK_FLAGS
 229 #   Decora          DECORA_CC_FLAGS, DECORA_LINK_FLAGS
 230 #   Prism           PRISM_CC_FLAGS, PRISM_LINK_FLAGS
 231 #   Prism SW        PRISM_SW_CC_FLAGS, PRISM_SW_LINK_FLAGS
 232 #   Launcher        LAUNCHER_CC_FLAGS, LAUNCHER_LINK_FLAGS
 233 #
 234 # Other projects may use CC_FLAGS and LINK_FLAGS, or may not be fully abstracted out yet.
 235 # As such, the set of flags a COMPILE_FLAGS_FILES must support will change as time goes on.
 236 # Setting a custom COMPILE_FLAGS_FILE should be something rarely done, usually by
 237 # somebody who is setting up builds for a new compile target.
 238 #
 239 # The COMPILE_FLAGS_FILES is a gradle file and is applied directly by build.gradle.
 240 # This means that the file can implement logic (if / loop / etc) and has access to all of
 241 # the properties defined for the build.
 242 #
 243 # If not specified, the appropriate COMPILE_FLAGS_FILES for the designated COMPILE_TARGETS
 244 # will be chosen automatically. For example, win.gradle will be used when compiling on
 245 # windows, and armhf.gradle will be picked up when compiling for armhf (such as for
 246 # the Raspberry PI).
 247 #
 248 # Paths for those properties that take a path should be absolute or relative paths, or they
 249 # should be full URLs. For example:
 250 #
 251 #       COMPILE_FLAGS_FILES = foo.gradle
 252 #       COMPILE_FLAGS_FILES = ../foo.gradle
 253 #       COMPILE_FLAGS_FILES = bar/foo.gradle
 254 #       COMPILE_FLAGS_FILES = file:///path/to/foo.gradle
 255 #
 256 
 257 #COMPILE_FLAGS_FILES = path/to/flags/file.gradle, path/to/flags/file2.gradle
 258 
 259 # Define settings used when creating the VersionInfo. These settings are generally left alone
 260 # by developers and set only from Hudson.
 261 
 262 #HUDSON_JOB_NAME = not_hudson
 263 #HUDSON_BUILD_NUMBER = 0000
 264 #PROMOTED_BUILD_NUMBER = 00
 265 #PRODUCT_NAME = OpenJFX
 266 
 267 # Define the default SDK path on Mac. This should need to be rarely, if ever set.
 268 
 269 # MACOSX_SDK_PATH = /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.7.sdk