Export Setup Wizard Problems

[David Healey]

@Christoph-Hart said in Export Setup Wizard Problems:

once the process goes through we can just tell the agent to create a bash script / bat file that performs all those steps, then everybody can choose whether to run the script or use the agent.

Sounds good. The script should provide a nice interface, ask if they want to upgrade or install, which branch they want to use, etc.

Given what you said about one method failing and another succeeding and not caring because the AI handled it, how can we trust that the script it produces is bullet proof on all systems... I think there will still be some manual work required.

[dannytaurus]

@David-Healey said in Export Setup Wizard Problems:

Something wrong there, I compile on a VM with less.

Yep, definitely something wrong. Could be the way macOS handles RAM. Could have been something else on my system.

I bought a 32GB MacBook Air and it flies now, so I don't care what was causing it.

[David Healey]

@dannytaurus said in Export Setup Wizard Problems:

Could have been something else on my system.

Was it an Apple silicon system? That might be the difference.

[dannytaurus]

@David-Healey said in Export Setup Wizard Problems:

Was it an Apple silicon system? That might be the difference.

Yeah, it was an M1 MacBook Air. It was a really nice machine, and everything else worked fine. I could run large Logic projects, have loads of running apps, multiple Safari windows, etc.

It was just compiling HISE where it completely fell down.

[Christoph Hart]

Alright, guys I present to you: The HISE Installation Wizard.

https://hise-install-wizard.vercel.app/

(once this stabilizes, we'll port it over to https://setup.hise.dev, but for now let's enjoy that random 3rd party hoster).

Repo:

https://github.com/christophhart/hise_install_wizard

I think this is the best approach so far. It queries information from the user, then creates a build script which can be executed which should setup the system correctly to export plugins. It even checks the CI build status if I fuck up a commit and then resorts to the last working one. I will add a "AI Agent" mode soon that will spit out a prompt instead of a script so you can have your favorite robot hold your hand during that process if you want, but first let's confirm that the actual scripts work on each system. I did a test run on my mac and windows systems, but I'm so bad at setting up VMs it's not even funny anymore, so I still haven't tested a fully vanilla system yet.

Feel free to add issues in this repo with build issues or feedback regarding the UX.

[David Healey]

Noice! I get to redo my videos again :) but this time I just need to make one instead of 3!

@Christoph-Hart said in Export Setup Wizard Problems:

Feel free to add issues in this repo with build issues or feedback regarding the UX.

I like the UX.

Missing FFTW on Windows and Linux.
Missing IPP on Linux
Missing option to select the branch - or maybe we don't need that.

It's trying to install dependencies on Linux that aren't needed.

This tooltip is confusing, check the box if you've already cloned the repo - it's a button not a checkbox and the logic is inverted as the "box" is already checked.

@Christoph-Hart said in Export Setup Wizard Problems:

but I'm so bad at setting up VMs

You using proxmox yet?

[Christoph Hart]

@David-Healey said in Export Setup Wizard Problems:

proxmox

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

• Missing FFTW on Windows and Linux.
• Missing IPP on Linux

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?

It's trying to install dependencies on Linux that aren't needed.

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

Just make some issues over there, I'll chew through them.

This tooltip is confusing, check the box if you've already cloned the repo - it's a button not a checkbox and the logic is inverted as the "box" is already checked.

Yeah I've been going back and forth with this UX. So basically what I want is to let the user tick which components he has already installed so that the script can skip that, but that is exactly the other way how you would expect a installer to behave... any idea?

[dannytaurus]

@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

maybe the script should handle figuring out what's installed instead of trusting the user?

[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.