Awesome. I'll leave this for a day to let somebody who knows cmake well to also have a glance. I checked it through a bit too.

portaudio is a submodule now, right ?

Yes, portaudio is a submodule. It already was since that previous build system related commit, but in this version it is obligatory for Windows. Keeping the options of both building portaudio as part of the SC build or providing libraries compiled outside of SC made subsequent code a lot more complicated and intransparent. Since the audio APIs provided now are the same than you would get from a portaudio build outside of SC I thought this was the preferable way.

To come back to the question of where that submodule/pa-fork should reside: I'd actually prefer to see it in the SC repo, not because of any burden it creates while it's in my repo, but because if people wanted to commit to the fork, they'd have to go through my repo. That would make me kind of a gate-keeper of portaudio on SC, something I'd prefer not to be...

okay, let's fork from yours into the supercollider org.

Great! Should I do it, or will you? It's not urgent, of course...