Arm Apple Silicon, Deken and binary releases

[domenicostefani]

Hi, I'm dealing with students from an HCI master degree and others that are not always versed in "computer stuff". This year, Apple silicon users have told me that mrpeach is not available in Deken, while it's fine for Intel Mac users. I also do not have an Arm Mac to try and compile this for them.

Is there any chance that:

• An Apple Silicon version of mrpeach can be added to Deken,
• Compilation instructions can be added to the README here (so that less experienced user can compile this),
• Binaries can be added to the "Releases" section (like SDT);

[umlaeute]

i think 1 & 3 are rather "unlikely"

mrpeach has been (mostly) factored out into separate repositories, and new users should pull the individual packages.

• binfile: available for Darwin/arm64 on deken; also note that the new vanilla [file] object probably makes this obsolete anyhow
• midifile: missing(!)
• slip: available on deken
• osc: available on deken (and if possible, you probably should use Pd's builtin OSC objects)

do you need anything else?

as for 2, sure, PRs welcome :-)

in practice it really boils down to:

• Install Pd at a common location
• Install a build environment
• Run make

The hard part is of course the "Install a build environment", but I'm afraid that this is quite beyond the scope of a project like this. (aka: i think there should be a central place for such instructions, where separate externals can point to; i don't know of such a place).

[danomatika]

Most externals are pure C/C++ without dependencies and building them usually comes down to make.

Following the steps outlined by @umlaeute, for modern macOS systems, setting up and building such an external usually boils down to:

1. download and install a Pd.app to /Applications
2. in Terminal, install Commandline Tools build environment:

   xcode-select --install

   Note: running git on the commandline on a fresh system will helpfully suggest to run the above...

3. in Terminal, git clone the external sources. I usually suggest to ~/Pd/Documents/externals
4. in Terminal, cd to the external source dir
5. build

   make

6. add path to built external dir to your Pd paths in the preferences

For externals with dependencies, etc most libraries can be installed by Homebrew. Note: libraries linking Homebrew libraries are generally not distributable, ie. can't be simply copied onto another machine.