Help adding new compiler; spaces in path
Posted: Sat Jul 16, 2011 12:37 am
I need to add a new compiler in Build Settings. The problem is that I cannot avoid having spaces in the path to the compiler executable (don't ask why) and CodeLite can't seem to handle that. Is there some trick that will get it to work? I've tried putting double quotes around the whole path. I've tried inserting double quotes in just the parts of the path with spaces. I've tried not using quotes, and escaping the spaces with \, but apparently MinGW interprets either \ or / as a path separator so it doesn't recognize \ as an escape.
It's a path like this:
C:\Program Files\VendorName\CompilerName CompilerFlavor Compilerversion\rest\of\path\cross-gcc.exe
Are my only options to either somehow finagle these tools into a path with no spaces, or to use a custom makefile and cygwin, which can be made to handle spaces in paths?
Hmmm... I guess a makefile that works with spaces under cygwin probably won't work as a custom build in CodeLite because CodeLite will use MinGW... so if I use a cygwin makefile with paths I cannot use the CodeLite IDE to run it?? Or can I get CodeLite to use cygwin instead of MinGW? (how?)
- jasper77
It's a path like this:
C:\Program Files\VendorName\CompilerName CompilerFlavor Compilerversion\rest\of\path\cross-gcc.exe
Are my only options to either somehow finagle these tools into a path with no spaces, or to use a custom makefile and cygwin, which can be made to handle spaces in paths?
Hmmm... I guess a makefile that works with spaces under cygwin probably won't work as a custom build in CodeLite because CodeLite will use MinGW... so if I use a cygwin makefile with paths I cannot use the CodeLite IDE to run it?? Or can I get CodeLite to use cygwin instead of MinGW? (how?)
- jasper77