Then on an article, automatically generate the framework, this article I put the Shell Automation Packaging IPA organized a bit, I hope you like it, hehe. We suggest that you take a look at the previous article first. Http://www.unitymanual.com/thread-21475-1-1.html
First of all, we must first understand the important steps of nity automatic packing.
1. Automatic generation of Xcode engineering.
2. Automatically generate. IPA and dSYM documents.
3. Upload the App Store (abbreviated in this article)
First of all we do in the channel package, generally each channel has its own special needs, such as game name, game icon, SDK, and so on. So when I do the automated packaging tool, I need to pass the channel as a parameter into the shell script, as shown in the following figure to start running my shell script, which only receives one parameter, in fact, is to tell the script what channel you want to hit the package, here I write 91.
The script is relatively simple, the principle is that Mr. Xcode Engineering, and then build. IPA. The $ in code represents the first argument 91 string I passed in.
Unity_path: Is the unity of the installation path, if you do not change unity of the name of the Mac will be this path.
Peoject_path: This is the path to your game project. Which is the path to the assets/level.
Build_ios_path: This is a script that I packed to generate IPA, and I'll go into the details that I'm currently putting this script in my game project, so he's a relative path.
Xcode_path: This is the path to generating the XCODE project, because there may be a lot of channels, so I'll pass the 91 string as the filename. [AppleScript] Plain text view copy code?
| 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28-29 |
#!/bin/sh |