Export Setup Wizard Problems

[David Healey]

@Christoph-Hart said in Export Setup Wizard Problems:

no, still honking around on VirtualBox, from a scale from 1 to Boomer how deprecated is that?

You've gone full boomer :p This is the guide I followed, should get you up and running. @Dan-Korneff put me on to Proxmox originally and I'm very grateful for it!

@Christoph-Hart said in Export Setup Wizard Problems:

Ah ok. Is FFTW optional on Linux? I thought this is the standard. I'll add IPP on Linux too, I think FFTW for Windows is a bit of a nerd option, no?

Yes FFTW is optional. On Windows you'd want it if you're making open source projects. The setup is pretty easy.

I can provide more instructions if needed.

@Christoph-Hart said in Export Setup Wizard Problems:

Which ones? I tried to grep all the build instructions from the HISE readme but they might be outdated.

The one's in the github readme are correct. I think the AI is hallucinating some extras.

It's added libpthread-stubs0-dev and ladspa-sdk. Also libwebkit2gtk-4.0-dev will need to be libwebkit2gtk-4.1-dev on newer distros but is correct for older ones.

I'd also install mold if it's available in the repo as it's a much faster linker.

I'll add some issues to the git repo with more details about this stuff.

@Christoph-Hart said in Export Setup Wizard Problems:

So basically what I want is to let the user tick which components he has already installed so that the script can skip that

I'd flip it and ask the user to select which components they want to install.

[dannytaurus]

@Christoph-Hart Maybe the script should know if we're building open or closed source projects?

[dannytaurus]

@Christoph-Hart Tiny UX thing but maybe change "Apple Silicon (M1/M2/M3)" to something like "Apple Silicon (M1 and later)" or "Apple Silicon (M-series)".

M4 and M5 are already out and folks with newer machines might still head to the forum and ask if their chip is supported.

Everyone likes to be a special case

[dannytaurus]

@Christoph-Hart Since we've already chosen a platform at the top of the page, the C++ Compiler section could be simplified to just show the compiler for our platform.

[Christoph Hart]

Good points.

Maybe the script should know if we're building open or closed source projects?

Why? It's only building HISE, not your projects.

[dannytaurus]

@Christoph-Hart said in Export Setup Wizard Problems:

Why? It's only building HISE, not your projects.

I thought you have to build HISE with FFTW instead of IPP on Windows when you're making closed-source.

I haven't started on the Windows side yet so I've probably got that mixed up.

So does IPP/FFTW only come into play when building the actual plugin?

[David Healey]

@dannytaurus said in Export Setup Wizard Problems:

So does IPP/FFTW only come into play when building the actual plugin?

Nope you're correct.

IPP for proprietary and FFTW for open source.

However if you're making both categories of project you would likely want both installed, then you'd build HISE and your projects with whichever one your project requires.

[dannytaurus]

@David-Healey said in Export Setup Wizard Problems:

then you'd build HISE and your projects with whichever one your project requires.

So does that complicate the setup script? Or would it just install both?

[David Healey]

@dannytaurus said in Export Setup Wizard Problems:

So does that complicate the setup script? Or would it just install both?

You can install both but I believe HISE can only be built with one - if it could be built with both and have a switch inside HISE that would be good though.

[Christoph Hart]

Alright, new features coming in:

• automatic update check. There's a new tool in HISE at Help -> Update HISE. This copies a string with the current HISE stats into the clipboard. Go to the web app/update, paste that buddy and it checks if a new PASSING build is available, then creates the script that pulls the changes and recompiles HISE. It checks against the CI build output so if I fuck up an intermediate commit, it won't be shown there as an update.
• I've also added a ZIP2GIT migration system: if the user doesn't use git, but has copied the zip file, it will migrate the system to use git (install git, delete the HISE folder, initialise it back as git repository and then pull & update). It currently preserves the Faust libraries on macOS, as this is the only thing that is added to the HISE source by the user, but am I missing something here?

I'm also thinking about a "Nuke HISE" tool, that creates a script that clears everything related to HISE (app data settings, HISE repo, PATH variables), etc. This might be helpful when users mess up the installation to get back to a clean slate.

[David Healey]

@Christoph-Hart Sounds like you've been busy, I'll try to check it out tomorrow