Export tool

[Casey Kolb]

@d-healey Not sure if this is useful for you, but I think I just figured out a way to write the LinkOSX file based on the user selected destination in the installer. Whitebox Packages gives you some variables to work with in the shell script, so it's just a really simple two-liner:

#!/bin/sh
# Write sample location selected by user to LinkOSX for HISE
destfile=/Users/${USER}/Library/Application\ Support/YourCompany/YourProduct/LinkOSX
echo $DSTROOT > "$destfile"

If you add this to the post-installation scripts, it'll run at the end of the installer. The only drawback is that needs to be a raw package in order for the samples to be relocatable.

Note: Still need to test this on more than just my machine.

[d.healey]

@Lunacy-Audio I'll try it out. I've added a file selector so you can add any post install script you like to the installer, I haven't tested it yet though.

[ustk]

@d-healey Hey Dave! I'm back on track... I just wanted to say that the Export Tool is an amazing idea! I will definitely have a closer look at it as it is very promising!

[d.healey]

What can you tell me about codesigning on Windows?

[Lindon]

@d-healey said in Export tool:

What can you tell me about codesigning on Windows?

-- that mostly no one does it.

If you are going to add additional code signing I STRONGLY recommend you look at the Pace/AAX signing next.

[Dan Korneff]

@d-healey The only signing/wrapping I do involves the Pace Wrap Tool. Same as with Lindon said.

[d.healey]

I've had other requests for signing Windows apps so users don't get the "untrusted software" popup, as I'd also like to prevent this popup for my users I'm interested in signing Windows apps.

What do I need to sign AAX plugins? I have a developer account with AVID but I haven't bought a license/certficate (whatever they call it) as I can't use it with my plugins due to license conflicts.

[Dan Korneff]

@d-healey head over to https://www.paceap.com/proaudio.html and sign up to be a developer (it's free). They will give you access to the Pace Eden Toolkit which contains their signing/wrapping tool.

[ustk]

@d-healey You need an iLok and install the iLok manager to access your Pace Central Account. Afaik it is the only way.
But first, you need to contact Avid so they push you to PACE. PACE will reach to you to install the Eden tool and give you all the necessary information to access the Pace Central Account...

[d.healey]

@dustbro I have a developer account already, and an iLok (a very very very old one), but don't I need to pay for something before I can sign apps?

[ustk]

@d-healey It is free

[d.healey]

@ustk Cool, can the tools be used from the command line?

[ustk]

@d-healey it is all command line in the terminal... but => PM because I don't know if it is legal to go further...

[d.healey]

Is it possible to export 32bit plugins/standalone on Mac? And is there any point in doing it?

[gorangrooves]

@d-healey said in Export tool:

Is it possible to export 32bit plugins/standalone on Mac? And is there any point in doing it?

No. XCode won't allow you to export a 32bit plugin.

[ustk]

@d-healey Apple stopped releasing 32bit macs 16 years ago, I don't think many people are still using a 16 years old machine to make music

[orange]

Yeah 32 bit macs are pretty old. But you can still export both 32 & 64 bit supporting Universal Binary plugins with XCode 8 and macOS Sierra or High Sierra. Just tick 'Support 32bit macOS' box in Hise Compiler Settings and compile the plugin in XCode 8.

XCode 10 doesn't support 32 bit.

[d.healey]

Thanks, I'll try to put a check for the xcode version number in my app and only show the 32bit option if XCode 8 is installed.

[ustk]

@orange But why would you export 32bit? Is there demand from mac users for that?

[d.healey]

@ustk Part two of my question :p

And is there any point in doing it?

I guess for crazy people running a 32bit host maybe...