Bug #969

standalone apps don't build correctly in some cases

Added by Adrian Gierakowski 7 months ago. Updated 7 months ago.

Status:Closed Start date:2011-10-07
Priority:Normal Due date:
Assignee:Adrian Gierakowski % Done:

100%
Category:- Spent time: 2.00 hours
Target version:- Estimated time:2.00 hours
Branch: OS:

Description

if the patches in the app don't use jcom.remote and jcom.message the corresponding .mxo files do not get copied to the bundle. This causes max to when the standalone is opened:

jcom.hub: jcom.remote: No such object
jamoma: could not load extern (jcom.remote) within the core
method setcallback called on invalid object
method subscribe called on invalid object
jcom.message: No such object
jamoma: could not load extern (jcom.message) within the core
jcom.message: No such object

and obviously the modules in the app are not functional

to reproduce:

open:
1.jmod.mouse.maxhelp
2.create a standalone app out of it
3.open the app

manually copying the jcom.remote.mxo and jcom.message.mxo to the application bundle fixes the problem

Associated revisions

Revision 6924c912
Added by Nils Peters 7 months ago

fixes #969

History

#1
Updated by Adrian Gierakowski 7 months ago

  • Status changed from New to Closed
  • % Done changed from 50 to 100

fixed in commit: https://github.com/jamoma/JamomaModular/commit/b93c9de6d958a2c7f7fccd09d24369464a7536ee

Application Builder now always copes the jcom.remote.mxo and jcom.message.mxo to the application bundle (fixed only for Mac, I'll work on windows side later)

#2
Updated by Nils Peters 7 months ago

  • Status changed from Closed to Assigned
  • % Done changed from 100 to 70

Hi Adrian,

good catch!
on a devel machine where the externals are not in the C74 folder, your fix doesn't work.
I'll try to make the path to jcom.message and jcom.remote more dynamic and will commit.

#3
Updated by Nils Peters 7 months ago

  • Status changed from Assigned to Closed
  • % Done changed from 70 to 100

Also available in: Atom PDF