Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Compiler and project file changes in latest SVN.
mandrav:
A quick test showed that the code actually does quote paths with spaces.
This leads me to believe that you have setup a global (or user) variable for C::B SDK, i.e.
--- Code: ---CB_SDK=C:\Documents and Settings\yop\My Documents\Workbench\codeblocks\src
--- End code ---
So this is actually expanded without quotes...
Is this the case?
One part of the optimizations, has to do with macro expansion being performed just once, after the command-line has been generated. This would explain the change of behaviour.
Have you tried quotting the variable's value?
yop:
--- Quote from: mandrav on November 29, 2005, 09:18:41 am ---A quick test showed that the code actually does quote paths with spaces.
--- End quote ---
I also checked the source before posting and I also saw that (it would be an easy one otherwise :))
--- Quote from: mandrav on November 29, 2005, 09:18:41 am ---This leads me to believe that you have setup a global (or user) variable for C::B SDK, i.e.
--- Code: ---CB_SDK=C:\Documents and Settings\yop\My Documents\Workbench\codeblocks\src
--- End code ---
So this is actually expanded without quotes...
Is this the case?
One part of the optimizations, has to do with macro expansion being performed just once, after the command-line has been generated. This would explain the change of behaviour.
Have you tried quotting the variable's value?
--- End quote ---
Yes this seems to be the case, I do have a global variable (what an amazing feature btw), I'll try quoting this afternoon when I return from work. If that's the case though, the gobal variable has been set using the "..." button in the global variables dialog that allows you to browse to the location you want to set the global variable to, then it won't get quoted and leed to the above errors. So some of the usability of the global vars is lost (although you just have to do the quoting thingy once ;)). It's not a big deal after all, it's just a decision you have to make on the design/usability/features of the global variables.
mandrav:
--- Quote ---If that's the case though, the gobal variable has been set using the "..." button in the global variables dialog that allows...<snipped>
--- End quote ---
Yes, the subject of this topic is the change in command-line generation so we can find and fix these problems :)
Navigation
[0] Message Index
[*] Previous page
Go to full version