annotate gradle.properties @ 3746:4aa29e84eb5e

Fix RT-30254: PixelReader fails for grayscale JPEG images
author flar <James.Graham@oracle.com>
date Tue, 28 May 2013 14:03:46 -0700
parents 2a81b0ed9704
children 06379693010c
rev   line source
richard@3156 1 #
richard@3156 2 # Copyright (c) 2013, Oracle and/or its affiliates. All rights reserved.
richard@3156 3 # DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
richard@3156 4 #
richard@3156 5 # This code is free software; you can redistribute it and/or modify it
richard@3156 6 # under the terms of the GNU General Public License version 2 only, as
richard@3156 7 # published by the Free Software Foundation. Oracle designates this
richard@3156 8 # particular file as subject to the "Classpath" exception as provided
richard@3156 9 # by Oracle in the LICENSE file that accompanied this code.
richard@3156 10 #
richard@3156 11 # This code is distributed in the hope that it will be useful, but WITHOUT
richard@3156 12 # ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
richard@3156 13 # FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
richard@3156 14 # version 2 for more details (a copy is included in the LICENSE file that
richard@3156 15 # accompanied this code).
richard@3156 16 #
richard@3156 17 # You should have received a copy of the GNU General Public License version
richard@3156 18 # 2 along with this work; if not, write to the Free Software Foundation,
richard@3156 19 # Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
richard@3156 20 #
richard@3156 21 # Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
richard@3156 22 # or visit www.oracle.com if you need additional information or have any
richard@3156 23 # questions.
richard@3156 24 #
richard@3156 25
richard@3156 26 #####################################################################################
richard@3156 27 # #
richard@3156 28 # This properties file allows for a developer to override various properties used #
richard@3156 29 # when building JavaFX. In general you should not edit this file directly, but #
richard@3156 30 # rather, copy it into your ~/.gradle/ directory (into a file also called #
richard@3156 31 # gradle.properties). Any settings you configure there will have precedence over #
richard@3156 32 # any values specified in the build script itself or in the gradle.properties #
richard@3156 33 # file in the project directory. #
richard@3156 34 # #
richard@3156 35 #####################################################################################
richard@3156 36
richard@3156 37 # These properties give developers the chance to skip building WebKit and/or
richard@3156 38 # GStreamer. WebKit takes a fair amount of time to build (more than 50% of the
richard@3156 39 # overall full build time is taken by WebKit), so allowing a developer to
richard@3156 40 # selectively enable building of WebKit is important. To build WebKit or
richard@3156 41 # GStreamer, uncomment the appropriate lines below.
richard@3156 42
richard@3156 43 #COMPILE_WEBKIT = true
richard@3156 44 #COMPILE_GSTREAMER = true
richard@3156 45
rbair@3458 46 # Specify the COMPILE_TARGETS when performing cross compiles. A Cross-Compile is
richard@3156 47 # when you build for a platform other than the one you are building on. For example,
rbair@3458 48 # to build for Apple iOS, you would specify ios as one of the COMPILE_TARGETS.
rbair@3458 49 # The case is not significant. Valid cross build targets for each OS include:
richard@3156 50 #
richard@3156 51 # OS Target
richard@3156 52 # ------------------------------
richard@3156 53 # Mac mac
richard@3156 54 # Mac ios
richard@3156 55 # Mac swt
richard@3156 56 # Linux linux
rbair@3458 57 # Linux armv6hf
rbair@3458 58 # Linux armv6sf
richard@3156 59 # Linux swt
richard@3156 60 # Windows win
richard@3156 61 # Windows swt
rbair@3458 62 #
rbair@3458 63 # The compile targets are listed as a comma separated list. Alternatively,
rbair@3458 64 # you can set COMPILE_TARGETS to "all" and every appropriate compile target
rbair@3458 65 # for your current machine configuration will be used. We will look up and
rbair@3458 66 # determine whether, for example, you have the Android tools installed and
rbair@3458 67 # only build Android if those tools are installed.
rbair@3458 68 #
rbair@3458 69 # If you manually specify a compile target which cannot be built, then the
rbair@3458 70 # build will fail. If you specify "all" then only those targets which can
rbair@3458 71 # be built will be attempted. For example, if your system is missing the
rbair@3458 72 # required toolchains for embedded builds, then armv6 builds would not
rbair@3458 73 # even be attempted when "all" is set.
richard@3156 74
rbair@3458 75 #COMPILE_TARGETS = all
richard@3156 76
richard@3156 77 # The JDK_HOME must either be specified or will be inferred based on the JDK / JRE used to
richard@3156 78 # execute Gradle. From the JDK_HOME are derived the JAVA, JAVAC, JAVAH, JAVADOC, and BINARY_STUB
richard@3156 79 # properties, although each of these may be specified individually. Normally the gradle build
richard@3156 80 # will work based on whatever "java" is being used to run gradle. It does this by looking for
richard@3156 81 # a JDK relative to the bin/java location. However if you want to build with a different JDK than
richard@3156 82 # what is used to execute Gradle, or to fix a failed attempt by the build script to locate the
richard@3156 83 # JDK_HOME, you may want to specify it manually here.
richard@3156 84
richard@3156 85 #JDK_HOME = /path/to/the/jdk
richard@3156 86 #JAVA = /path/to/the/jdk/bin/java
richard@3156 87 #JAVAC = /path/to/the/jdk/bin/javac
richard@3156 88 #JAVAH = /path/to/the/jdk/bin/javah
richard@3156 89 #JAVADOC = /path/to/the/jdk/bin/javadoc
richard@3156 90 #BINARY_STUB = /path/to/the/jdk/jre/lib/ext/jfxrt.jar
richard@3156 91
richard@3156 92 # The generated JavaDocs contain many references to core JDK classes such as java.lang.String
richard@3156 93 # and java.util.concurrent.Executor. These references are resolved via the JDK_DOCS property,
richard@3156 94 # which should point to the JDK API documentation. You can override which JDK to point to here.
richard@3156 95 # This follows the rules specified in the JavaDoc tool documentation. Examples are below.
richard@3156 96
richard@3156 97 #JDK_DOCS = http://download.oracle.com/javase/7/docs/api
richard@3156 98 #JDK_DOCS = file:///Library/Java/JavaVirtualMachines/jdk1.8.0/Content/Home/docs/api
richard@3156 99 #JDK_DOCS = relative/path/to/docs/api
richard@3156 100
richard@3156 101 # Specify the build configuration (Release or Debug). The default setting is Release.
richard@3156 102
richard@3156 103 #CONF = Debug
richard@3156 104
richard@3156 105 # Enables the use of the "use depend" feature. This speeds up incremental builds, but at the
richard@3156 106 # cost of accuracy. Under normal circumstances, if you modify a single source file in the
richard@3156 107 # "base" project, a near-complete recompile of the entire project is required for correctness
richard@3156 108 # since that change *may* have caused other files to no longer compile / link correctly.
richard@3156 109 # However, in many cases this is just additional compilation overhead because you may have
richard@3156 110 # only added comments or performed some other work that didn't change the public API in any
richard@3156 111 # way. By setting "use depend" to true, the build system will do more extensive analysis to
richard@3156 112 # only recompile those classes directly impacted by your change. In some cases this will miss
richard@3156 113 # compiling some classes that really do require recompilation and your build will be faulty.
richard@3156 114 # This flag is disabled by default for command line builds. Uncomment to make use of "use depend"
richard@3156 115
richard@3156 116 #USE_DEPEND = true
richard@3156 117
richard@3156 118 # Specify compiler LINT arguments. These values are defined by the javac compiler. You can
richard@3156 119 # study the list of available options here http://docs.oracle.com/javase/7/docs/technotes/tools/solaris/javac.html
richard@3156 120 # If LINT is empty, then no warning are generated. Otherwise, LINT should be a space or comma separated
richard@3156 121 # list of names. If the name is prefixed with a '-' then that warning is removed (not used). For example:
richard@3156 122 #
richard@3156 123 # LINT = static try -varags
richard@3156 124 #
richard@3156 125 # This command would turn on the "static" and "try" warnings, but turn off the "varargs" warnings. The
richard@3156 126 # special values "all" and "none" are used to turn on all recommended warnings, or turn them all off, respectively.
richard@3156 127 # The default (for now) is "none" but as we clean up our warnings, we will likely change this to "all".
richard@3156 128
richard@3156 129 #LINT = all
richard@3156 130
richard@3156 131 # Define the number of threads to use when compiling native code. This value must be
richard@3156 132 # > 0, or the build system will default to 1. If not specified, the number of compile
richard@3156 133 # threads is determined based on the number of CPU cores on the machine. If this value
richard@3156 134 # is too high, the amount of time servicing the threads will start slowing down your
richard@3156 135 # build. Likely the optimal value is somewhat larger than the number of cores on the
richard@3156 136 # machine, and playing with this value may improve build time performance.
richard@3156 137
richard@3156 138 #NUM_COMPILE_THREADS = 12
richard@3156 139
richard@3156 140 # The COMPILE_FLAGS_FILE defines the native compilation flags to use. Each native project
richard@3156 141 # defines a pair of flags, XXX_CC_FLAGS and XXX_LINK_FLAGS as defined below:
richard@3156 142 #
richard@3156 143 # Project Flags
richard@3156 144 # -----------------------------------
richard@3156 145 # Glass GLASS_CC_FLAGS, GLASS_LINK_FLAGS
richard@3156 146 # Decora DECORA_CC_FLAGS, DECORA_LINK_FLAGS
richard@3156 147 # Prism PRISM_CC_FLAGS, PRISM_LINK_FLAGS
richard@3156 148 # Prism SW PRISM_SW_CC_FLAGS, PRISM_SW_LINK_FLAGS
richard@3156 149 # Launcher LAUNCHER_CC_FLAGS, LAUNCHER_LINK_FLAGS
richard@3156 150 #
richard@3156 151 # Other projects may use CC_FLAGS and LINK_FLAGS, or may not be fully abstracted out yet.
richard@3156 152 # As such, the set of flags a COMPILE_FLAGS_FILE must support will change as time goes on.
richard@3156 153 # Setting a custom COMPILE_FLAGS_FILE should be something rarely done, usually by
richard@3156 154 # somebody who is setting up builds for a new compile target.
richard@3156 155 #
richard@3156 156 # The COMPILE_FLAGS_FILE is a gradle file and is applied directly by build.gradle.
richard@3156 157 # This means that the file can implement logic (if / loop / etc) and has access to all of
richard@3156 158 # the properties defined for the build.
richard@3156 159 #
richard@3156 160 # If not specified, the appropriate COMPILE_FLAGS_FILE for the designated COMPILE_TARGET
richard@3156 161 # will be chosen automatically. For example, win.gradle will be used when compiling on
richard@3156 162 # windows, and armhf.gradle will be picked up when compiling for armhf (such as for
richard@3156 163 # the Raspberry PI).
richard@3156 164 #
richard@3156 165 # Paths for those properties that take a path should be absolute or relative paths, or they
richard@3156 166 # should be full URLs. For example:
richard@3156 167 #
richard@3156 168 # COMPILE_FLAGS = foo.gradle
richard@3156 169 # COMPILE_FLAGS = ../foo.gradle
richard@3156 170 # COMPILE_FLAGS = bar/foo.gradle
richard@3156 171 # COMPILE_FLAGS = file:///path/to/foo.gradle
richard@3156 172 #
richard@3156 173
richard@3156 174 #COMPILE_FLAGS_FILE = path/to/flags/file.gradle
richard@3156 175
richard@3156 176 # Define the programs to use for compiling and linking native code. The values specified
richard@3156 177 # here will take precedence over those specified in the COMPILE_FLAGS_FILE. This can
richard@3156 178 # sometimes lead to errors if the designated compiler cannot handle both C / C++ files,
richard@3156 179 # and may also require manipulating the compiler parameters. In general, it is recommended
richard@3156 180 # that you supply a custom COMPILE_FLAGS_FILE and set the CC / LINK paths there.
richard@3156 181
richard@3156 182 #CC = g++
richard@3156 183 #LINK = g++
richard@3156 184
richard@3156 185 # Define settings used when creating the VersionInfo. These settings are generally left alone
richard@3156 186 # by developers and set only from Hudson. We have to manually rev this version number from
richard@3156 187 # release to release.
richard@3156 188
richard@3156 189 #HUDSON_JOB_NAME = not_hudson
richard@3156 190 #HUDSON_BUILD_NUMBER = 0000
richard@3156 191 #PROMOTED_BUILD_NUMBER = 00
richard@3156 192 #PRODUCT_NAME = OpenJFX
richard@3156 193 #RAW_VERSION = 8.0.0
richard@3156 194 #RELEASE_NAME = 8.0
richard@3156 195 #RELEASE_MILESTONE = ea
richard@3494 196
richard@3494 197 # Variables used when building on the Mac. These should need to be rarely, if ever set. The
richard@3494 198 # default value for MACOSX_SDK_PATH is based on the MACOSX_MIN_VERSION, so if you wanted to
richard@3494 199 # build with 10.8 instead of 10.7 you could just specify MACOSX_MIN_VERSION and the other
richard@3494 200 # settings should not need to be specified.
richard@3494 201
richard@3494 202 # MACOSX_MIN_VERSION = 10.7
richard@3494 203 # MACOSX_SDK_PATH = /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.7.sdk
richard@3494 204 # MACOSX_JDK_FRAMEWORK = /System/Library/Frameworks/JavaVM.framework