Export Setup Wizard Problems

[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

[dannytaurus]

@Christoph-Hart said in Export Setup Wizard Problems:

I'm also thinking about a "Nuke HISE" tool

Definitely, although it won't help users who have multiple copies of the source on their machine.

[Christoph Hart]

@dannytaurus said in Export Setup Wizard Problems:

Definitely, although it won't help users who have multiple copies of the source on their machine.

Actually, yes it creates a script that searches THE ENTIRE FILESYSTEM for every copy of the HISE source code and then deletes everything.

I also add the ability of removing HISE plugin binaries and standalone binaries that aren't in the HISE folder.

[ustk]

@Christoph-Hart said in Export Setup Wizard Problems:

I also add the ability of removing HISE plugin binaries and standalone binaries that aren't in the HISE folder.

If it's an option yes, otherwise it's not very sexy for keeping different versions intentionnaly

[Christoph Hart]

@ustk said in Export Setup Wizard Problems:

If it's an option yes, otherwise it's not very sexy for keeping different versions intentionnaly

If you're at the level of keeping multiple versions INTENTIONALLY, then you won't need that feature. That's really just a tool so that we can tell noobs to NUKE that stuff and try again fresh.

[HISEnberg]

@Christoph-Hart Just confirming that the Wizard effectively worked on my Mac M2 (ARM64). Will run a test shortly on Windows.

My only concern is the nuclear option. Probably you've considered this already but all of my HISE projects are stashed in a folder named HiseProjects . I would be pretty upset if that nuke button removed this folder just because HISE was in the name, so it may need to be idiot-proofed somewhat.

[David Healey]

@HISEnberg I've known people who keep their projects in the same folder as the HISE source code so definitely needs to be fool proof.

[HISEnberg]

@David-Healey said in Export Setup Wizard Problems:

@HISEnberg I've known people who keep their projects in the same folder as the HISE source code so definitely needs to be fool proof.

Wait...I'm not supposed to do that???

I think I made that mistake when starting out. So yes, idiot-proof is tried and true when it comes to the nuclear option.

[dannytaurus]

@David-Healey @Christoph-Hart @HISEnberg I think whatever regex magic and tree-following voodoo is in the script, there will be some user somewhere who loses all their work because of their weird setup.

Maybe instead of actually deleting the detected HISE folders, the script should just alert the user of potential issues?

[Christoph Hart]

@David-Healey yeah that would be a problem. But A hise project folder with hise in the name will not be deleted, that would be nuts. It looks for all HISE Standalone.jucer files and walks the folder hierarchy up to the HISE root.