search

kiselgra / c-mera

Next-level syntax for C-like languages :)
Other
408 stars 17 forks source link

build steps for osx #101

Open seanjensengrey opened 5 years ago

seanjensengrey commented 5 years ago

This is not a bug but an quick guide for folks building c-mera on OSX.

These are the steps I went through to get the cm tool installed on OSX using homebrew. I am not a Common Lisp developer, so all of this was new to me.

The existing readme build steps are pretty good, but there are a couple little gotchas.

install deps

brew install clozure-cl gpg autoconf automake m4

add new m4 to path, shadows existing m4

export PATH="/usr/local/opt/m4/bin:$PATH"

create symlink for ccl

clozure-cl only install ccl64, build scripts expect ccl

pushd /usr/local/bin; ln -s ccl64 ccl; popd

install quicklisp

https://www.quicklisp.org/beta/#installation

install network library

ccl --eval "(ql:quickload :net.didierverna.clon)"

build

git clone https://github.com/kiselgra/c-mera
cd c-mera
# fixed an odd build breakage when running configure
mkdir m4
autoreconf -if
./configure --prefix=$HOME/opt/c-mera --with-ccl
make
make install

The cm tool will now be in $HOME/opt/c-mera/bin/

kiselgra commented 5 years ago

Hi,

thanks for putting this up here!

One open point that I take away from this: make sure we have the correct binary name for ccl (or make it configurable). Another one: integrate your dependency list into our readme. Maybe even most of your report, but I'd wait until we figure out what went wrong (below) and fixed the issues (above).

Do you know why you had to create the m4 directory? Do you think there is something wrong with our configure.ac?

I have never worked on a mac, so this might be a stupid question: is there something corresponding to debian's build-essential package that you could have used (instead of listing the auto* individually)?

A minor note: clon is the command line argument library we use :)