Option to create scheme files in xcode module

[mihaisebea]

Xcode will autocreate scheme files once you open the project in xocde.
But if you do not, there is no way to build only part of a workspace if you don't specify a scheme.

A solution would be this mr:
premake/premake-xcode#25

@ratzlaff , @starkos was there a reason for which this was not merged?

Should I make a new MR with this? Ideally we should specify trough a command line option or a flag if we want schemes to be generated or not.

[ratzlaff]

Oh wow, I had forgotten about that PR from three years ago!

I can only speculate as to the reasons why it was not merged. I suspect it was because it was in a submodule with low visibility and I didn't know how to use git at the time (because I did not submit a PR on the main project to merge in the submodule changes)

Ideally we should specify trough a command line option or a flag if we want schemes to be generated or not

note: I am not an xcode guru, I just keep things going so all our supported platforms here at work build and test.

The linked PR generates a shared scheme. I could not tell you why a shared scheme is necessary here, but from what I understand, it is not the same thing as the project schemes that xcode generates you describe. When I edit the scheme for a project through xcode, these shared scheme files do not change at all.

I wrote this after reverse engineering the files that xcode would create so that building my executable would also build various dylibs that were not explicit dependencies (ie: plugins). As I recall at the time (and I could be wrong about this), the shared schemes are also necessary so that building from the command line with xcodebuild does not lock up.

[starkos]

I'm not seeing any specific reason for it to not have been merged, may have just fallen through the cracks.