2 ms·
Can't understand why a Lisp would be hard to build on a Mac or elsewhere. What are the dependencies besides some common C libraries (e.g. for math, unicode hand
by coldtea 7y ago
Can't understand why a Lisp would be hard to build on a Mac or elsewhere. What are the dependencies besides some common C libraries (e.g. for math, unicode handling, etc)?
- chrisseaton 7y ago> Can't understand why a Lisp would be hard to build on a Mac or elsewhere. Huge number of complex and extremely platform-specific dependencies and modules, like garbage collectors, foreign function interfaces, native code generators, etc, etc. All inherently very platform-specific, fragile, and dependent on specific tooling. Very much not plain C code.
- lloda 7y agoI build Guile on the Mac regularly. I need to pass the paths to these 4 libraries to configure: libgmp, libunistring, libiconv, and libreadline. The libraries themselves I get from MacPorts. Then make check && make install. Doesn't look all that awful to me to be honest.
- bjoli 7y agoDoing it using libraries installed by homebrew is borderline impossible unless you write your own brew formula. I have up on trying to use deps from homebrew and went with macports, and voilà: worked flawlessly. It is not unique to guile either. Compiling things on Mac os brings back memories from Redhat 8. I have had so much more luck with WSL or even cygwin than Mac os for at least a dozen open source apps.