So you're saying that having a space between the "-I" and your path on the
command-line is incorrect?
As for the specific issue I'm having - the first example below didn't work and
the second did:
--gccxml-config
"C:\Xxxx\Xxxxx\xxxxxxxxx\xxx\xxxxxxxxxx\dev\bin\gccxml\gccxml_config" -D
"__XX_GCCXML" -D "XX_XXXX_XX_XXXXXXX" -I
"C:\Xxxx\Xxxxx\xxxxxxxxx\dev\xxxxxxxxxx\dev\source\tool\xxx-xxxxxx" -I
"C:\Xxxx\Xxxxx\xxxxxxxxx\dev\xxxxxxxxxx\dev\source\tool" -I
"E:\Xxxxx\Xxxxx\Xxxxxxxx\" -I
"E:\Xxxxx\Xxxxx\Xxxxxxxx\XXxxxx\2.0.12\include\common" -I
"E:\XXxxx\Xxxxx\Xxxxxxxx\XxxxxxXxx\2.2.5.0-CL530685" -I
"E:\XxxxX\Xxxxx\Xxxxxxxx\XxxxxxXxx\2.2.5.0-CL530685\xxxxxxxxx"
-fxml="E:\XXxxx\Xxxxx\Xxxxxx\Xxxxxxxx\dev\Build\Xxxxxx\Xxxxxxxxxx\gccxml_XXxxxxxxxx.xml"
"E:\XXxxX\Xxxxx\Xxxxxx\Xxxxxxxx\dev\Build\Global\Xxxxxxxxxx\gccxml_XXxxxxxxxx.h"
--gccxml-config
"C:\Xxxx\Xxxxx\xxxxxxxxx\xxx\xxxxxxxxxx\dev\bin\gccxml\gccxml_config" -D
"__XX_GCCXML" -D "XX_XXXX_XX_XXXXXXX" -I
C:\Xxxx\Xxxxx\xxxxxxxxx\dev\xxxxxxxxxx\dev\source\tool\xxx-xxxxxx -I
C:\Xxxx\Xxxxx\xxxxxxxxx\dev\xxxxxxxxxx\dev\source\tool -I
E:\Xxxxx\Xxxxx\Xxxxxxxx\ -I
E:\Xxxxx\Xxxxx\Xxxxxxxx\XXxxxx\2.0.12\include\common -I
E:\XXxxx\Xxxxx\Xxxxxxxx\XxxxxxXxx\2.2.5.0-CL530685 -I
E:\XxxxX\Xxxxx\Xxxxxxxx\XxxxxxXxx\2.2.5.0-CL530685\xxxxxxxxx
-fxml="E:\XXxxx\Xxxxx\Xxxxxx\Xxxxxxxx\dev\Build\Xxxxxx\Xxxxxxxxxx\gccxml_XXxxxxxxxx.xml"
"E:\XXxxX\Xxxxx\Xxxxxx\Xxxxxxxx\dev\Build\Global\Xxxxxxxxxx\gccxml_XXxxxxxxxx.h"
Thanks again!
Tim
--- On Mon, 4/20/09, Brad King <[email protected]> wrote:
From: Brad King <[email protected]>
Subject: Re: [GCC-XML] Can't seem to get --gccxml-gcc-options to work
To: [email protected]
Cc: [email protected]
Received: Monday, April 20, 2009, 5:30 PM
Tim Cassidy wrote:
> Thanks Brad - that fixes the issue. So on the command-line it supports
having a space between the "-I" and the include path, but not in the
options file?
On the command line the space separates it into two arguments. The
options-file way to do this would be to put each on its own line:
-I
C:\Program Files\Faked Path\With\include
-I
C:\Foo\Bar\Foo\Bar\Foo\Bar\Foo\Bar\2.0.7\include\Common
-I
C:\Bar\Foo\Bar\Foo\Bar\Foo\dev\include
-I
c:\Bar\Bar\Foo\Foo\Bar\Bar\Foo\Foo\runtimetest
-I
c:\Foo\Foo\Bar\Bar\Foo\Foo\dev
This approach makes the options file trivial to parse and its syntax
easy to define. There is no need for any escaping or quoting.
> Also, does anyone know if there is a character limit on command line? I
think we were seeing things stop working at about the 600 character mark? Is
that a limitation of windows or gccxml?
The windows command line limit is just under 32K. I'm not aware of a
particular limit in gccxml though. Can you reproduce this and post
instructions?
-Brad
__________________________________________________________________
Make your browsing faster, safer, and easier with the new Internet Explorer® 8.
Optimized for Yahoo! Get it Now for Free! at
http://downloads.yahoo.com/ca/internetexplorer/_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.gccxml.org/mailman/listinfo/gccxml
