To
the best of my understanding, these are not issues with BEAGLE.
BEAGLE v4 on Mac is now a universal build that supports x86 and ARM64
execution automatically. Rather, the issues seem to be related to Apple
changing the default search paths on M1 systems when executing BEAST
through the GUI application. I have found a patch that works and
expect to provide an updated BEAST release relatively soon. In the
meantime, here's how one can make the patch on their local computer:
1. Open in Finder the directory that contains the BEAST
v1.10.4.app2. Control-click to Show Package Contents
3. Open in a text editor Info.plist
4. Change this line:
<string>-Xmx2048M</string>
to now read
<string>-Xmx2048M -Djava.library.path=/usr/local/lib</string>
As
far as I can tell, these issues do not arise when using the
command-line script `beast` since that script already adds the necessary
java.library.path VM option.
best, Marc