Creating an Installer on Mac - Can't access subfolders using Whitebox

[d.healey]

I do it through the command line. Everything you need is here - https://github.com/davidhealey/sofiawoodwinds/tree/master/Packaging/OSX

[LeeC]

You're both legends for replying so quick.

Ok, I'll take a look at the information posted.

Cheers

[LeeC]

Hey guys,

I managed to create an installer that is setup to install an AU & VST file to their associated folders (below), however, when I run the installers the files are not copied to the destinations despite the fact that 'The installation was successful' is shown .

library>audio>plug-ins>components>plugin.component
library>audio>plug-ins>vst>plugin.vst

Interestingly though, if I create a different installer to place files directly in the 'Library' folder or 'User' folder location they show up fine.

library>plugin.vst
user>plugin.vst

Any thoughts would be much appreciated.

Cheers

[LeeC]

Considering trying your command line approach @d-healey but I honestly wouldn't know where to start.

I checked out the github link that you sent, but I'm such a newb that I wouldn't know how to make use of the files within it

I know you were talking about setting up tutorials on Patreon a while back....
Is this something that you've covered already?

Any guidance would be golden.

Thanks

[orange]

@LeeC Be sure that you made the plugin's file path "Absolute" in Packages. Go to the Payloads section, click on your plugin, on the right side, it should be set to Absolute.

[LeeC]

@orange Yes the plugin reference is definitely set to 'Absoulte Path' in the payloads section...

Thanks

[LeeC]

So just looked in a little deeper and they are infact installing to the hard drive.
I noticed that there are two plugin locations on a Mac for anyone finding similar issues...

1. Users>Computername>library>audio>plugins
2. library>audio>plugins

I was initially checking location 1 but the installer was writing to loaction 2.

Thanks to everyone for helping out

[d.healey]

@LeeC

I know you were talking about setting up tutorials on Patreon a while back....
Is this something that you've covered already?

The Patreon has been going for a few months now but exporting plugins and building installers isn't something I covered yet. Probably won't get around to them until next year now.

[LeeC]

@d-healey Thanks for letting me know.
Will definitely check out the Patreon once I get over this installer malarchy

[LeeC]

Typical!

So it turns out that in order for Logic X to recognise au plugins, the component actually needs to be installed in location 1. below:

1. Users>Computername>library>audio>plugins>components
2. library>audio>plugins>components

Does any know how to get Packages to create an installer to write to this location (1.)?

The issue I'm finding is that the Computername will vary depending on which machine it's installed on. So setting it as an absolute location is not on option.

Has anybody been down this road before using Whitebox Packages?

Hope this makes sense.

Thanks

[ulrik]

@LeeC see this pictures, when on payload, click the + and you will be able to locate the user/library/audio/plugins

[LeeC]

@ulrik Thanks for replying.

But from my understanding your picture below shows that the plugins will install directly into the /users folder and not into the user/name/library/audio/plugins folder.....

Appreciate your response though

[ulrik]

@LeeC that picture shows only when you start the process, when in payload I load the plugins from /Users/myName/Library/Audio/PlugIns/ and components & VST3

[ulrik]

This post is deleted!

[ulrik]

@LeeC I'm sorry, I did not read your first question so well, I see now that you want to install the plugins to Library/Audio/PlugIns/etc...
stupid me, I'll delete the latest post...

[arminh]

In oner installer you can't install in system file and home user folder. To do this I created post install script which move content from Library/Aplication Support/PLUGIN NAME to ~/Library/Aplication Support/PLUGIN NAME.

[LeeC]

@ulrik No worries. Thanks for trying though!

[LeeC]

@arminh This sounds interesting...

So what did you use to create a post install script?

I think this is exactly what needs to be done

[arminh]

@LeeC I just edited code which are on white box page

First create file post-installation.sh and use it as main post installation script

#!/bin/sh

foundPackage=`/usr/sbin/pkgutil --volume "$3" --pkgs=$INSTALL_PKG_SESSION_ID`

## For Mac OS X 10.5 ##

if [ -z "$SHARED_INSTALLER_TEMP" ]; then

	if [ -f $INSTALLER_TEMP/.install.$INSTALL_PKG_SESSION_ID ]; then

		foundPackage=""

		/bin/rm $INSTALLER_TEMP/.install.$INSTALL_PKG_SESSION_ID

	fi
fi

## End For Mac OS X 10.5 ##

if test -n "$foundPackage"; then

	# It's an upgrade

	/bin/sh ./postupgrade.sh

else

	# It's a clean install

	/bin/sh ./postinstall.sh

fi

exit 0

Next, create second script called postinstall.sh with this content

#!/bin/sh


cd ~/Library/Application\ Support/
mkdir COMPANY_NAME
cd ~/Library/Application\ Support/YOUR_COMPANY NAME
mkdir PRODUCT_NAME
sudo mv /Library/Application\ Support/COMPANY_NAME/PRODUCT_NAME/* ~/Library/Application\ Support/COMPANY_NAME/PRODUCT_NAME/
cd /Library/Application\ Support/
sudo rm -rf COMPANY_NAME


exit 0

If you have space in your Company or product name you must write this like this

My\ Company = My Company
My\ Product = My Product

[LeeC]

@arminh Great info thanks.
I'll check it out