Closed brylie closed 3 years ago
One idea that comes to mind is that it might be useful to have a configuration option (under Edit->Settings) to manually specify the Cabbage Rack binary.
That's a good idea. I can add a custom CabbageRack path as I have for other things.
Better yet, would it be feasible for the Cabbage Rack binary to be included in the standard Cabbage build?
I'm currently moving to CMake for all Cabbage builds. This will make it easier to build and install Cabbage. I am also working on a new cross platform build/install script that will pull everything Cabbage needs from remote servers when installing. I will share it with you once it's done so you can test. I'll leave this issue open until we are happy that things are resolved.
Btw, to answer the title of this issue, you should place the CabbageRack folder into the same directory the Cabbage binary. On Linux this isn't such a great strategy. Adding the option to set a custom path is probably best in this instance.
I've updated the build system on Linux. If you want to try building yourself, can you do a fresh clone of the CMake branch and follow the instructions? The Python build script will pull the latest CabbageRack from its git hub repo and bundle it together in the CabbageInstall
directory. If you run the installer script it will put everything into the correct location. If you would prefer to run it locally, then simply place the CabbageRack folder into the CabbageInstall/bin
directory. Can you let me know if this works ok?
You rock @rorywalsh! :man_singer: :guitar:
I just ran python build.py --config=Release
, in the cmake
branch, and got the following errors:
Below is the output from CMakeOutput.log:
After installing the following packages, the JUCE build(s) succeed:
Hm, it appears libgl1-mesa-dev
may be needed for some OpenGL related build steps in JUCE.
fatal error: GL/glx.h: No such file or directory
Pass --installLinuxDeps=True
the first time you try to build on LInux and it will install all the relevant libraries you need, including the ones listed above. This is mentioned in the cmake branch's main readme.
OK, thanks. I was reading from top to bottom and hadn't read to the "note for Linux users" section.
OK, everything works so far. No "CabbageRack cannot be found". I think I'm this close |---| to creating a "hello world" Rack module!
OK, the export worked! There is a small issue with labels not appearing that I will open separately:
We can probably close this issue now, since you have resolved it with the CMake support.
When trying to export a plugin for VCV Rack, I get the following error prompt:
This message is a bit confusing for two reasons
/usr/share/applications
, which is not a parent folder of/user/bin/..
Am I overlooking some documentation (I often do, sorry!)?
Configuration option?
One idea that comes to mind is that it might be useful to have a configuration option (under
Edit
->Settings
) to manually specify the Cabbage Rack binary.Include Cabbage Rack in default Cabbage build?
Better yet, would it be feasible for the Cabbage Rack binary to be included in the standard Cabbage build?