From: Brian M. <ma...@ex...> - 2008-07-03 17:25:56
|
Summary: Xcode seems to strongly prefer that all your Ruby files be at the top level of the resources directory. Can my preference for a source directory structure override its? Suppose I think of my app in this structure: root/ TranslatorEnlister.rb translators/ ToString.rb controllers/ util/ I can mimic that structure in Xcode groups, but as far as I can tell, the structure is always flattened to look like this: Contents/Resources/ TranslatorEnlister.rb ToString.rb This is a problem if I'm doing unit testing outside the build directory, in which case (say) TranslatorEnlister.rb would have a "require 'translators/ToString'". I can create the directories on disk, add them, and tell Xcode to create folder references instead of groups. However, Xcode's dependency checking seems to stop at the top-level folder. So if I change a file within .../translators/, Xcode doesn't copy it into the build unless I touch .../translators/ or something. Am I confused? I remember the thrill, back around 1980, of first working on an operating system that allowed a directory hierarchy. I could have two files with *the same name*. I would like to recapture that thrill with Xcode. ----- Brian Marick, independent consultant Mostly on agile methods with a testing slant www.exampler.com, www.exampler.com/blog, www.twitter.com/marick |