Slight update. I've merged the configs from the faust and non-faust exporters into a single exporter - like it is for the other platforms.

For example, you can now use CONFIG=ReleaseWithFaust

@d-healey

I keep accidentally trying to use metaprogramming concepts from c++20 and have to remember Hise is not c++20 😩

@orange said in Qt Installer framework:

Personally, I do not see any additional advantage

You only have to learn a single installer platform instead of learning a separate one for each OS. It will also look more similar on each system so a user moving from Windows to Mac for example will get a similar experience on both.

@oskarsh It is in the official repo already. I've just pre setup my juicer file for my use case.

@oskarsh I don't think HISE compiles against JUCE 7. Your best bet may be to port the fix yourself.

@d-healey I've installed an old ubuntu version and compiled the Plugin again! I will keep that in mind and set up this VM only for compiling. Thanks!

@etXzat Yes Ubuntu has some quirks when it comes to installing some packages, that is why I build from source and installed in manually.
I want to avoid installing from the official repository since they have outdated versions, see:
https://launchpad.net/ubuntu/+source/faust
latest current stable is 2.41

@sletz
make all && sudo make install solved my issues! Thank you very much.

JUCE_DISABLE_NATIVE_FILECHOOSERS=1 Is the solution. The non-native file picker is ugly but it does the job.

Linux Threads Be Like 🤣
https://media.tenor.com/images/220b86608e0781337040b846a71f0ebb/tenor.gif

alt text

@d-healey Well the sets are not correct, SSE 4.2 is NOT the highest or newest that HISE uses. Most likely AVX and AVX2 aswell. Or indeed I would have to dig out that old spiked-on AMD cpu in my intel machine.

Architecture = "native" is the issue. It over-rides any setting you make in hise. It uses your build-cpu´s sets available to do the best enhancements available. And whoever said IPP is the only thing in need of higher sets hasnt read the amount of issues on this topic over at the juce forums.

Setting Architecture to x64 in the .jucer project is the ONLY thing I was able to start my instrument build with. That flattens it to x86_64, which is basic original specs of the first 64-bit cpus, so no SSE3 or above, most likely.

@d-healey said in Linux standalone instrument application and settings folder locations:

/home/.config is a folder. . on GNU/Linux means the folder is a hidden folder. The default vst folder is /home/.vst or /home/.vst3/ and LV2 plugins go in /home/.lv2`. I'm pretty sure most users are familiar with this.

Windows and (especially) MacOS like to tell users what to do, GNU/Linux is a little more flexible generally, depending on the distro and desktop environment.

Okay, that´s a big part of why a lot of people choose Linux instead of the others. That´s a part of the platform and most experienced users or intermediate will handle that fine. The obviousness/strictness of a mac is a big part of why an answer can be found almost anywhere. And having rules for it is a big part of a platform. Nevertheless, freedom is in the whole Linux air. To be respected.

You can download an installer I created here to try it out.

Will do! Thanks a lot for the info.

This info should really go in the docs. The paths on Linux is an essential part of docs. One fine day. Perhaps I´ll get there first, you never know.