This makes my life less miserable when doing releases on the GH mirror,
because I don't have to manually edit the installer filenames before
uploading any more.

GitHub doesn't like blanks in upload file names, using dashes instead
makes uploading much easier and eliminates the need to zip the installer
before uploading. We also include a proper cpu architecture designation
(x86 or x86_64) in the output file name in lieu of the '(64 bit)' suffix
which causes trouble in GH uploads as well, because of the parentheses.

Note that this shouldn't affect the Gitlab CI since it looks for a
'Purr*.exe' build artifact, which will still match the package name.

pd-lua now uses the latest pd-lib-builder and includes lua as a
submodule, so building it becomes a lot easier. Most notably, Lua 5.4 is
linked statically from lua/onelua.c, so Lua isn't needed as a build or
runtime dependency any more and the resulting external will use exactly
the same Lua version across different platforms.

This gives the same treatment to the audio devs as the previous commit
does to the MIDI devices, adding new audioindevname and audiooutdevname
keys to the preferences, which enables us to remap device indices on the
fly at startup in case the device list has changed during invocations.

This adds new midiindevname and midioutdevname keys to the preferences,
which enables us to remap device indices on the fly at startup in case
the device list has changed during invocations. (Which happens a lot, in
particular, with the portmidi backend, due to MIDI devices being plugged
and unplugged, change of virtual MIDI devices, etc.)

Note that this doesn't provide hotplugging support, which is really what
we'd like to have, but is currently impossible due to backend
limitations. But at least Purr Data will not connect to the wrong
devices on relaunch any more, which previously was a major annoyance.

These need to be massaged so that they work on Apple arm64 cpus.
Backported from vanilla, cf.:

https://github.com/pure-data/pure-data/commit/deff7957
https://github.com/pure-data/pure-data/commit/69b444ad
https://github.com/pure-data/pure-data/commit/000b7611

On Apple Silicon, Homebrew is installed in a different location. Thus
in the externals Makefile and the embed-MacOSX-dependencies.sh script,
we now check the HOMEBREW_PREFIX environment variable to determine
whether Homebrew is installed and, if so, where it is.

Also added missing include and library paths in some externals so that
they actually find the Homebrew header files and libraries.

Specifically, we disable the branches which attempt to detect iOS
cross compilation by checking for a Darwin system with arm cpu
architecture. With Apple Silicon Macs this test is now broken, since
an M1/M2 Mac would be detected as an iOS target.

For now, we skip this check by looking for a non-existent arm-iphone
architecture. This should be fine since currently we don't support iOS
anyway, and AFAIK Purr Data has never been tested there. If we want to
revive iOS cross compilation at some point, we'll have to devise a
check which will do the right thing on both iOS and macOS arm devices.

Albert Gräf authored 2 years ago and Albert Gräf committed 2 years ago

Specifically, cmd+1-9 don't appear to work, at least not from nw.js
0.42.4 onward. We work around this by adding corresponding keydown
event handlers in pdgui.js which are invoked from pd_canvas.c in order
to deal with various key bindings that need special treatment for
various reasons.

See: https://github.com/pd-l2ork/pd-l2ork/commit/d657ae67