This is the mail archive of the
mailing list for the GCC project.
Porting from Win C++ to linux slash vs backslash
- From: barryg <bandegee at yahoo dot com>
- To: gcc-help at gcc dot gnu dot org
- Date: Tue, 14 Nov 2006 14:19:37 -0800 (PST)
- Subject: Porting from Win C++ to linux slash vs backslash
Our extensive C++ library that in the past was compiled using windows has the
following type of #include statments ...
however the gcc command line expects slashes in the other direction...
(Assume that the path is set to /home/yo and the file is in
In our example gcc will not find the file.h unless we switch the \ to / in
the #include. We'd have to change countless files to do this.
We have tried
We also looked through the gcc options for an option that says to flatten
Is there a way to do this without changing all our source files?
View this message in context: http://www.nabble.com/Porting-from-Win-C%2B%2B-to-linux-slash-vs-backslash-tf2632625.html#a7347745
Sent from the gcc - Help mailing list archive at Nabble.com.