So the script works around that by copying the project to desktop and building off there. host:/ Īlso, XCode can’t build inside Shared Folder regardless of mounting. So, the script mounts it in the local drive prior to any other commands: mkdir -p sudo mount -t vmhgfs. Those names must match with build settings in Unity Editor.īy default, commands like cd and cp can’t access inside Shared Folder (“no such file or directory”). The Shared Folder is named _transfer_ in the script which may be changed, as well as project name ( MyProject) and app name ( foo.app). The process can be halted it by closing the terminal window. The script may be set to login item so that it automatically starts running. For the timestamp file’s format, the script can be something like this:
Static methods marked with attribute are invoked whenever a build is finished. Also an iPhone needs to be connected to the computer via USB and routed to VM. Xcodebuild doesn’t have a feature to deploy to devices, but there’s another tool called ios-deploy to do so. To build an XCode project via shell script, there’s a command line tool called xcodebuild. This folder will house and enable communication between Unity Editor and shell script. Shared Folder is VMWare’s feature to access to the host file system. So, as long as the script is running on VM, user can press the “Build” button in Unity Editor and hands-free wait until iPhone opens the app automatically. Then in VM, the shell script will detect the flag, build/deploy the project and fold the flag. Whenever Unity Editor composes a project into the folder, a C# post-process script will set a flag in the files.
#UNITY BUILDING FOR MAC SLOW ON WINDOWS WINDOWS#
The shell script watches very simple timestamp files in a directory that both Windows and VM macOS have a read/write access to. Please acknowledge the risk and proceed on your own responsibility. Also, please read through and do your own research before fully committing, because there may be some hardware requirements.ĭisclaimer: Running any macOS on non-Apple hardware is against the Apple EULA. Note: This is a “poor man’s” method an d potentially wastes your resource in a long run if you could just buy a Macbook in the first place. This article proposes some components to manage the automation. The process is click-and-wait basis and each build should take about 5 minutes. Using VMWare, one can run a shell script on a local virtual machine to automate the entire process of deploying Unity apps from Editor to iPhone via USB. Here is an aid for developing Unity iOS apps on Windows machine.
0 kommentar(er)
