Yes, to clarify either: "..\testA.h" or "../testA.h" results in the "cannot find testA.H" compile error. I was just trying the unix-style directory separator on a whim and once that didn't work is when I copied/pasted for my email.
On 9/25/07, Bryan Ischo <[EMAIL PROTECTED]> wrote: > > [my apologies if this is a dup, I sent it from the wrong email address > before, and I am not sure if it would get through the list properly] > > > Probably a stupid question, but does: > > #include "..\testA.h" > > work? > > I noticed that you are using unix-style directory separators in the > #include directive that does not work, and Windows-style directory > separators in the #include directive that does work. Could this point to > the problem? > > If so, does this mean that gccxml has a bug? I'm not sure, I don't know > exactly what the C++ standard says about how paths have to be constructed > in #include directives; I personally always use unix-style paths there and > have never had a problem (even on Windows). > > Thanks, > Bryan > > > > > ------------------------------------------------------------------------ > Bryan Ischo [EMAIL PROTECTED] 2001 Mazda 626 GLX > Hamilton, New Zealand http://www.ischo.com RedHat Fedora Core 5 > ------------------------------------------------------------------------ > > >
_______________________________________________ gccxml mailing list [email protected] http://www.gccxml.org/mailman/listinfo/gccxml
