view gradle.properties @ 3784:582edfecdb04

imported patch gradle-builders
author kcr
date Sat, 01 Jun 2013 08:00:37 -0700
parents 2a81b0ed9704
children 06379693010c
line wrap: on
line source
#
# Copyright (c) 2013, Oracle and/or its affiliates. All rights reserved.
# DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
#
# This code is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License version 2 only, as
# published by the Free Software Foundation.  Oracle designates this
# particular file as subject to the "Classpath" exception as provided
# by Oracle in the LICENSE file that accompanied this code.
#
# This code is distributed in the hope that it will be useful, but WITHOUT
# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
# FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
# version 2 for more details (a copy is included in the LICENSE file that
# accompanied this code).
#
# You should have received a copy of the GNU General Public License version
# 2 along with this work; if not, write to the Free Software Foundation,
# Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
#
# Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
# or visit www.oracle.com if you need additional information or have any
# questions.
#

#####################################################################################
#                                                                                   #
# This properties file allows for a developer to override various properties used   #
# when building JavaFX. In general you should not edit this file directly, but      #
# rather, copy it into your ~/.gradle/ directory (into a file also called           #
# gradle.properties). Any settings you configure there will have precedence over    #
# any values specified in the build script itself or in the gradle.properties       #
# file in the project directory.                                                    #
#                                                                                   #
#####################################################################################

# These properties give developers the chance to skip building WebKit and/or
# GStreamer. WebKit takes a fair amount of time to build (more than 50% of the
# overall full build time is taken by WebKit), so allowing a developer to
# selectively enable building of WebKit is important. To build WebKit or
# GStreamer, uncomment the appropriate lines below.

#COMPILE_WEBKIT = true
#COMPILE_GSTREAMER = true

# Specify the COMPILE_TARGETS when performing cross compiles. A Cross-Compile is
# when you build for a platform other than the one you are building on. For example,
# to build for Apple iOS, you would specify ios as one of the COMPILE_TARGETS.
# The case is not significant. Valid cross build targets for each OS include:
#
#   OS             Target
#  ------------------------------
#   Mac             mac
#   Mac             ios
#   Mac             swt
#   Linux           linux
#   Linux           armv6hf
#   Linux           armv6sf
#   Linux           swt
#   Windows         win
#   Windows         swt
#
# The compile targets are listed as a comma separated list. Alternatively,
# you can set COMPILE_TARGETS to "all" and every appropriate compile target
# for your current machine configuration will be used. We will look up and
# determine whether, for example, you have the Android tools installed and
# only build Android if those tools are installed.
#
# If you manually specify a compile target which cannot be built, then the
# build will fail. If you specify "all" then only those targets which can
# be built will be attempted. For example, if your system is missing the
# required toolchains for embedded builds, then armv6 builds would not
# even be attempted when "all" is set.

#COMPILE_TARGETS = all

# The JDK_HOME must either be specified or will be inferred based on the JDK / JRE used to
# execute Gradle. From the JDK_HOME are derived the JAVA, JAVAC, JAVAH, JAVADOC, and BINARY_STUB
# properties, although each of these may be specified individually. Normally the gradle build
# will work based on whatever "java" is being used to run gradle. It does this by looking for
# a JDK relative to the bin/java location. However if you want to build with a different JDK than
# what is used to execute Gradle, or to fix a failed attempt by the build script to locate the
# JDK_HOME, you may want to specify it manually here.

#JDK_HOME = /path/to/the/jdk
#JAVA = /path/to/the/jdk/bin/java
#JAVAC = /path/to/the/jdk/bin/javac
#JAVAH = /path/to/the/jdk/bin/javah
#JAVADOC = /path/to/the/jdk/bin/javadoc
#BINARY_STUB = /path/to/the/jdk/jre/lib/ext/jfxrt.jar

# The generated JavaDocs contain many references to core JDK classes such as java.lang.String
# and java.util.concurrent.Executor. These references are resolved via the JDK_DOCS property,
# which should point to the JDK API documentation. You can override which JDK to point to here.
# This follows the rules specified in the JavaDoc tool documentation. Examples are below.

#JDK_DOCS = http://download.oracle.com/javase/7/docs/api
#JDK_DOCS = file:///Library/Java/JavaVirtualMachines/jdk1.8.0/Content/Home/docs/api
#JDK_DOCS = relative/path/to/docs/api

# Specify the build configuration (Release or Debug). The default setting is Release.

#CONF = Debug

# Enables the use of the "use depend" feature. This speeds up incremental builds, but at the
# cost of accuracy. Under normal circumstances, if you modify a single source file in the
# "base" project, a near-complete recompile of the entire project is required for correctness
# since that change *may* have caused other files to no longer compile / link correctly.
# However, in many cases this is just additional compilation overhead because you may have
# only added comments or performed some other work that didn't change the public API in any
# way. By setting "use depend" to true, the build system will do more extensive analysis to
# only recompile those classes directly impacted by your change. In some cases this will miss
# compiling some classes that really do require recompilation and your build will be faulty.
# This flag is disabled by default for command line builds. Uncomment to make use of "use depend"

#USE_DEPEND = true

# Specify compiler LINT arguments. These values are defined by the javac compiler. You can
# study the list of available options here http://docs.oracle.com/javase/7/docs/technotes/tools/solaris/javac.html
# If LINT is empty, then no warning are generated. Otherwise, LINT should be a space or comma separated
# list of names. If the name is prefixed with a '-' then that warning is removed (not used). For example:
#
# LINT = static try -varags
#
# This command would turn on the "static" and "try" warnings, but turn off the "varargs" warnings. The
# special values "all" and "none" are used to turn on all recommended warnings, or turn them all off, respectively.
# The default (for now) is "none" but as we clean up our warnings, we will likely change this to "all".

#LINT = all

# Define the number of threads to use when compiling native code. This value must be
# > 0, or the build system will default to 1. If not specified, the number of compile
# threads is determined based on the number of CPU cores on the machine. If this value
# is too high, the amount of time servicing the threads will start slowing down your
# build. Likely the optimal value is somewhat larger than the number of cores on the
# machine, and playing with this value may improve build time performance.

#NUM_COMPILE_THREADS = 12

# The COMPILE_FLAGS_FILE defines the native compilation flags to use. Each native project
# defines a pair of flags, XXX_CC_FLAGS and XXX_LINK_FLAGS as defined below:
#
#   Project         Flags
#  -----------------------------------
#   Glass           GLASS_CC_FLAGS, GLASS_LINK_FLAGS
#   Decora          DECORA_CC_FLAGS, DECORA_LINK_FLAGS
#   Prism           PRISM_CC_FLAGS, PRISM_LINK_FLAGS
#   Prism SW        PRISM_SW_CC_FLAGS, PRISM_SW_LINK_FLAGS
#   Launcher        LAUNCHER_CC_FLAGS, LAUNCHER_LINK_FLAGS
#
# Other projects may use CC_FLAGS and LINK_FLAGS, or may not be fully abstracted out yet.
# As such, the set of flags a COMPILE_FLAGS_FILE must support will change as time goes on.
# Setting a custom COMPILE_FLAGS_FILE should be something rarely done, usually by
# somebody who is setting up builds for a new compile target.
#
# The COMPILE_FLAGS_FILE is a gradle file and is applied directly by build.gradle.
# This means that the file can implement logic (if / loop / etc) and has access to all of
# the properties defined for the build.
#
# If not specified, the appropriate COMPILE_FLAGS_FILE for the designated COMPILE_TARGET
# will be chosen automatically. For example, win.gradle will be used when compiling on
# windows, and armhf.gradle will be picked up when compiling for armhf (such as for
# the Raspberry PI).
#
# Paths for those properties that take a path should be absolute or relative paths, or they
# should be full URLs. For example:
#
#       COMPILE_FLAGS = foo.gradle
#       COMPILE_FLAGS = ../foo.gradle
#       COMPILE_FLAGS = bar/foo.gradle
#       COMPILE_FLAGS = file:///path/to/foo.gradle
#

#COMPILE_FLAGS_FILE = path/to/flags/file.gradle

# Define the programs to use for compiling and linking native code. The values specified
# here will take precedence over those specified in the COMPILE_FLAGS_FILE. This can
# sometimes lead to errors if the designated compiler cannot handle both C / C++ files,
# and may also require manipulating the compiler parameters. In general, it is recommended
# that you supply a custom COMPILE_FLAGS_FILE and set the CC / LINK paths there.

#CC = g++
#LINK = g++

# Define settings used when creating the VersionInfo. These settings are generally left alone
# by developers and set only from Hudson. We have to manually rev this version number from
# release to release.

#HUDSON_JOB_NAME = not_hudson
#HUDSON_BUILD_NUMBER = 0000
#PROMOTED_BUILD_NUMBER = 00
#PRODUCT_NAME = OpenJFX
#RAW_VERSION = 8.0.0
#RELEASE_NAME = 8.0
#RELEASE_MILESTONE = ea

# Variables used when building on the Mac. These should need to be rarely, if ever set. The
# default value for MACOSX_SDK_PATH is based on the MACOSX_MIN_VERSION, so if you wanted to
# build with 10.8 instead of 10.7 you could just specify MACOSX_MIN_VERSION and the other
# settings should not need to be specified.

# MACOSX_MIN_VERSION = 10.7
# MACOSX_SDK_PATH = /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.7.sdk
# MACOSX_JDK_FRAMEWORK = /System/Library/Frameworks/JavaVM.framework