3 ms·

Wait a second, if I got it right you use an external tool to generate Xcode project? So basically the external tool don't properly set the 'development team' v

by Twisell 10y ago

Wait a second, if I got it right you use an external tool to generate Xcode project? So basically the external tool don't properly set the 'development team' variable in the generated Xcode project. May I ask how this is supposed to be Apple's fault if a third party App haven't yet been updated to meet new requirements? Did you update XCode ahead of version supported by your external tool? Coming from scripting languages, I'm starting to learn pure Xcode/Cocoa/Swift workflow with a free account and I really don't relate to problems you are describing (but my target is only macOs for now, so I might miss the deployement hassle you describe I give you that)

jm547ster 10y ago
This used only be an issue with iOS as target needing paid account for development to run apps on hardware
flohofwoe 10y ago
The problem is not the external tool, cmake allows to set all Xcode project attributes just fine. The problem is that there is no automatic default for this one setting, the development team setting has to be manually set. For instance, you also cannot distribute Xcode project files now which simply compile out of the box. You'll have to go into project settings first and set the development team for every single app target. Why the development team is part of the project setting, and not simply an Xcode-wide setting in the preferences is beyond me.
- Arcanum-XIII 10y ago
  As of right now, my Xcode got access to 5 to 10 team and their project. How is he supposed to know that I want my target z go to team y ? And that this target is a store account, not the usual enterprise one for other project by the same team ? And I think cmake can add the proper account to the project too, but it's probably not well documented...
  - flohofwoe 10y ago
    I think the proper solution would be to have a 'default team' which is filled in for each target that hasn't an explicit team set. That way, Xcode project files coming with open source projects could keep the team setting empty and would still compile and deploy out of the box.

by Twisell 10y ago

jm547ster 10y ago

This used only be an issue with iOS as target needing paid account for development to run apps on hardware

flohofwoe 10y ago

The problem is not the external tool, cmake allows to set all Xcode project attributes just fine. The problem is that there is no automatic default for this one setting, the development team setting has to be manually set. For instance, you also cannot distribute Xcode project files now which simply compile out of the box. You'll have to go into project settings first and set the development team for every single app target. Why the development team is part of the project setting, and not simply an Xcode-wide setting in the preferences is beyond me.

Arcanum-XIII 10y ago
As of right now, my Xcode got access to 5 to 10 team and their project. How is he supposed to know that I want my target z go to team y ? And that this target is a store account, not the usual enterprise one for other project by the same team ? And I think cmake can add the proper account to the project too, but it's probably not well documented...
- flohofwoe 10y ago
  I think the proper solution would be to have a 'default team' which is filled in for each target that hasn't an explicit team set. That way, Xcode project files coming with open source projects could keep the team setting empty and would still compile and deploy out of the box.