| "space" character between option and argument - howto? [message #162742] |
Mon, 30 January 2006 17:45  |
Eclipse User |
|
|
|
Originally posted by: stenny.gmx.de
Hello,
I'm just developing a tiny CDT plugin to support my cross compilation
tool chain in the managed make environment.
With that, I'm having difficulties defining command line options to the
tools, which require som sort of parameter and a space separating the
option and the parameter.
Just one example:
With most C-Compilers, include paths are given in this way
"-I/path/to/include".
In the CDT plugin, I define an option with the command being "-I" and
the type being an includePath and the browseType set to "directory".
Now I need a similar setup for special include paths. Th C-Compiler I
have to use supports the option "-sys_include_directory
/path/to/include". It definitely needs the space between option and
path. How do I specify options, which are separated from their arguments
by a space?
thanks
stefan
|
|
|
|
| Re: "space" character between option and argument - howto? [message #162818 is a reply to message #162760] |
Tue, 31 January 2006 16:24  |
| Eclipse User |
|
|
|
Originally posted by: stenny.gmx.de
Norbert Ploett wrote:
> Hi Stefan,
>
> surely you have already noticed the "CDT Extensibility Document" (Menu
> Help --> Contents -->CDT Plugin Developers Guide --> Programmer's Guide -->
> Managed Build System Extensibility Document
>
> The "option" element is described in section 3.13, and in the big table in
> 3.13.4 ("Schema") it says:
>
> command
> An optional value that specifies the actual command that will be passed
> to the tool on the command line. The command provides a "pattern" for
> specifying where the value should be placed for options of type string and
> stringlist. The pattern can contain the replaceable variable "value". If
> no ${value} is specified in the command, the option value is appended to the
> end of the specified command.
>
>
>
> So you could try to specify
>
> "-sys_include_directory "
>
> (note the blank behind -sys_include_directory) or, even more explicitly
>
> "-sys_include_directory ${value}"
>
thanks a lot ...
meanwhile I discovered, that thorough reading of the documentation can
effectively avoid such questions.
The setting "-sys_include_directory ${value}" does exactly, what I expect.
Thank you
stefan
|
|
|
Powered by
FUDForum. Page generated in 0.03280 seconds
Home