Linux vs ThirdParty Nodes

[iamlamprey]

What's the best way to compile these? I can't open my project without first compiling the nodes, but I can't use "Compile DSP Networks to DLL" because Linux

Do I really have to copy + paste the AutoGeneratedProject.jucer file from Windows, manually set all the module paths and includes and run make every time? Surely there's some equivalent to the Export button that will create the DspNetworks/Binaries subfolder correctly on Linux?

[David Healey]

@iamlamprey said in Linux vs ThirdParty Nodes:

but I can't use "Compile DSP Networks to DLL" because Linux

Works here

[iamlamprey]

@d-healey Did you have to set anything up special? Mine just asks me to go through the Compile wizard forever

Edit: ok im definitely missing something, my Export Wizard asks me for an IDE and the dropdown list is just empty

[David Healey]

@iamlamprey The wizard doesn't work on Linux, in fact I recall disabling it in a commit a few months ago, but perhaps that's only for plugin export. You can bypass it by checking the setting in project preferences, if you don't see it then you'll need to edit the settings xml file in the HISE app data folder. I think I demonstrate this in the bootcamp.

[iamlamprey]

@d-healey I've got this:

<?xml version="1.0" encoding="UTF-8"?>

<CompilerSettings>
  <HisePath value="home/user/Documents/HISE"/>
  <UseIPP value="0"/>
  <ExportSetup value="1"/>
</CompilerSettings>

Still just asks me every time, I'm not using your fork, do you know if you've made any other changes that might affect this?

[iamlamprey]

ah there's a full 35 min video in the course, thank you sir :)

[Dan Korneff]

@iamlamprey I remember somewhere that the configuration exists in 2 different places for some reason. You might be editing the wrong one.

[iamlamprey]

@Dan-Korneff Yep you're right, I had to copy

~/.config/HISE/compilerSettings.xml

to

~/.hise/compilerSettings.xml

Ctrl + H to view hidden files, for anyone stumbling upon this in the future

[David Healey]

@iamlamprey said in Linux vs ThirdParty Nodes:

~/.config/HISE/

Where did this come from?

[iamlamprey]

@d-healey Clanker said it was the Linux equivalent of %appdata%

Copying it seemed to get me past the compile wizard, and I can use Compile DSP networks to dll to create the .sh script, but that's all it makes

I don't get the usual folder structure or even the AutoGeneratedProject.jucer file

[iamlamprey]

Okay, just had to add my HISE path to that same file

[David Healey]

@iamlamprey said in Linux vs ThirdParty Nodes:

Clanker said it was the Linux equivalent of %appdata%

Don't trust chat GPT. If you want to know the correct path you can access it from the file menu in HISE.

[Dan Korneff]

@d-healey in my distro this is also the equivalent of app data.
Not sure why both get auto-generated

[David Healey]

@Dan-Korneff said in Linux vs ThirdParty Nodes:

Not sure why both get auto-generated

The distro shouldn't affect it. You can see the line here where that folder is created by HISE: https://github.com/christophhart/HISE/blob/5492ce96392057892a6d6b8dfa9420ff55653e39/hi_core/hi_core/PresetHandler.cpp#L1132

If you delete the one in your .config folder I don't think it will change anything.

[Dan Korneff]

@d-healey said in Linux vs ThirdParty Nodes:

If you delete the one in your .config folder I don't think it will change anything.

Is there any reason that HISE creates an additional folder .hise in the first place?
If AppData = ~/Application Support = .config, and HISE stores its program junk in AppData (Win) and ~/Application Support (MacOS), why doesn't it use .config on Linux for consistency?

[David Healey]

@Dan-Korneff said in Linux vs ThirdParty Nodes:

Is there any reason that HISE creates an additional folder .hise in the first place?

This is the correct folder. The one in .config is not used (and was never created on my system). Some programs store their settings in .config, others (like HISE) just dumb them in the home folder.

However one thing I've just noticed is if you use the snippet browser, this does create a "HISE" folder in .config

@Christoph-Hart Might want to check that.

[Dan Korneff]

@d-healey Exported plugins store their data (presets, documentation, etc.. ) in .config within the Company subfolder. Just like the structure on MacOS and Win. I just don't understand why it would be different for Linux.

[David Healey]

@Dan-Korneff said in Linux vs ThirdParty Nodes:

@d-healey Exported plugins store their data (presets, documentation, etc.. ) in .config within the Company subfolder. Just like the structure on MacOS and Win. I just don't understand why it would be different for Linux.

Yep that's true. It's just HISE itself that stores it in the home folder. According to the Filesystem Hierarchy Standard dumping them in the home folder is acceptable.

However the XDG Base Directory Spec recommends a .config folder.

It's a mess. I'd prefer it to all be in .config too. Maybe we can put it to a vote.