I'm trying to catch up on recent changes made to CFFI with regard to path discovery with the idea of simplifying code, both in CFFI itself, and in GSLL (which uses CFFI). The grovel option pkg-config-cflags seems to permit the elimination of some other code in e.g. libffi-unix.lisp. With the presence of (pkg-config-cflags "libffi" :optional t), it seems like these could be eliminated:
#+darwin (cc-flags "-I/opt/local/include/")
#+openbsd (cc-flags "-I/usr/local/include")
and these
#+darwin (include "ffi/ffi.h") #-darwin (include "ffi.h")
could be replaced with (include "ffi.h")
Is that correct? Not a darwin or openbsd user so can't test myself.
Thanks, Liam
On Sat, Jul 11, 2015 at 9:45 PM, Liam Healy lnp@healy.washington.dc.us wrote:
I'm trying to catch up on recent changes made to CFFI with regard to path discovery with the idea of simplifying code, both in CFFI itself, and in GSLL (which uses CFFI). The grovel option pkg-config-cflags seems to permit the elimination of some other code in e.g. libffi-unix.lisp. With the presence of (pkg-config-cflags "libffi" :optional t), it seems like these could be eliminated:
#+darwin (cc-flags "-I/opt/local/include/")
#+openbsd (cc-flags "-I/usr/local/include")
and these
#+darwin (include "ffi/ffi.h") #-darwin (include "ffi.h")
could be replaced with (include "ffi.h")
That would have been a nice simplification. Alas, AFAICT, OS X does not ship with pkg-config. (And even if one installs pkg-config, the system-installed libffi is not registered in the pkg-config database.)
I don't know about OpenBSD.
Cheers,
-
Liam Healy -
Luís Oliveira