Apple Silicon Support

[spfennell]

No description provided.

[spfennell]

I got this to work but its ugly, and for some reason SIM_amoeba (with monte carlo) is giving me problems. I had this problem before but I can't remember the fix.

• Checkout the master branch of Trick

• Follow the install guide instructions for Intel to get all dependencies, except ignore any llvm installation instructions. https://nasa.github.io/trick/documentation/install_guide/Install-Guide#macos-monterey-big-sur-catalina

• brew install ninja. For some reason I had issues when using Unix Makefile to build llvm, so we will be using ninja instead. It's possible that it was because I built for all target architectures instead of just AArch64 when I was using the Unix Makefile.

• Download llvm 13 source code from their github (either clone or release) and build and install using the following commands. See these link for more details, but the command below should work. Make sure to change the install prefix if you want to put llvm somewhere else besides your home directory.
  https://llvm.org/docs/CMake.html#quick-start
  https://clang.llvm.org/get_started.html
  https://llvm.org/docs/GettingStarted.html

cmake -G Ninja -DLLVM_ENABLE_PROJECTS=clang -DLLVM_TARGETS_TO_BUILD=AArch64 -DCMAKE_INSTALL_PREFIX=${HOME}/llvm13-aarch64 ../llvm
cmake --build .
cmake --build . --target install

• add these flags to your environment (you can add them to your .zshrc in your home directory and source the file or relaunch the terminal)

export PYTHON_VERSION=3
export TRICK_CXXFLAGS="-g -I/opt/homebrew/include -L/opt/homebrew/lib -Wno-unused-command-line-argument"
export TRICK_CFLAGS="-g -I/opt/homebrew/include -L/opt/homebrew/lib -Wno-unused-command-line-argument"

• configure trick with this command (change the llvm location if you changed the install prefix earlier):

./configure --with-llvm=${HOME}/llvm13-aarch64 --with-udunits=/opt/homebrew

• Then make.

This passes all tests except for SIM_amoeba, which has some issue with monte host/slave connection. I've had this problem before so it may be unrelated to the M1 build.