XCode2.1; because stuff breaking is fun

#1 OK, So I'm pretty heavily unimpressed. On further documentation poking:

Quote:Within the build directory, Xcode maintains separate subdirectories for each different build configuration defined by the project. In this way, changing the active build configuration does not require you to clean and rebuild the active target.

...

BUILT_PRODUCTS_DIR: The path to the folder that contains built productsor symbolic links to themfor all targets in a project. By default, this is $(SYMROOT)/$(CONFIGURATION) . You can use this build setting in a Run Script build phase to refer to the built products for each target, even if those products reside in different places in the file system, as in an install build.

This build setting is read-only; you should not modify it.

In conclusion, IT'S A FEATURE, and YOU CAN'T CHANGE IT.

In the meantime, I've put a symlink in TorqueGameEngineSDK called "Development" that points to "example", and have the build target dir one up; ie, my build target dir is now "/Users/chunky/Desktop/TorqueGameEngineSDK".

It's exactly the flithy hack I was hoping to avoid, but apple appear to have decided this one for me. It works, but it's crappy.

Gary (-;

#2 Yeah, ran up against that today, myself. It does indeed suck.
As far as I can tell, your idea of aliases named Development, Deployment and Default, all actually pointing to the example directory is the only fix I was able to find today.

Kindof a bummer, but thanks for the fix!
/Paul

#3 No custome build action were you can cp the binary to a final resting place a'la visual studio?

#4 @Ron: In theory, yes. In practice, I find that no less ugly a hack than my way of doing it, and it adds something to break when I move to a different place, or a different machine, or ... or... or...

Gary (-;

#5 Its a feature and you CAN change it. What i do is name a configuration based on a project. For example i make a configuration called examples, for Torque samples, and put (or link) the files to that directory under build. I also have emaga from 3D programming all in one book, and I have a third for my personal project. This makes management easier for me because I just select active build, and it will build to that folder and having that folder reference in Xcode makes access to the files much faster. If you want to look at the configurations from Xcode go Project->Edit Project Settings->Configuration. The only real limitation to this is that they still are created under the build, and you have to manually tweak compiler settings for deployment.

Your Milage May Vary
Mark Kromis

#6 @Mark: Well, renaming one of the configurations would have been fine too, except then I have another configuration...

Actually, I've changed my directory tree somewhat now, in case anyone's curious.

Basically, I removed anything and everything from "example" that represents compiled type stuff; all .dsos, all object files and temporary build stuff, and binaries and bundles.

I created two new directory trees; one called "Development" and one called "Deployment". The contents of these two trees is a hard link farm from example into them. For a quick easy script to do it, clear out example, and do this:

cd Desktop/TorqueGameEngineSDK/example
for f in Development Deployment
do
  mkdir ../$f
  find . -type d -exec mkdir -p ../$f/{} \;
  find . -type f -exec ln -f {} ../$f/{} \;
done

Make sure you don't create console.log, .dsos, or other relevant stuff in "example", but make all your modifications to torquescript /et al/ in example. It will be reflected in the other configurations. If you add files to example, re-run that script.

Gary (-;

#7 @all
Since this is gonna be a hassle for everyone who uses TGE on Xcode2.1, I'm thinking there ought to be a quick & easy 'official' fix for this. I've come up with a little script that will solve the issue for most people, and should be very easy to customize for individual projects:

#!/bin/bash
if [ -e build ]; then
        mv build build-old-'date "+%m.%d.%C%y-%H.%M.%S"'
fi
mkdir build
cd build
ln -s ../../example Default
ln -s ../../example Development
ln -s ../../example Deployment

It makes symlinks ( unix's version of an alias ) that point to the example directory. You can then move your Torque installation to other parts of your hard drive without fouling the links.

Small caveat: this means that if you're using Xcode2.1, you no longer change the project's build products location to "../example", you just run the script as a one - time setup operation.

Ok, that's it.
Thoughts?