thejustinwalsh
commented
9 years ago For additional info, using this script for my travis CI builds works like a charm. However, who needs ruby when we can do this as a part of the premake process.
Open thejustinwalsh opened 9 years ago
thejustinwalsh
commented
9 years ago For additional info, using this script for my travis CI builds works like a charm. However, who needs ruby when we can do this as a part of the premake process.
starkos
commented
9 years ago Thanks for the report! I think Blizzard may be about to land a bunch of new Xcode work, so I might hold off on this until I see what's coming.
When using xcodebuild or xctool to build the generated workspace and projects one will be missing the schemes required to do the build.
If you open the xcworkspace file at least once in Xcode, it will automatically generate the schemes for you. If you do not open the xcworkspace with Xcode, you will be missing schemes required to build the workspace.
Requesting that premake generates the project schemes as shared schemes and places them in the xcshareddata/xcschemes folder within each xcodeproj in the workspace. Alternatively one could build a workspace scheme with project references as well.
The ruby gem Xcodeproj has a method Project#recreate_user_schemes that appears to generate schemes for you. Something like this but automated into premake upon the creation of the projects and workspaces would be legit!