dapinsker

I've created a standalone app that uses mxj objects (specifically maxhole) to communicate over a wireless network. When using the actual .maxpat files, the system works perfectly. However, when the standalone is created, the mxj objects do not work properly. (The Max window indicates that there is a JVM error.) Is this a compiling issue? If so, how do I build the standalone app so that the mxj objects function correctly?

I've created a standalone app that uses mxj objects (specifically maxhole) to communicate over a wireless network.  When using the actual .maxpat files, the system works perfectly.  However, when the standalone is created, the mxj objects do not work properly.  (The Max window indicates that there is a JVM error.)  Is this a compiling issue?  If so, how do I build the standalone app so that the mxj objects function correctly?

problems-with-mxj-and-standalone-app

This is an issue that has been around for a LONG time (and still bugs me that it isn't fixed) - max.jar isn't automatically moved into your standalone package, you have to copy it manually. And any custom classes you've built, as well, I think. It lives in Cycling '74: Java: Lib, and while I'm not sure where you're 'supposed' to put it in the standalone package, adding it to the 'resources' folder inside the app seems to work OK.

I'm assuming you're on a mac, by the way.

This is an issue that has been around for a LONG time (and still bugs me that it isn't fixed) - max.jar isn't automatically moved into your standalone package, you have to copy it manually.  And any custom classes you've built, as well, I think.  It lives in Cycling '74: Java: Lib, and while I'm not sure where you're 'supposed' to put it in the standalone package, adding it to the 'resources' folder inside the app seems to work OK.

I'm assuming you're on a mac, by the way.


Yes - I'm on a Mac. Thank you - I was pulling my hair out over this. I had a nasty feeling it was something like this.

Yes - I'm on a Mac.  Thank you - I was pulling my hair out over this.  I had a nasty feeling it was something like this.

No problem - now I know I'm not the only one that'll keep pestering C74 to make this automatic :)

we already had this in max5. its gone in max6 ....

also for the jsextensions.
we already had this in max5. its gone in max6 ....


This isn't still an issue is it?I'm having an issue with a standalone that's seeming to point to an MXJ object. I don't have to do anything special to have MXJ included and functioning in a standalone, do I?

MXJ is the best for all types situation . Today 

 MXJ is the best for all types situation . Today java development field MXJ is broadly used .

Problems with mxj and standalone app