mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-06-06 17:26:01 +02:00
Code Issues Wiki Activity

*.exsd files are actually ASCII, not binary!

Browse source
This commit is contained in:
Norbert Pltt 2006-09-06 08:09:50 +00:00
parent de527bb7cd
commit eca28bea4a
2 changed files with 2764 additions and 2742 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
build/org.eclipse.cdt.managedbuilder.core/schema/buildDefinitions.exsd
View file

@ -423,6 +423,18 @@
</documentation>
</annotation>
</attribute>
<attribute name="pathConverter" type="string">
<annotation>
<documentation>
Toolchains like Cygwin based Gnu tools can accept paths which are not valid for the OS platform. E.g. &quot;/usr/include&quot; is well difined for a Cygwin gcc compiler while it is not a meaningful path for a java.io.File. Therefore toolchains can specify a pathConverter which will be applied to include and library paths configured in the Managed Build System.
The pathConverter of a toolchain applies for all tools of the toolchain except if a tool defines it&apos;s own pathConverter. In this case the pathConverter supplied by the toolchain is ignored.
</documentation>
<appInfo>
<meta.attribute kind="java" basedOn="org.eclipse.cdt.managedbuilder.core.IPathConverter"/>
</appInfo>
</annotation>
</attribute>
</complexType>
</element>
@ -691,6 +703,16 @@
</documentation>
</annotation>
</attribute>
<attribute name="pathConverter" type="string">
<annotation>
<documentation>
Tools like Cygwin based Gnu tools can accept paths which are not valid for the OS platform. E.g. &quot;/usr/include&quot; is well difined for a Cygwin gcc compiler while it is not a meaningful path for a java.io.File. Therefore tools can specify a pathConverter which will be applied to include and library paths configured in the Managed Build System.
</documentation>
<appInfo>
<meta.attribute kind="java" basedOn="org.eclipse.cdt.managedbuilder.core.IPathConverter"/>
</appInfo>
</annotation>
</attribute>
</complexType>
</element>