You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: io.sloeber.autoBuild/schema/buildDefinitions.exsd
+30-115
Original file line number
Diff line number
Diff line change
@@ -225,6 +225,7 @@ Additional special types exist to flag options of special relevance to the build
225
225
<annotation>
226
226
<documentation>
227
227
An optional value that specifies the actual command that will be passed to the tool on the command line. The attribute value provides a "pattern" for specifying where the option "value" should be placed for options of type string and stringlist. If no ${value} is specified in the command, the option value is appended to the end of the specified command.
228
+
For booleans there is a special case. See the commandFalse description for more details
228
229
</documentation>
229
230
</annotation>
230
231
</attribute>
@@ -241,7 +242,16 @@ Additional special types exist to flag options of special relevance to the build
241
242
<attributename="commandFalse"type="string">
242
243
<annotation>
243
244
<documentation>
244
-
An optional value, used only with options of type Boolean, that specifies the actual command that will be passed to the tool on the command line when the value of the Boolean option is False.
245
+
An optional value, used only with options of type Boolean when false, that specifies the actual command that will be passed to the variable specified in assignToCommandVariable.
246
+
alternatively this can be a ; seperated list of var=value.
247
+
248
+
The only multiple command variables I can currently think of is to allows for
249
+
--start-group archives --end-group
250
+
with a command line containing ${START_LIB_GROUP} ${INTERNAl_LIBS} ${LIBS) ${END_LIB_GROUP}
251
+
In which case assignToCommandVarriables would be ignored
@@ -1228,6 +1245,15 @@ The path is relative to the plug-in directory which defines .buildDefinitions.
1228
1245
</appinfo>
1229
1246
</annotation>
1230
1247
</attribute>
1248
+
<attributename="weight"type="string">
1249
+
<annotation>
1250
+
<documentation>
1251
+
A weight specifying where in the command variable (typically FLAGS) these option categories will be put.
1252
+
The higher the weight the earlier in the command line options of this category will be placed.
1253
+
Default is 50
1254
+
</documentation>
1255
+
</annotation>
1256
+
</attribute>
1231
1257
</complexType>
1232
1258
</element>
1233
1259
@@ -1681,31 +1707,6 @@ For example, builder representing GNU make would define parallelBuildCmd as &quo
1681
1707
</complexType>
1682
1708
</element>
1683
1709
1684
-
<elementname="managedBuildRevision">
1685
-
<annotation>
1686
-
<documentation>
1687
-
<p>
1688
-
Version identifier for the Auto build extension point. It is a string representation, consisting of three (3) tokens separated by a decimal point. The 3 tokens are positive integer numbers. For example, the following are valid version identifiers:
Specifies whether the resource is excluded from building in the parent configuration. The default is false. The resourceConfiguration element retains its tool children, if any exist, even when excluded from the build.
2084
-
</documentation>
2085
-
</annotation>
2086
-
</attribute>
2087
-
</complexType>
2088
-
</element>
2089
-
2090
-
<elementname="fileInfo">
2091
-
<annotation>
2092
-
<documentation>
2093
-
Represents per-file settings.
2094
-
This element has the same meaning as resourceConfiguration.
2095
-
It is added for consistency with the folderInfo element.
2096
-
The only difference between this element and the resourceConfiguration is that resourceConfiguration specifies the resource full path, while the fileInfo specifies project-relative resource path in the same way as the folderInfo does.
2097
-
</documentation>
2098
-
</annotation>
2099
-
<complexType>
2100
-
<attributename="resourcePath"type="string">
2101
-
<annotation>
2102
-
<documentation>
2103
-
Project-relative resource path
2104
-
</documentation>
2105
-
</annotation>
2106
-
</attribute>
2107
-
<attributename="exclude"type="boolean">
2108
-
<annotation>
2109
-
<documentation>
2110
-
Specifies whether the resource is excluded from building in the parent configuration. The default is false. The resourceConfiguration element retains its tool children, if any exist, even when excluded from the build.
2111
-
</documentation>
2112
-
</annotation>
2113
-
</attribute>
2114
-
<attributename="rcbsApplicability">
2115
-
<annotation>
2116
-
<documentation>
2117
-
Identifies how the user desires to apply a resource custom build step:
2118
-
1. Apply rcbs tool before any other tools defined for the resource.
2119
-
2. Apply rcbs tool after any other tools defined for the resource.
2120
-
3. Apply rcbs tool overriding any other tools defined for the resource.
2121
-
4. Disable (don't apply) the rcbs tool.
2122
-
</documentation>
2123
-
</annotation>
2124
-
<simpleType>
2125
-
<restrictionbase="string">
2126
-
<enumerationvalue="before">
2127
-
</enumeration>
2128
-
<enumerationvalue="after">
2129
-
</enumeration>
2130
-
<enumerationvalue="override">
2131
-
</enumeration>
2132
-
<enumerationvalue="disable">
2133
-
</enumeration>
2134
-
</restriction>
2135
-
</simpleType>
2136
-
</attribute>
2137
-
<attributename="toolsToInvoke"type="string">
2138
-
<annotation>
2139
-
<documentation>
2140
-
Identifies which tools to invoke by a semicolon separated list of child tool ids. Applies as follows:
2141
-
1. Defaults to all tools in the order found
2142
-
2. Use specified ordered list of children to invoke
2143
-
3. If empty string, treat as if no resource configuration existed, i.e., use project level tool.
0 commit comments