From 5cf4415ddee91a16e3059f6fb558bd030fa74796 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Norbert=20Pl=F6tt?= Date: Tue, 12 Sep 2006 06:59:35 +0000 Subject: [PATCH] Documenation for bug #156187 (PathEntry framework should handle cygwin style paths on Windows) --- .../Managed_Build_Extensibility.html | 45 +++++++++++++++++++ 1 file changed, 45 insertions(+) diff --git a/doc/org.eclipse.cdt.doc.isv/guide/mbs/extensibilityGuide/Managed_Build_Extensibility.html b/doc/org.eclipse.cdt.doc.isv/guide/mbs/extensibilityGuide/Managed_Build_Extensibility.html index d7025e159f8..511143d5954 100644 --- a/doc/org.eclipse.cdt.doc.isv/guide/mbs/extensibilityGuide/Managed_Build_Extensibility.html +++ b/doc/org.eclipse.cdt.doc.isv/guide/mbs/extensibilityGuide/Managed_Build_Extensibility.html @@ -1534,6 +1534,24 @@ the schema table below.

style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top">no + + optionPathConverter + + +

The name of a class that implements + IOptionPathConverter. Some tools like Cygwin on Windows understand non-standard paths, e.g. "/usr/local/include" + which are not valid on the platform itself and cannot be understood by CDT's PathEntry framework. + The path converter will be called each time when a tool's include or library path settings + are evaluated for use by PathEntry and can change the given path to a platform-compatible format.
+ An optionPathConverter can be defined globally per toolchain or per tool. + When path translation is required the tool is asked for it's optionPathConverter. + If a converter is defined for the tool it will be used and override any toolchain settings. + If a converter is not defined on the tool, the tool will ask it's toolchain for a converter. + + no

3.6 Builder

@@ -2585,6 +2603,33 @@ Gnu C compiler, or g++ for the Gnu C++ compiler.

no

+ + + +

optionPathConverter

+ + +

The name of a class that implements + IOptionPathConverter. Some tools like Cygwin on Windows understand non-standard paths, e.g. "/usr/local/include" + which are not valid on the platform itself and cannot be understood by CDT's PathEntry framework. + The path converter will be called each time when a tool's include or library path settings + are evaluated for use by PathEntry and can change the given path to a platform-compatible format.
+ If a path converter is not defined on the tool, the tool will also ask it's toolchain for a path converter. + + +

no

+ + + + + +

3.9