From 5dd0ee30434314ecb938c2d126597096c1f11396 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Norbert=20Pl=F6tt?= Date: Wed, 6 Sep 2006 08:15:04 +0000 Subject: [PATCH] Changing binary -> ascii committed some changes prematurely. Reverting to the content of Rev. 1.27 --- .../schema/buildDefinitions.exsd | 22 ------------------- 1 file changed, 22 deletions(-) diff --git a/build/org.eclipse.cdt.managedbuilder.core/schema/buildDefinitions.exsd b/build/org.eclipse.cdt.managedbuilder.core/schema/buildDefinitions.exsd index ef9fc8138ea..4b659291571 100644 --- a/build/org.eclipse.cdt.managedbuilder.core/schema/buildDefinitions.exsd +++ b/build/org.eclipse.cdt.managedbuilder.core/schema/buildDefinitions.exsd @@ -423,18 +423,6 @@ - - - - Toolchains like Cygwin based Gnu tools can accept paths which are not valid for the OS platform. E.g. "/usr/include" 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's own pathConverter. In this case the pathConverter supplied by the toolchain is ignored. - - - - - - @@ -703,16 +691,6 @@ The pathConverter of a toolchain applies for all tools of the toolchain except i - - - - Tools like Cygwin based Gnu tools can accept paths which are not valid for the OS platform. E.g. "/usr/include" 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. - - - - - -