On Wed, 2022-04-27 at 08:42 +0200, IOhannes m zmoelnig wrote:
so here's a better solution (also untested). instead if *everything* i wrote above do this:
- find the file Pd.app/Content/Resources/tcl/pd-gui.tcl
- open it in an editor
- locate the line (somewhere around line:846) that says:
"[exec -- $pd_exec -guiport $::port {*}$::pd_startup_args &]" 4. in this line put an "arch -x86_64" before the $pd_exec, so it now reads: "[exec -- arch -x86_64 $pd_exec -guiport $::port {*}$::pd_startup_args &]"
That's valuable to know. Thanks, IOHannes. I still have two questions regarding this matter:
1. How does Deken detect current platform/arch? Does it something like `uname -m` or does it check what arch Pd has, or something else?
2. Does the code-signing take into account only the compiled binaries or the whole app? Do I have to re-code-sign after having modified pd- gui.tcl?
BTW: I have access to an M1 with macOS Monterey and hopefully will soon be able to build a few externals and test stuff.
Roman