On Mon, May 25, 2015 at 7:58 PM, Luís Oliveira <luis...@gmail.com> wrote: > [just noticed I failed to include the list adress in my earlier reply] > > On Sat, May 23, 2015 at 3:21 PM, Mirko Vukovic <mirko.vuko...@gmail.com> > wrote: >> in order to get GSLL to run on Windows7+CCL+MSYS2+GSL, I needed to customize >> *cc* and *cc-flags*. Right now, I do this by modifying the code in >> grovel.lisp, as for *cc-flags*: >> >> #+(and windows msys2) >> (list "-I" "E:/msys64/mingw64/lib/libffi-3.2.1/include/" >> "-I" >> "c:/Users/977315/quicklisp/dists/quicklisp/software/cffi_0.14.0/") >> >> >> (I prefer not to modify system-wide environment variables on my PC) > > We've recently added pkg-config-cflags to cffi-grovel and cffi-libffi > was its first user. If you use CFFI from Git, which uses this scheme, > does it fix this particular problem? pkg-config needs to be in your > path, of course, but if it isn't that's probably more obvious to fix. > > [For the record, Mirko then replied he'd like to try this out via > Quicklisp rather than pulling CFFI from Git. The next CFFI release > will most likely be included in the June distribution.] > > Cheers, > > -- > Luís Oliveira > http://kerno.org/~luis/ > But libffi-win32.lisp shows no use of pkg-config-cflags; does pkg-config work on Windows? (I've already learned it doesn't work on Mac OSX.) If so, I will add (pkg-config-cflags "libffi" :optional t) to libffi-win32.lisp. I want to make sure everything works and I understand the proper way to define paths in cffi-libffi before I fix up GSLL.
Thanks, Liam
