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

[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

[LeeC]

Found a way to access the Users>Computername>library>audio>plugins using Whitebox for anyone that's following this.

Check this out:

WhiteBox - Packages - Q&A_03

(s.sudre.free.fr)

Instructions
Let's say you want to install a file in ~/Library/Application Support. Here's how to do that:

Open Packages
Create a new Distribution project.
Choose Packages > Preferences…
Click Advanced.
Check Show Advanced User Options and close the Preferences window.
Select Project in the source list.
Click the Settings tab.
Scroll to the bottom of the Advanced Options list.
Check current user's home.
Click the Requirements & Resources tab.
Check Install on startup disk only.
Select the package in the source list.
Click the Settings tab.
Uncheck Require admin password for installation.
Click the Payload tab.
Select the /Library/Application Support row in the Contents list.
Click +.
Select the file you want to install and click Add…
Select the Reference Style and click Add.
You can now build your package and test it.

[Dan Korneff]

@LeeC I tried the instructions, and it doesn't install to the ~/Library
The link even has a Sample Project.... I opened and ran. Still installed to /Library

[LeeC]

@dustbro I think I tried that it sample project and it worked ok.
Let me take another look.....

[LeeC]

@dustbro Yep just tried the sample project and it worked.

Installed a 'payload_file.txt' file to the ~/Library/Application Support/ location.

I'll have a play about but not entirely sure why you're not seeing it your end :(

[arminh]

BTW. In white box installer you can only install in one location. You must choose whether you want to install on /Library on user home ~/Library You can't install part in normal library and second part on user folder. Only one option which I figure out is post install scrip which install everything in normal Library and then copy it to user home

[Dan Korneff]

I guess at the end of the day, VST/AU/AAX plugin folders exist in /Library, so I removed my concern for needing to install to ~/Library

[Dan Korneff]

Hey guys,
I need your help figuring out a simple install package for a plugin on MAC.
I have an FX plugin that contains audio files that are too large to embed, so the resources file will need to be added to an installer. Shouldn't be an issue.

Not a problem with PC. I can install the plugins to their proper folders, as well as deposit my AudioResources.dat file to the User AppData folder. Yay!

My dilemma is with MAC. Using Packages, I can create a Distribution package that can install the AudioResources.dat file to the ~/Library, but if I add my plugin raw packages to this Distribution package, all of the files get installed to the ~/Library folder.
I could just create 2 installers... one for the ~/Library and another for /Library, but I feel like there's a better way to do it.

What have you done in the past?

[ustk]

@dustbro I'm not sure I understand well but if you create a distribution project with Packages, you can add as many packages as you want with their own payload and destination... Each package within a distribution is unique and different from the others, so I don't see where you have an issue with the destination