On Dec 7, 2005, at 7:36 AM, Steve Mills wrote: On Dec 6, 2005, at 20:33, Prachi Gauriar wrote: Following Bill's advice in this blog post has saved me a lot of trouble when it comes to build locations.
<http://www.friday.com/bbum/2004/12/05/xcode-file-references-build-locations/>
I highly recommend it putting your build products and intermediate files in /tmp somewhere.
/tmp? You've got to be kidding. tmp's contents can be deleted. I don't want my 20 minutes worth of building to suddenly go away when I least expect it.
For what it's worth, here's what I do:
I have a separate volume (not a system volume) on my machine called /Volumes/Stuff. It holds everything I want to persist whenever I need to install a new system, or boot into a different system. I create a directory there called Objects, and have a symlink to it as /Objects. Then I set my build directory to be /Objects.
Actually, I tend to have many (at least 6) check-outs of the same code base at one time, so I set each one (in the project inspector, which is per-project-per-user) to its own subdirectory, e.g. /Objects/General, /Objects/SearchPaths, or whatever other specific project that check-out is for.
I also set (in my user preferences) my intermediates directory to $(CONFIGURATION_BUILD_DIR)/Intermediates, so that all of my intermediate files go into a common subdirectory of my build directory, which keeps my build directory from getting overly cluttered.
Also, Xcode 2.2 supports expanding build settings in executables, which makes using custom executables in the face of varying build directories a lot more convenient - simply sprinkle $(BUILT_PRODUCTS_DIR) liberally wherever your executable needs to look in the current project build directory for something.
This model has worked well for me for several years. But of course your mileage may vary. :-)
--
Michael Rawdon Apple Computer, Cupertino CA
Xcode Developer email@hidden
|