exporting Pc versions on mac

[aaronventure]

@sodanswishers Running Windows on Parallels. You can also set up Github Actions to export the plugins on all three systems.

[sodanswishers]

@aaronventure how can i create the GitHub action ? i didn't want to use parallel just not to familiar with virtual machines and don't want to save anything in the wrong location and possibly corrupt something on accident

[aaronventure]

@sodanswishers check out how HISE's actions are set up for testing commits.

for setting up IPP via Github Actions specifically if you need it on Windows, check this out https://github.com/sudara/pamplejuce/blob/main/.github/workflows/build_and_test.yml

[dannytaurus]

@sodanswishers I'm on Mac and just installed the Parallels trial. Seems fairly straightforward.

But I'm also very interested in using GitHub actions for building Windows plugins. I have them set up already for building Mac AU/VST but no idea where to start with Windows builds. I'll dig into the HISE actions a bit more.

@aaronventure Thanks for the IPP tip!

[aaronventure]

@dannytaurus Give this a look, too

HISE/.github/workflows/build_installer.yml at develop · christophhart/HISE

The open source framework for sample based instruments - HISE/.github/workflows/build_installer.yml at develop · christophhart/HISE

GitHub (github.com)

[Matt_SF]

@dannytaurus be aware, if you have a M1 chip or above : pace tools (iLok and codesigning) are not supported on parallels vm machines

[d.healey]

@Matt_SF said in exporting Pc versions on mac:

pace tools (iLok and codesigning) are not supported on parallels vm machines

I got an email a couple of days ago to say you can sign with a web service now, no iLok required. I don't know if that would help get around this problem.

[aaronventure]

@d-healey Did you try this out?

[d.healey]

@aaronventure I already have the iLok method integrated into my build script so I haven't looked into the other method at all.

[dannytaurus]

@Matt_SF Thanks for the tip, makes sense. But I'm not planning on code signing my Windows plugins, and I'm certainly not going anywhere near iLok

[Matt_SF]

@d-healey you're right. I was aware of this service, but I don't know if you have to pay for it, or if it's free...

[Matt_SF]

@dannytaurus well, in that case...
It depends of what's your goal. Ultimately, if you want to distribute your plugins and reach Protools users you'll have to go through this.

[d.healey]

@Matt_SF said in exporting Pc versions on mac:

I don't know if you have to pay for it, or if it's free..

Paid but with a free trial

AAX signing without an iLok
Our latest service, Cloud AAX Signing, allows AAX code signing for hosted, cloud-based CI build systems without the need for any iLok USB. For a free evaluation of our Cloud AAX Signing service, please contact PACE Sales at sales@paceap.com.

[Matt_SF]

@d-healey ah, that's what I thought

[dannytaurus]

@Matt_SF I don't target Protools users at all. I reckon my customer base and Protools users have virtually zero overlap. I'd rather lose that tiny percentage of sales than mess about with AAX and iLok. Sounds like a lot of work!

Regarding the code signing on Windows - I see folks here saying they don't do it and their Window users get on just fine with installing and using their plugins.

If I get complaints I might look into Windows code signing, but honestly I would think seriously about only selling to Mac users rather than go down that rabbit hole. At least until they make code signing on Windows as simple as it is on Mac.

[EDIT] That's not meant to be 'shots fired'! It's just an observation of what I see on this forum.