Linux binary things
d.healey last edited by d.healey
I have found some things with exporting my instrument as plugin and standalone on Linux.
First the plugin, it is necessary to disable the JUCE_WEB_BROWSER component under juce_gui_extra in Projucer before compiling the plugin. If this isn't done Ardour (and perhaps other hosts) blacklist the plugin. No idea why.
When Reaper first loads after the plugin has been added to its search path it will run through its splashscreen and then crash (instant close). Then when opening Reaper again there is no problem and Reaper runs just fine and detects the plugin. This is probably a Reaper issue I would think...
And a strange thing with the standalone, it will only run from the terminal. If I double click the binary and enable the Make Executable and Run permission it doesn't do anything. I've tried as root and user, the result is the same with both. Very odd. Also the binary doesn't have an icon (other than the OS default), how do I set one?
dustbro last edited by
@d-healey I saw this on the Visual Studio forums:
To specify an application icon
In Solution Explorer, choose a project node (not the Solution node).
On the menu bar, choose Project > Properties.
When the Project Designer appears, choose the Application tab.
(Visual Basic)—In the Icon list, choose an icon (.ico) file.
@dustbro I'm in GNU/Linux world, no such thing as visual studio, it's all command line here
Christoph Hart last edited by
I've tried as root and user, the result is the same with both. Very odd. Also the binary doesn't have an icon (other than the OS default), how do I set one?
Hmm, on macOS, applications are bundled in a folder called package (and the icon is stored within the package) so maybe it's the same on Linux.
Unfortunately my Linux skills are not sufficient to be a real help here...
@christoph-hart I'll play around with and if I find anything I'll share it here
I found the answer to the icon thing, no icons for Linux apps - https://forum.juce.com/t/icons-in-linux/14500
Standalone thing is kind of solved. I realised that HISE itself won't run when I double click the binary (even though the execute permission is set). However it will run from the terminal or from the start menu (which is how I usually open it). So maybe this is a JUCE quirk or it's something strange with my system.