search

BlueFrogGaming / icuke

Integration testing for iPhone applications with Cucumber
MIT License
20 stars 3 forks source link

Xcode 4 and iCuke work-around #3

Closed rbeiter closed 13 years ago

rbeiter commented 13 years ago

I wanted to post a work-around for the changing of the simulator binary for Xcode 4 and iCuke:

If you're not married to Xcode 4's relocation of the derived data dir you can get iCuke running by going into Xcode->Preferences->Locations and set 'Build Location' to 'Place build products in locations specified by targets' - this will revert to creating a build dir at the same level as your xcode project and all will be happy.

If you'd prefer to keep the resources in the derived location, I also got iCuke to work by symlinking a directory such as this in the same dir as the project file: (Replace MyApp with YourApp's name and don't use a wildcard if Xcode has made more than one derived directory)

ln -s ~/Library/Developer/Xcode/DerivedData/MyApp-*/Build/Products build

This will symlink the uniquely named derived data location's build products dir to build and iCuke will be happy.

In a shared environment, this dir will be different for each developer. This value doesn't seem to be stored in the project anywhere but the Xcode build process is aware of it and has env varibles that point to it. One could place a custom script in the build process to create this symlink and iCuke could use it.

rbeiter commented 13 years ago

Just noticed the main page for the project also includes this info now - sorry for the dup.