| Actually, I think I just found a work-around. I'm storing the application name in a variable. The library and framework search paths take this as it's typed, so I can escape the space. However, I can't do this for an actual application name, or for shell scripts. I have a second version of the variable that is unescaped, and I use one of the two where appropriate. So, far, this appears to be compiling correctly.
Hank Schultz Cedrus Corporation
On Nov 11, 2005, at 1:32 PM, William H. Schultz wrote: On Nov 10, 2005, at 11:43 AM, Chris Espinosa wrote: Here are some commonly-reported issues that are known with this release of Xcode.
• Spaces in project path items Any build setting that contains a path (or includes another build setting that resolves to a path) must be enclosed in double quotes if the path is likely to contain a space character. Xcode will handle the quoted value correctly, but will fail if an unquoted value resolves to a path that includes a space.
This still doesn't seem to be working correctly. It's better, but incomplete. I put quotes around the one path in my library search path, and it retains the quotes when I close the project. However, I have two directories in my framework search path, and the quotes aren't retained here. I tried putting the quotes around one or both (individually, of course), and the quotes aren't retained when the project is closed.
Am I missing something?
Hank Schultz Cedrus Corporation
|
