On Apr 14, 2006, at 1:05 PM, Greg Link wrote: Xcode User's Group - By chance, I had instantiated a build configuration "Development/GenProfile", so that I didn't have to change the internal build setting every time I wanted to do an iterative rebuild. I just now noticed that the build products are placed into the directory
<ProjectRoot>/build/Development/GenProfile/
rather than something along the lines of
<ProjectRoot>/build/Development&GenProfile/
which would allow things to work a bit better, in my case, as my scripts would still be able to find the directory (and expect a fixed number of upper-level directories in their relative paths).
Is this intentional behavior, so developers can have buildsetting subdirectories, (and thus there should be some sort of warning when editing build configurations that you're about to make a sub-directory), or should the tool convert "/" characters in build configuration titles to something more file-system friendly?
Unfortunately using any Unix metacharacters in project, target, or configuration names (or any Xcode build settings, for that matter) is a) not prevented by the IDE and b) basically troublesome. The characters involved include /, ., .., *, ~, etc. as well as constructs like $(VAR) and ${VAR}.
The escaping you suggest is not useful, as that's an HTML convention, not a shell convention. There are ways to quote and escape shell metacharacters and we'll do a better job of it in the future, but for now try to avoid using them in project, target, and file names.
Chris |