Export tool

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

[d.healey]

@Lindon thanks, that's what I figured, seems I have a bug to track down

[Lindon]

@d-healey good luck!

[arminh]

@d-healey there's no good place to store pdf. I always drop pdfs and tutorial content on dmg

[Lindon]

@arminh - were trying to use pkg not dmg no?

[arminh]

@Lindon yeah that why I'm mention about dmg. There's no good place to store documentation. We can save them in application support company/plugin.

Even big companies don't install docs.

[Lindon]

@arminh said in Export tool:

@Lindon yeah that why I'm mention about dmg. There's no good place to store documentation. We can save them in application support company/plugin.

Even big companies don't install docs.

right - so I think you are saying "there is no standard place for documentation on Mac"...

let me add "There is no standard place for documentation on Windows"

and then observe:

Not having a standard place to store documentation should be no reason for not including it in your installer..

YMMV

[arminh]

@Lindon on windows you can drop shortcut to pdf in start menu.

[Lindon]

@arminh -yes of course you can - and thats what I do , the above still holds.

[d.healey]

I was going to make a folder in applications with the company name and a sub folder for docs, e.g. /Applications/libre wave/documentation. I think this is what native instruments does but I need to check.

[arminh]

@d-healey adobe have something like this.

[d.healey]

It seems there is some issue with adding pdf files using the pkgbuild and productbuild tools, and not much info online. So I'm going to revert to packaging on Mac via WhiteboxPackages, this will be from a template file that my app automatically configures but it does impose some limitations I was hoping to avoid. But I think it will be suitable for most situations so not too bad.

Anyone know how to add a post installer script to a Whitebox Packages installer? I can see how to do it for individual components but not for the entire installer.

[d.healey]

Got a strange issue with MacOS installers. When I build the installer through Whitebox Packages everything seems to go smoothly, but after I run the install and install the app/plugins I go to open the standalone application and it won't run. When I expand the application bundle I can see a little no-entry sign indicating I don't have permission to run it. Have any of you had this issue or know of the solution?

Here's a screenshot of the bundle in packages showing the permissions, let me know if this is different to how you have yours set up.