Open StLoch opened 14 years ago
Will that fuck up the way the system currently copies ruby scripts over to some directory? Could we perhaps just have a rule somewhere high-level in the project that does a tree-copy of all the ruby scripts to their appropriate destinations?
Oh, nah. The scripts are already next to their counterparts on disk and the layout in XCode doesn't matter to anything except the developer. Any changes to the group setup won't break stuff in the copy operations.
How does the copy operation work, exactly? I was under the impression that importing scripts to that project directory added them to a build step that copied the scripts someplace useful by the binary.
The target a file is associated with and the group it is displayed in and the folder it lives on in disk are all handled separately. As long as xcode can find the file on disk and it is associated with the Mountainhome target's copy phase, we're good.
It's getting annoying switching around all over the place in the XCode groups. We just need to stick the bound objects and their scripts together.