Export tool

[andioak]

@d-healey Perfect! Just didn´t see any replies here for it in any earlier messages.

[d.healey]

I'm finishing up the Windows installer and it's thrown up a question I'd like to get your opinion on.

Do you think the installer should allow for both standard and legacy CPU support (see image below)? Or should there be two separate installers, one for modern systems and one for legacy? Or something else?

I think one installer is nice because it means users don't get confused about which installer to download, but it's not so nice because there is now a confusing selection of options within the installer.

[gorangrooves]

I think that what you have in your screenshot is good enough. One installer (to rule them all!) :)

[A Former User]

Maybe just the modern CPU Version for each, then have a single switch somewhere that adds Legacy?

I don't see a reason why anyone would want, say, the 32-bit standalone for Legacy CPU, and the 64-bit plugin without it.

[orange]

I think it could be better to make separate the installers because nowadays almost nobody uses a very very old pc to run these plugins.

• 32-bit / 64-bit Standalone
• 32-bit / 64-bit VST2
• 32-bit / 64-bit VST3
• 32-bit / 64-bit AAX

structure would be straight forward for it.

[ustk]

What @orange said...

[d.healey]

I think I'll go with the separate installer option. I'll get the exporter to automatically build two installers if it finds legacy plugins have been compiled. Do any of you bundle documentation in your installers?

[Lindon]

@d-healey yep - usually the manual...and on windows an uninstaller for the stand-alone...

[d.healey]

@Lindon Is the manual a single file or a documentation folder containing multiple files?

[Lindon]

@d-healey its a single pdf...I am of course thinking of going over to this new fangled in-line documentation panelly thig that all the kids seem to be down with......

[d.healey]

@Lindon I'll include the ability to add an optional pdf to the installer.

[Lindon]

@d-healey nice...

[d.healey]

Status update:

GNU/Linux: Fully working (standalone, vst2, installer). x64 only
Windows: Fully working (standalone, vst2, vst3, installer). x86/x64
MacOS: Fully working (standalone, vst2, vst3, au, codesigning). Needs a bit of tuning but almost there (installer). x64 only.

When I say fully working, that's in my own tests, I expect many a bug report when I release it into the wild.

It's quite possible that AAX plugins will compile just fine on Windows and MacOS too, I've implemented it in the app but haven't tested it.

If all goes well I should finish up the tuning of the MacOS build tomorrow and it will be ready for my patrons to test this weekend!

@Christoph-Hart Could you merge my juce_template pull request (if all is well) as the mods there are needed for my app. The mods are also useful for regular exporting from HISE, bigobj is enabled by default and the VST3 SDK is set correctly to the one that is in the JUCE folder.

[Lindon]

@Christoph-Hart - yep those additional changes to the juce_template will be very helpful...

[alepan]

@d-healey Great News!!

[Natan]

@d-healey Sir, Is This Only Works This Way?
Hise Export To Installer?

Or Can We Use This For Packaging Other Things, Such As PDF Guides?
I Mean Can We Include Any Files To The End Installer?

BTW, This Is A Brilliant Idea, Will Jump In The TRain In Release Date <3
God Bless You, Sir David, You Are An Inspiration :folded_hands_light_skin_tone:

[d.healey]

@Natanr In a single process it can compile projects and create an installer with a bundled license file and user guide. On MacOS it can also codesign and notarize (as long as you have valid Apple credentials). If you want to add extra files they need to be placed in to the packaging folder manually before the installer is generated, this part though won't work on Windows as the installer template is predefined.

[Natan]

@d-healey This Is Absolutely Insane Well Done Sir

[d.healey]

Anyone know how to add a user manual (pdf) to a Mac installer?

[Lindon]

@d-healey just like a .component or .vst place it in the package hierarchy.