Update the doc about building and running on macOS

[lkuty]

On macOS M2, I had to point to the directory containing the CBQN library to build and run beacon. The directory where CBQN was installed on my system is /Users/ludo/Downloads/github/CBQN. Could you update the README ?

Building and running:

export DYLD_FALLBACK_LIBRARY_PATH=/Users/ludo/Downloads/github/CBQN
RUSTFLAGS='-L /Users/ludo/Downloads/github/CBQN' cargo run --release

[vmchale]

I think the way cargo handles linker flags on OSX is hinky. I use the following:

install_name_tool -add_rpath /usr/local/lib target/release/beacon

(/usr/local/lib is where my BQN shared library is)

This creates an executable that I can use.

[x86y]

On macOS M2, I had to point to the directory containing the CBQN library to build and run beacon. The directory where CBQN was installed on my system is /Users/ludo/Downloads/github/CBQN. Could you update the README ?

Building and running:

export DYLD_FALLBACK_LIBRARY_PATH=/Users/ludo/Downloads/github/CBQN
RUSTFLAGS='-L /Users/ludo/Downloads/github/CBQN' cargo run --release

I think the way cargo handles linker flags on OSX is hinky. I use the following:

install_name_tool -add_rpath /usr/local/lib target/release/beacon

(/usr/local/lib is where my BQN shared library is)

This creates an executable that I can use.

61ad52e

I added some build.rs code to take care of this during the build stage. Just cloning and running cargo run --release should work now.