I was using a response file with POLINK and I noticed I could only use short path names with /LIBPATH. Is it supposed to do that? I'm using POLINK 4.00.0.
This didn't work:
/DEBUG
/DEBUGTYPE:CV
/LIBPATH:"C:\Program Files\PellesC\Lib"
/LIBPATH:"C:\Program Files\PellesC\Lib\Win"
/SUBSYSTEM:CONSOLE
This worked:
/DEBUG
/DEBUGTYPE:CV
/LIBPATH:C:\PROGRA~1\PellesC\Lib
/LIBPATH:C:\PROGRA~1\PellesC\Lib\Win
/SUBSYSTEM:CONSOLE
For long names with embedded spaces you have to quote the entire option:
"/LIBPATH:C:\Program Files\PellesC\Lib"
Pelle
Quote from: "Pelle"For long names with embedded spaces you have to quote the entire option:
"/LIBPATH:C:\Program Files\PellesC\Lib"
Pelle
No offense Pelle... but, unless all the other options have to be quoted too... Greg's way makes a lot more sense.
Certainly I wouldn't have blundered onto the current method without you mentioning it...
I use the argv array for the arguments - which is parsed by the C startup code. The startup code will only make a single argument when the whole string is quoted. The handle /option:"string with spaces" I would have to use GetCommandLine(), or something similar, and do my own parsing. Lots of additional code for absolutely no good reason. You just have to learn to move the quote in front of the option. It's only need for handling options with embedded spaces which isn't very common.
Pelle
Pelle,
Thanks for the explanation. Now that I know how to do it, it is no problem. But, I wouldn't have thought of doing it that way.
The "C:\Program Files\" directory structure can sure be a pain sometimes.
No, it's not very obvious. I have added a page in the help file for the entire "Command line tools" section about this (the same thing applies to all of them).
I guess you have to switch to the Swedish Windows version - here we call Program Files just Program - saves some trouble... ;-)
Pelle
you can try long path tool software, it works fine for me :) good luck