Open kphillisjr opened 8 years ago
This is important for building a number of projects, especially the AGV-related build settings. It's a little complicated by the CVS and SVN integration in the tool itself, though.
I believe CVS/SVN Integration can be handled in as a separate issue, and we can simply imply for now that the "-noscm" argument is specified for now. If you must have cvs or svn integration right away the simplest option is to wrap the relevant tool itself, and make sure this tool is found... otherwise generate an error.
Edit: I think that fixing issue #89 may be extremely helpful in this, since we could implement agvtool as a shell script.
All agvtool is used for is Modifying version information in the property list files and project files. There is a few cases where projects script this utility to modify the product versioning information.
Apple Technical Q&A QA1827: Automating Version and Build Numbers Using agvtool Apple Mac OS X Developer Tools Manual Page: agvtool(1) JellyStyle Blog: Versioning with Xcode
note: I believe the "submit" action is the only action that can be left out.