Installers

[d.healey]

Uninstallers...

I'm not familiar enough with whitebox or inno setup. Is it possible to make the uninstallers remove the configuration files that HISE plugins add to appData and where ever they are put on a Mac?

[Christoph Hart]

Innosetup creates an uninstaller automatically but weirdly there is no concept of uninstallers on macOS.

[d.healey]

@Christoph-Hart The inno one doesn't remove the config files though :(

[Lindon]

@d-healey correct... everything that your HISE product "installs"(Writes) then the installer - who has long since finished and gone to the pub --- knows nothing about - so the native installer has no idea about all that stuff in /AppData/Roaming etc...

[d.healey]

@Lindon But we do :) hence my original question. Can we make the uninstaller remove those files? I can do this easy peasy on GNU with a bash uninstaller.

[Lindon]

@d-healey well we are already at the limits of my inno knowledge here....:-(

[Lindon]

but theres this:

Inno Setup Help

(www.jrsoftware.org)

[d.healey]

@Lindon Thanks, I'll read through that.

[Dan Korneff]

Does INNO have the ability to let end users select what they'd like to install? Like a check box for vst, vst3 or aax?

edit:
found this thread that may help

Just a moment...

(stackoverflow.com)

[Christoph Hart]

Yes of course. The Inno script file that is created from HISE does give the user the option to select individual components.

[Dan Korneff]

@Christoph-Hart

Open a terminal and type %hise_path% --help for all available commands:(%hise_path% stands for the path to your HISE executable(standalone).)

my standalone app exists in:

C:\Program Files\HISE-scriptnode\projects\standalone\Builds\VisualStudio2017\x64\Release\App

so I open cmd and type in ?

C:\Program Files\HISE-scriptnode\projects\standalone\Builds\VisualStudio2017\x64\Release\App --help

[Christoph Hart]

My mediocre batch processing skills would suggest

"C:\Program Files\HISE-scriptnode\projects\standalone\Builds\VisualStudio2017\x64\Release\App\HISE.exe" --help

Because you've got a space between Program and Files.

[Dan Korneff]

@Christoph-Hart

[Dan Korneff]

@Christoph-Hart With Packages, do I need to make a "package" for each version of the plugin? and then import each of those into a project?
I just clicked around, but it looks like I'll actually have to read some documentation

[Christoph Hart]

Check out David's package files:

sofiawoodwinds/Packaging/OSX at master · davidhealey/sofiawoodwinds

Contribute to davidhealey/sofiawoodwinds development by creating an account on GitHub.

GitHub (github.com)

I am not doing it much differently.

[Dan Korneff]

@Christoph-Hart Any tricks on how to create the package for aax?
Packages shows my Application Support folder as Empty

[ustk]

@dustbro I don't have my computer in front of me, but you need to create each subfolder of the path (right click on Application Support)

[Christoph Hart]

Packages shows a "Vanilla" system, that you have to populate with folders and files that it will populate during the installation, so it's like Greg said, you need to add all folders and files at the location you want them to be.

Be aware that the AAX plugins have to be at the global /Library/Application Support/Avid/Audio/Plug-Ins folder and not the user ~/Library/... path. This is a problem if you are using the current user's home domain by ticking the last checkbox in the advanced settings:

[Dan Korneff]

@Christoph-Hart said in Installers:

Be aware that the AAX plugins have to be at the global /Library/Application Support/Avid/Audio/Plug-Ins folder and not the user ~/Library/... path. This is a problem if you are using the current user's home domain by ticking the last checkbox in the advanced settings:

I'm having a slightly different problem I can't seem to access the user ~/Library (which is where the VST3 folder is located.
I've tried

chflags unhidden ./Library/ 

from Terminal, but get access denied. Yay!!

[Dan Korneff]

I was able to create a shortcut for the user library and access thru there
My next issue involves confusion over the source and destination. When you add a folder to your list, what is that actually selecting?? I went thru and added my plug, and it automatically selects the Source and Destination. In Inno Setup, I could script the source file, and it's destination. This just makes me scratch my head.