Johannes

after creating a simple app (only showing a comment and a panel) I cannot open this app on the machine with the following specs:

http://www.tryek.de/content/mmx_test_franke.zip

I built the app on a MacBookPro, Snow 10.6.7, 2.5 GHz, Intel Core 2 Duo, Ram 4 gb

com.apple.lauchd.peruser starting child process com.cycling74.com.com.Max.mmx_test_franke.appRuntime Result: Permission denied.

I already did a change on the App with Apple+I and changed the rights to RW to everyone, recursivly

after creating a simple app (only showing a comment and a panel) I cannot open this app on the machine with the following specs:
Snow 10.6.3
MacPro4,1
Quad-Core Intel Xeon
2,66 GHz
Cores: 4
Ram: 3 GB
Please download the program from here:
http://www.tryek.de/content/mmx_test_franke.zip

I built the app on a MacBookPro, Snow 10.6.7, 2.5 GHz, Intel Core 2 Duo, Ram 4 gb
Max 5.1.8

The console is giving me the message:
com.apple.lauchd.peruser starting child process com.cycling74.com.com.Max.mmx_test_franke.appRuntime Result: Permission denied.

after-build-app-is-not-opening-mac-only

Nice program! It works for me (well, I can see a "A TEST" message and a dark green panel).

A couple of years ago, building an .app on another partition than the boot one created an unusable application (cause by a permission problem, just like you - the solution was to apply some chmod u+x thru the Terminal on the runtime stuff).

Since then I always build my .apps on the desktop and move them afterwards although I had the feeling this bug was corrected.

A couple of years ago, building an .app on another partition than the boot one created an unusable application (cause by a permission problem, just like you -  the solution was to apply some chmod u+x thru the Terminal on the runtime stuff).

thanks for trying. Yes the program looks like that.

As I mentioned, I changed the permissions, but I will check again.

thanks for trying. Yes the program looks like that.
As I mentioned, I changed the permissions, but I will check again.

You need to make sure the executable bit is set, not the RW, which is something that can't be done thru OSX' info panel. You need to do that in a shell with chmod.

finally I got a crash report thanks to the recommended changes

Hi
finally I got a crash report thanks to the recommended changes
can anyone interpret the info?

It seems to me that is a frameworks issue,

try to reinstall maxmsp and recompile your app.

( do a backkup first of maxmsp folders and files)

It seems to me that is a frameworks issue,
try to reinstall maxmsp and recompile your app.
( do a backkup first of maxmsp folders and files)


Probably your comment is based on an interpretation of the crashreport.

Would you be so kind and give me a hint how you got to this conclusion?

Hi balam,
thanks for your advice, I will try so.

Probably your comment is based on an interpretation of the crashreport.
Would you be so kind and give me a hint how you got to this conclusion?

does anybody have a Mac Pro Quad and may try the test app

It looks like built apps on dual core with Max 5.1.8 are not running on Quads...

does anybody have a Mac Pro Quad and may try the test app
http://www.tryek.de/content/mmx_test_franke.zip
for me?
It looks like built apps on dual core with Max 5.1.8 are not running on Quads...

After Build, App is not opening (MAC only)