|
1 ############################################################################### |
|
2 # Copyright (c) 2003, 2006 IBM Corporation and others. |
|
3 # All rights reserved. This program and the accompanying materials |
|
4 # are made available under the terms of the Eclipse Public License v1.0 |
|
5 # which accompanies this distribution, and is available at |
|
6 # http://www.eclipse.org/legal/epl-v10.html |
|
7 # |
|
8 # Contributors: |
|
9 # IBM Corporation - initial API and implementation |
|
10 ############################################################################### |
|
11 ##################### |
|
12 # Parameters describing how and where to execute the build. |
|
13 # Typical users need only update the following properties: |
|
14 # baseLocation - where things you are building against are installed |
|
15 # bootclasspath - The base jars to compile against (typicaly rt.jar) |
|
16 # configs - the list of {os, ws, arch} configurations to build. |
|
17 # |
|
18 # Of course any of the settings here can be overridden by spec'ing |
|
19 # them on the command line (e.g., -DbaseLocation=d:/eclipse |
|
20 |
|
21 #The type of the top level element we are building, generally "feature" |
|
22 topLevelElementType = feature |
|
23 #The id of the top level element we are building |
|
24 #TODO - no docs on exactly what this is - ideally this is type product and id com.nokia.carbide.cpp.product. |
|
25 # if it needs to be a feature, we may need to create a "master" feature which just includes all of the |
|
26 # features we use in the product. of course, that's what the product.xml does. :) |
|
27 topLevelElementId = com.nokia.carbide.cpp |
|
28 |
|
29 # this is set to work around bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=237922 |
|
30 launcherIcons=${buildDirectory}/plugins/com.nokia.carbide.cpp/icons/Carbide_c_flat.ico |
|
31 |
|
32 ############# PRODUCT/PACKAGING CONTROL ############# |
|
33 product=product.xml |
|
34 runPackager=true |
|
35 |
|
36 #Set the name of the archive that will result from the product build. |
|
37 #archiveNamePrefix= |
|
38 |
|
39 # The prefix that will be used in the generated archive. |
|
40 archivePrefix=eclipse |
|
41 |
|
42 # The location underwhich all of the build output will be collected. |
|
43 collectingFolder=${archivePrefix} |
|
44 |
|
45 # The list of {os, ws, arch} configurations to build. This |
|
46 # value is a '&' separated list of ',' separate triples. For example, |
|
47 # configs=win32,win32,x86 & linux,motif,x86 |
|
48 # By default the value is *,*,* |
|
49 #configs = *, *, * |
|
50 configs=win32, win32, x86 |
|
51 |
|
52 #configs=linux,gtk,x86 |
|
53 #configs=win32, win32, x86 & \ |
|
54 # linux, gtk, ppc &\ |
|
55 # linux, gtk, x86 & \ |
|
56 # linux, gtk, x86_64 & \ |
|
57 # linux, motif, x86 & \ |
|
58 # solaris, motif, sparc & \ |
|
59 # solaris, gtk, sparc & \ |
|
60 # aix, motif, ppc & \ |
|
61 # hpux, motif, PA_RISC & \ |
|
62 # macosx, carbon, ppc |
|
63 |
|
64 # By default PDE creates one archive (result) per entry listed in the configs property. |
|
65 # Setting this value to true will cause PDE to only create one output containing all |
|
66 # artifacts for all the platforms listed in the configs property. |
|
67 # To control the output format for the group, add a "group, group, group - <format>" entry to the |
|
68 # archivesFormat. |
|
69 #groupConfigurations=true |
|
70 |
|
71 #The format of the archive. By default a zip is created using antZip. |
|
72 #The list can only contain the configuration for which the desired format is different than zip. |
|
73 #archivesFormat=win32, win32, x86 - antZip& \ |
|
74 # linux, gtk, ppc - antZip &\ |
|
75 # linux, gtk, x86 - antZip& \ |
|
76 # linux, gtk, x86_64 - antZip& \ |
|
77 # linux, motif, x86 - antZip& \ |
|
78 # solaris, motif, sparc - antZip& \ |
|
79 # solaris, gtk, sparc - antZip& \ |
|
80 # aix, motif, ppc - antZip& \ |
|
81 # hpux, motif, PA_RISC - antZip& \ |
|
82 # macosx, carbon, ppc - antZip |
|
83 archivesFormat =\ |
|
84 win32, win32, x86-zip &\ |
|
85 linux, gtk, x86-zip &\ |
|
86 *,*,*-zip |
|
87 |
|
88 #Set to true if you want the output to be ready for an update jar (no site.xml generated) |
|
89 #outputUpdateJars = true |
|
90 |
|
91 #Set to true for Jnlp generation |
|
92 #codebase should be a URL that will be used as the root of all relative URLs in the output. |
|
93 #generateJnlp=false |
|
94 #jnlp.codebase=<codebase url> |
|
95 #jnlp.j2se=<j2se version> |
|
96 #jnlp.locale=<a locale> |
|
97 #jnlp.generateOfflineAllowed=true or false generate <offlineAllowed/> attribute in the generated features |
|
98 #jnlp.configs=${configs} #uncomment to filter the content of the generated jnlp files based on the configuration being built |
|
99 |
|
100 #Set to true if you want to sign jars |
|
101 #signJars=false |
|
102 #sign.alias=<alias> |
|
103 #sign.keystore=<keystore location> |
|
104 #sign.storepass=<keystore password> |
|
105 |
|
106 # Used to sign Rgml |
|
107 signJars=false |
|
108 sign.keystore=${buildDirectory}/plugins/com.nokia.carbide.rgml/.jarsign/.carbidestore |
|
109 sign.keypass=ca8913 |
|
110 sign.storepass=ca1399 |
|
111 sign.alias=carbide |
|
112 |
|
113 #Arguments to send to the zip executable |
|
114 zipargs= |
|
115 |
|
116 #Arguments to send to the tar executable |
|
117 tarargs= |
|
118 |
|
119 #Control the creation of a file containing the version included in each configuration - on by default |
|
120 #generateVersionsLists=false |
|
121 |
|
122 ############## BUILD NAMING CONTROL ################ |
|
123 # The directory into which the build elements are fetched and where |
|
124 # the build takes place. |
|
125 buildDirectory=.build |
|
126 |
|
127 # Type of build. Used in naming the build output. Typically this value is |
|
128 # one of I, N, M, S, ... |
|
129 buildType=I |
|
130 |
|
131 # ID of the build. Used in naming the build output. |
|
132 buildId=Carbide.c |
|
133 |
|
134 # Label for the build. Used in naming the build output |
|
135 #buildLabel=${buildType}.${buildId} |
|
136 buildLabel=${buildId} |
|
137 |
|
138 # Timestamp for the build. Used in naming the build output |
|
139 timestamp=007 |
|
140 |
|
141 #The value to be used for the qualifier of a plugin or feature when you want to override the value computed by pde. |
|
142 #The value will only be applied to plugin or features indicating build.properties, qualifier = context |
|
143 #forceContextQualifier=<the value for the qualifier> |
|
144 |
|
145 #Enable / disable the generation of a suffix for the features that use .qualifier. |
|
146 #The generated suffix is computed according to the content of the feature |
|
147 #generateFeatureVersionSuffix=true |
|
148 |
|
149 ############# BASE CONTROL ############# |
|
150 # Settings for the base Eclipse components and Java class libraries |
|
151 # against which you are building. |
|
152 # Base location for anything the build needs to compile against. For example, |
|
153 # in most RCP app or a plug-in, the baseLocation should be the location of a previously |
|
154 # installed Eclipse against which the application or plug-in code will be compiled and the RCP delta pack. |
|
155 |
|
156 #base=.tools |
|
157 #baseLocation=${base}/eclipse |
|
158 #Os/Ws/Arch/nl of the eclipse specified by baseLocation |
|
159 baseos=win32 |
|
160 basews=win32 |
|
161 #baseos=linux |
|
162 #basews=gtk |
|
163 basearch=x86 |
|
164 |
|
165 #this property indicates whether you want the set of plug-ins and features to be considered during the build to be limited to the ones reachable from the features / plugins being built |
|
166 filteredDependencyCheck=false |
|
167 |
|
168 #this property indicates whether the resolution should be done in development mode (i.e. ignore multiple bundles with singletons) |
|
169 resolution.devMode=false |
|
170 |
|
171 #pluginPath is a list of locations in which to find plugins and features. This list is separated by the platform file separator (; or :) |
|
172 #a location is one of: |
|
173 #- the location of the jar or folder that is the plugin or feature : /path/to/foo.jar or /path/to/foo |
|
174 #- a directory that contains a /plugins or /features subdirectory |
|
175 #- the location of a feature.xml, or for 2.1 style plugins, the plugin.xml or fragment.xml |
|
176 #pluginPath= |
|
177 |
|
178 skipBase=true |
|
179 eclipseURL=<url for eclipse download site> |
|
180 eclipseBuildId=<Id of Eclipse build to get> |
|
181 eclipseBaseURL=${eclipseURL}/eclipse-platform-${eclipseBuildId}-win32.zip |
|
182 |
|
183 |
|
184 ############# MAP FILE CONTROL ################ |
|
185 # This section defines CVS tags to use when fetching the map files from the repository. |
|
186 # If you want to fetch the map file from repository / location, change the getMapFiles target in the customTargets.xml |
|
187 |
|
188 skipMaps=true |
|
189 mapsRepo=:pserver:user1@ascvs01.americas.nokia.com:/n |
|
190 mapsRoot=debug/eclipse/workspace/maps |
|
191 mapsCheckoutTag=HEAD |
|
192 |
|
193 #tagMaps=true |
|
194 mapsTagTag=v${buildId} |
|
195 |
|
196 |
|
197 ############ REPOSITORY CONTROL ############### |
|
198 # This section defines properties parameterizing the repositories where plugins, fragments |
|
199 # bundles and features are being obtained from. |
|
200 |
|
201 # The tags to use when fetching elements to build. |
|
202 # By default thebuilder will use whatever is in the maps. |
|
203 # This value takes the form of a comma separated list of repository identifier (like used in the map files) and the |
|
204 # overriding value |
|
205 # For example fetchTag=CVS=HEAD, SVN=v20050101 |
|
206 fetchTag=HEAD |
|
207 skipFetch=true |
|
208 |
|
209 |
|
210 ############# JAVA COMPILER OPTIONS ############## |
|
211 # The location of the Java jars to compile against. Typically the rt.jar for your JDK/JRE |
|
212 # jce.jar is required by com.nokia.carbide.bugreport |
|
213 bootclasspath=${java.home}/lib/rt.jar;${java.home}/lib/jce.jar |
|
214 |
|
215 # specific JRE locations to compile against. These values are used to compile bundles specifying a |
|
216 # Bundle-RequiredExecutionEnvironment. Uncomment and set values for environments that you support |
|
217 #CDC-1.0/Foundation-1.0= /path/to/rt.jar |
|
218 #CDC-1.1/Foundation-1.1= |
|
219 #OSGi/Minimum-1.0= |
|
220 #OSGi/Minimum-1.1= |
|
221 #JRE-1.1= |
|
222 #J2SE-1.2= |
|
223 #J2SE-1.3= |
|
224 #J2SE-1.4= |
|
225 #J2SE-1.5= |
|
226 #JavaSE-1.6= |
|
227 #PersonalJava-1.1= |
|
228 #PersonalJava-1.2= |
|
229 #CDC-1.0/PersonalBasis-1.0= |
|
230 #CDC-1.0/PersonalJava-1.0= |
|
231 #CDC-1.1/PersonalBasis-1.1= |
|
232 #CDC-1.1/PersonalJava-1.1= |
|
233 |
|
234 # Specify the output format of the compiler log when eclipse jdt is used |
|
235 logExtension=.log |
|
236 |
|
237 # Whether or not to include debug info in the output jars |
|
238 javacDebugInfo=on |
|
239 |
|
240 # Whether or not to fail the build if there are compiler errors |
|
241 javacFailOnError=true |
|
242 |
|
243 # Enable or disable verbose mode of the compiler |
|
244 javacVerbose=false |
|
245 |
|
246 # Extra arguments for the compiler. These are specific to the java compiler being used. |
|
247 #compilerArg= |
|
248 |
|
249 # Default value for the version of the source code. This value is used when compiling plug-ins that do not set the Bundle-RequiredExecutionEnvironment or set javacSource in build.properties |
|
250 javacSource=1.5 |
|
251 |
|
252 # Default value for the version of the byte code targeted. This value is used when compiling plug-ins that do not set the Bundle-RequiredExecutionEnvironment or set javacTarget in build.properties. |
|
253 javacTarget=1.5 |
|
254 |
|
255 # this is supposed to work to generated the meta data for the product, but there are problems |
|
256 # with it so commenting out for now. we manually call the p2 meta data generator after building |
|
257 # the product. note that the current problem with this is that it generates a path from the build |
|
258 # server in the meta data, so when you use the director, it puts an asbuild1 specific path in the |
|
259 # config.ini file and the product doesn't launch. we're also able to pass -compress on the command |
|
260 # line which basically gives us a repository that's essentially an update site without the site.xml. |
|
261 # I don't see a similar option that can be specified here. |
|
262 #generate.p2.metadata = true |
|
263 #p2.metadata.repo = file:${repoDirectory} |
|
264 #p2.artifact.repo = file:${repoDirectory} |
|
265 #p2.metadata.repo.name = Carbide.c++ Metadata Repository |
|
266 #p2.artifact.repo.name = Carbide.c++ Artifact Repository |
|
267 #p2.flavor = tooling |
|
268 #p2.publish.artifacts = true |
|
269 |
|
270 # From: http://help.eclipse.org/stable/index.jsp?topic=/org.eclipse.pde.doc.user/tasks/pde_individual_source.htm |
|
271 # Generating Individual Source Bundles |
|
272 # PDE/Build can automatically generate individual source bundles, but only in a headless build. |
|
273 # Individual soure bundle geneation can be turned on by specifying: |
|
274 individualSourceBundles=true |
|
275 # This must be specified in the build configuration's top level build.properties file and it |
|
276 # controls all source generation for that build. See Generating Source Features and Plug-ins |
|
277 # http://help.eclipse.org/stable/topic/org.eclipse.pde.doc.user/tasks/pde_source_generation.htm |
|
278 # for details on generating traditional source plug-ins and features, the remainder of this |
|
279 # page assumes familiarity with traditional source generation. |