jmod.node fails to build
|Assignee:||Théo de la Hogue||% Done:|
|Target version:||MVC for 0.6|
when I run the build script with Jamoma Modular at the 0.6-nodelib-and-multicore branch, jcom.node fails to build with the following three errors:
/Users/lossius/dev/Jamoma/Modules/Modular/implementations/MaxMSP/jcom.node/jcom.node.cpp:213:0 /Users/lossius/dev/Jamoma/Modules/Modular/implementations/MaxMSP/jcom.node/jcom.node.cpp:213: error: 'jamoma_node_add_observer' was not declared in this scope
/Users/lossius/dev/Jamoma/Modules/Modular/implementations/MaxMSP/jcom.node/jcom.node.cpp:359:0 /Users/lossius/dev/Jamoma/Modules/Modular/implementations/MaxMSP/jcom.node/jcom.node.cpp:359: error: 'jamoma_node_add_property' was not declared in this scope
/Users/lossius/dev/Jamoma/Modules/Modular/implementations/MaxMSP/jcom.node/jcom.node.cpp:500:0 /Users/lossius/dev/Jamoma/Modules/Modular/implementations/MaxMSP/jcom.node/jcom.node.cpp:500: error: 'jamoma_node_properties' was not declared in this scope
In addition the following post-build tasks fail:
cp: /Library/Application Support/Jamoma/OSC.dylib: Permission denied
cp: /Library/Application Support/Jamoma/Minuit.dylib: Permission denied
cp: /Library/Application Support/Jamoma/CopperLANPlugin.dylib: Permission denied
I checked the permissions for "/Library/Application Support/Jamoma". It is owned by system with read/write permissions, while the admin group and everyone have read permissions only. Are permissions screwed up at my laptop, or could it be that this is a general issue?
#1 Updated by Théo de la Hogue about 9 years ago
- Status changed from New to Closed
The jcom.node external was just a way to test some new experimental features...
But for the 0.6 version I will make a real jcom.node to replace the jcom.hub...
This is not for tomorrow so I just clean the jcom.node in order to have a successful
About the permission things I only test the copy on my computer and it works...
so maybe there is a something non-general in the way I copy them or maybe it's
in something relative to your system permissions... Anyway you could copy them
manually this time because they would not change before a long time...