Working on my first module here (Mac OS 10.14, Rack v1.1.15). I have been successful in developing locally but I would like to start tracking/pushing changes in my project to a private GitHub repo.
My non-git flow has been to make code changes and use Terminal to RACK_DIR=<Rack SDK folder> make install. After setting up git in my directory, still good. However, using git push -u origin master to my GitHub account, make install completes the build and places it in the Rack plugins folder (visible in Finder) but removes the plugin from the Rack app module browser.
There’s a lot of steps going on here. If your plugin folder is in the correct place but you don’t see your modules in the Module Browser, the log file will tell you what the loading problem is.
Ok, checking out log file now. I’m seeing the similar problem of not loading plugin after making an inconsequential change (remove character, add same character back, save file).
This appears to be relevant warning from log file (my plugin is AmenTest2):
[4.865 warn src/plugin.cpp:158] Could not load plugin /Users/inez/Documents/Rack/plugins-v1/AmenTest2: Failed to load library /Users/inez/Documents/Rack/plugins-v1/AmenTest2/plugin.dylib: dlopen(/Users/inez/Documents/Rack/plugins-v1/AmenTest2/plugin.dylib, 2): Symbol not found: _modelBaronial
Referenced from: /Users/inez/Documents/Rack/plugins-v1/AmenTest2/plugin.dylib
Expected in: flat namespace
in /Users/inez/Documents/Rack/plugins-v1/AmenTest2/plugin.dylib
Apparently _modelBaronial is not found, but to be clear the build works until I save.
No, I am not trying to instantiate Baronial. I’ve repurposed some DrumKit code and it may be hanging around. Regardless, the module builds/installs fine with it in there until I save a trivial change.
just noting that it wouldn’t be giving you an error about that module unless it were linked into init() via something like p->addModel(modelBaronial).
if you have some source you can share, I’m happy to point to it.
obviously I don’t care that you’re using drumkit source, or I wouldn’t have licensed it the way that I did
not sure why the “ugh”, I’ve typically had a better experience in lldb than I’ve had in gdb. of course, I still miss dbx, so no accounting for taste I guess.
the whole llvm suite makes me sad when I have to use the gnu suite at this point. pre-egcs, the gnu suite was slow, but very easy to work with. post-egcs it was hugely improved for compilation, but much more complicated to work inside. llvm (and clang/clang++) make me nostalgic for those simple gcc days, but still compile extremely well.
if you take the time to learn lldb, it’s amazing, and quite a few of the gdb commands “just work” (those ones were old dbx commands that gdb adopted).