|
|
Mar 9, 2012 at 9:25pm
Problems with mxj and standalone app
Hey all,
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?
Has anyone else encountered this before?
Marc P.
|
|
|
Mar 9, 2012 at 9:43pm
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.
|
|
|
Mar 9, 2012 at 9:59pm
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.
Thanks for the heads up on this one.
Marc P.
|
|
|
Mar 10, 2012 at 1:04am
No problem – now I know I’m not the only one that’ll keep pestering C74 to make this automatic :)
|
|
|
Mar 10, 2012 at 11:40am
+1 for the automation !!!!
|
|
|
Mar 10, 2012 at 4:13pm
+1 for the automation !!!!
also for the jsextensions.
we already had this in max5. its gone in max6 ….
|
