search

consulo / consulo-unity3d

Frameworks: Unity3D
Apache License 2.0
103 stars 10 forks source link

MacOSX: After building new executable, it can't open it #11

Closed joaomcarlos closed 9 years ago

joaomcarlos commented 9 years ago

15:53:17 Compilation completed successfully in 1 min 2 sec 15:53:17 Error running BuildMacOSX64: /Users/silent/Documents/Dropbox/Development/Unity/TSW Unity4.6 Test/out/production/Assembly-CSharp/TSW.app/Contents/MacOS/TSW is not exists

http://puu.sh/gU6I9/ea97719926.png http://puu.sh/gU6Fc/32f9eac807.png

joaomcarlos commented 9 years ago

Oh, and if I don't replace the module name manually, I get this:

15:49:33 Compilation completed successfully in 59 sec 15:49:33 Error running TSW Unity4.6 Test: /Users/silent/Documents/Dropbox/Development/Unity/TSW Unity4.6 Test/out/production/TSW Unity4.6 Test/$ModuleName$.exe/Contents/MacOS/$ModuleName$ is not exists

VISTALL commented 9 years ago

I think it duplicate https://github.com/consulo/consulo-unity3d/issues/4 but on MacOS

I known this bug - but i cant reproduce it

VISTALL commented 9 years ago

I think - i will done https://github.com/consulo/consulo-unity3d/issues/8 this issue - and u will test again.

Sorry for that - for now u can only run inside Unity Editor:(

joaomcarlos commented 9 years ago

It creates the file perfectly, just doesn't run it. If you run the .app file, macosx will trigger everything needed to open the sub-file, thats how executables work in macosx.

VISTALL commented 9 years ago

I already have some hack for MacOS - but u found case when it not works

https://github.com/consulo/consulo-unity3d/blob/master/src/org/mustbe/consulo/unity3d/module/Unity3dModuleExtension.java#L233

VISTALL commented 9 years ago

Me closed #8 - later update Unity3d plugin(and consulo - npe fix), reimport project and try compile and run. Create new issue if need