Mac Export - arm64 unidentified symbols

[d.healey]

@trillbilly said in Mac Export - arm64 unidentified symbols:

is it wise to become a "Mac Developer"

Yes.

Also you shouldn't distribute VST2s unless you have an agreement with Steinberg, which they are no longer providing.

[trillbilly]

@d-healey I was reading on this recently. Noted. Thanks again.

[ulrik]

@trillbilly said in Mac Export - arm64 unidentified symbols:

is it wise to become a "Mac Developer"

Yes :)

[trillbilly]

@ulrik Great thanks. I was rummaging through Xcode and seen an area for your apple development profile. I think HISE has the same settings in the the preferences panel. Is this correct? If so, does it auto-fill from HISE to Xcode?

[Lindon]

@trillbilly said in Mac Export - arm64 unidentified symbols:

@ulrik Great thanks. I was rummaging through Xcode and seen an area for your apple development profile. I think HISE has the same settings in the the preferences panel. Is this correct? If so, does it auto-fill from HISE to Xcode?

they are not really the same thing.

You will need an Apple Developer account to create install certifiicates - but if you are not doing installers then this might not be a requirement - however you are going to have to codesign your plugins - so you will need an Apple Account (the sort of thing everyone has to use the Apple Store) to create a password for altool - which you will need as part of the codesigning process...

[trillbilly]

@lindon Ok, cool.
I created an Apple Account when downloading Xcode and such. I was reading that this is a "Free" Developer Account, which grants access to things such as Xcode. But in order to sell products I was under the impression I would need the Paid Apple Developer Profile in order to sign.

The codesigning process is my next step to learn. Not looking forward to it lol

[Lindon]

@trillbilly said in Mac Export - arm64 unidentified symbols:

@lindon Ok, cool.
I created an Apple Account when downloading Xcode and such. I was reading that this is a "Free" Developer Account, which grants access to things such as Xcode. But in order to sell products I was under the impression I would need the Paid Apple Developer Profile in order to sign.

The codesigning process is my next step to learn. Not looking forward to it lol

You might need a Apple Developer account to sel on the Apple store - if you can even get on there, but otherwise you dont need it to sell Mac based products elsewhere.

The codesigning is (now Apple have stopped moving the goal posts every 5 mins) trivially easy really...

[trillbilly]

@lindon Ok great, I do not intend to sell anything on the App Store or with installers (at least as of yet).

Im just starting to dig into it. It looks like something done via the Terminal (kind of how xcpretty was installed). Is this correct?

Ive skimmed some things saying you can have Xcode sign things automatically for you, have you tested this?

[Lindon]

@trillbilly - yes its a set of terminal commands you should use, XCode will only sign for you if you set it up as part of the compile process- I dont think anyone here has got XCode to do this automatically out of a HISE initiated compile, and given how simple it is to do manually Im not sure any one is trying...

[trillbilly]

@lindon Ok, great, thanks! I'll dig into it now and see if I can figure it out.

Are these commands entered after the VST is exported or something done while exporting?

Week 2 with a Mac, lets see how it goes...

[Lindon]

@trillbilly said in Mac Export - arm64 unidentified symbols:

@lindon Ok, great, thanks! I'll dig into it now and see if I can figure it out.

Are these commands entered after the VST is exported or something done while exporting?

Week 2 with a Mac, lets see how it goes...

Once you have an exported plug-in set you will then need to code sign them individually.

Try reading (all of) this:

Just a moment...

(www.kvraudio.com)

if you get stuck given me a shout - and I will fire up the Mac to get you the relevant commands...

[trillbilly]

@lindon Ok, cool, thank you! Im going to read through this a bit and see what the deal is. Im sure I will be back lol

[Lindon]

@trillbilly said in Mac Export - arm64 unidentified symbols:

@lindon Ok, cool, thank you! Im going to read through this a bit and see what the deal is. Im sure I will be back lol

yeah its a bit confusing - but most of it is people struggling with their implementation - and Apple moving the requirements - its quite an old thread ...and Apple changed a few things at different points in the process - annoyingly...

[trillbilly]

@lindon Ya, there's a lot going on in the thread lol. I'm trying to dig through and decipher what I need. Ill be here for a while.

If you get to your Mac and are able to expedite my process, it would be greatly appreciated!

Just to be clear on the codesigning...

1. There is nothing I need to download in order to use this via the Terminal, correct?

2. The codesigning can be done without being App Developer (since Im creating products that do not use installer)?

[d.healey]

@trillbilly said in Mac Export - arm64 unidentified symbols:

Ya, there's a lot going on in the thread

You only need the first post.

[trillbilly]

@d-healey Ok, cool. According to that the Apple Developer ID is required, which is no biggy. Ill be trying to sign a plugin shortly. Thanks

[Lindon]

@trillbilly - yes, sorry if I gave you the impression you didnt need a developer ID - you do - to codesign stuff, but not to sell stuff..

So I'm at the Mac...so....

1. copy your plugins to the desktop (not strictly required but it makes everything a lot simpler)
2. open a terminal window...
3. type this:

codesign -s "Developer ID Application: ()" "/Users//Desktop/XXX.vst" --timestamp

so an example might be:

codesign -s "Developer ID Application: Alan Smith (1234AB4FDG)" "/Users/alan/Desktop/coolplugin.vst" --timestamp

4. hit enter and wait .....in a few moments you will be told it was successful - most errors are in the typing - make sure you include the quotes in the correct places...

To test it worked type this into the terminal window:

codesign -vvv /Users//Desktop/XXX.vst3

repeat replacing XXX.vst with XXX.component

Now you will have a couple of codesigned plugins - copy from the desktop to the correct plugin folders...

[trillbilly]

@lindon Awesome man, thanks! My daughter is home from Daycare today so I'm gonna be a little late getting to the studio today. When I get there, I'll throw this in the terminal and give it a go!

As for notarized, I can see it's a different process in the terminal. It looks like you need an auto generated password, which I believe you get from the Apple Developer Account, correct?

Just for my own sanity...

"Codesigning" is a stamp that let's Apple know the App is created by a trusted developer.

"Notarized" is ensuring the App doesn't have any virus, etc.

Are these the basic ideas of the two?

[Lindon]

@trillbilly said in Mac Export - arm64 unidentified symbols:

@lindon Awesome man, thanks! My daughter is home from Daycare today so I'm gonna be a little late getting to the studio today. When I get there, I'll throw this in the terminal and give it a go!

As for notarized, I can see it's a different process in the terminal. It looks like you need an auto generated password, which I believe you get from the Apple Developer Account, correct?

Just for my own sanity...

"Codesigning" is a stamp that let's Apple know the App is created by a trusted developer.

"Notarized" is ensuring the App doesn't have any virus, etc.

Are these the basic ideas of the two?

not quite...
DAWs should NOT open or even offer you access to non-codesigned plug-ins.

Notarizing is for stand alone applications - like a stand alone version of your product, or the installer/packager you give to users to set up your product, MacOS wont even run these stand-alones without them being notarized. All notarized products should be codesigned first, then notarized.

Dont even get me started on the Avid/PACE EDEN tool kit for AAX...

.

[trillbilly]

@lindon I'm not even concerned about AAX at the moment. As long as I can ensure VSTi and AU work and are compatible both Mac & Windows, I will be happy for the time being.

Thanks for the clarification. So in other words, if I'm not doing installers or a standalone app, which I'm doing neither, the notarization is useless and as long as the individual plugins are codesigned, they are good to go in Apples eyes?