cffi-devel July 2015

cffi-devel@common-lisp.net

4 participants
3 discussions

How to customize cffi-grovel:*cc*, *cc-flags*?
by Mirko Vukovic 03 Aug '15

03 Aug '15

Hello, 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) I see alternate ways of achieving the same effect: 1. Write own gsll loader that customizes *cc* and *cc-flags* 2. Write own cffi-libffi loader that customizes the variables 3. (somehow) advise gsll or cffi-libffi loaders in my lisp-init files to customize the variables 4. Modify environment variables for my process. What is the advised way to do this? I would prefer 3: in my lisp startup file, I (somehow) write some advice code to asdf that customize *cc* and *cc-flags*. But I don't know how to do that. Thank you, Mirko

3 5

Path discovery and simplification of libffi-unix.lisp
by Liam Healy 21 Jul '15

21 Jul '15

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

2 1

Using CFFI: dealing with a writeback buffer
by Victor 15 Jul '15

15 Jul '15

Hi all, I don't know if it is the best place to ask this question, but I'll try it. I am trying to wrap around a following function: OGRErr OSRExportToProj4(OGRSpatialReferenceH r, char **buff); This function allocates the string and assigns it to the (char*) pointer passed as buff and then its contents should be copied into a C string and the obtained pointer released via CPLFree(); So, basically, in C a typical usage would be: char *proj = NULL: OSRExportToProj4(handle, &proj); printf("%s\n", proj); CPLFree(proj); And the question is: how is this function should be wrapped with CFFI? Thanks, Victor -- реклама ----------------------------------------------------------- FREEhost.UA - быстрый и удобный хостинг доступный каждому. http://freehost.com.ua/unix/

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

cffi-devel July 2015