cffi-devel April 2020

cffi-devel@common-lisp.net

2 participants
2 discussions

unwanted recompilation with :CFFI-GROVEL-FILE
by JTK 16 Apr '20

16 Apr '20

Hello, Sorry if this is the wrong place to ask ... I’m using the ‘osicat’ package ( https://common-lisp.net/project/osicat/ <https://common-lisp.net/project/osicat/> and https://github.com/osicat/osicat <https://github.com/osicat/osicat> ) in SBCL on OSX. whenever I do ‘(asdf:load-system “osicat”) it seems to recompile the cffi-grovel-files and their dependencies. Is this normal, or is there some way to make it behave like asdf usually does, that it recompiles only when a file has changed? I know that this issue has 3 components (asdf, cffi, and osicat), but I thought I’d first check whether this is an unavoidable feature of using grovel files. If not, I can try to fix osicat. Here are some of the compilation messages: https://pastebin.com/GKArFCWc <https://pastebin.com/GKArFCWc> JK

2 5

size_t questions
by JTK 15 Apr '20

15 Apr '20

Hello, From the CFFI manual, Section 4.9, I understand that >> "Implementor’s note: size_t is almost always an unsigned int.” However, this seems to fail on a 64 bit Linux computers, where the C ints are 32 bit I’ve had better success with (cffi:defctype size_t #.(cond ((= 4 (cffi:foreign-type-size :pointer)) :uint32) ((= 8 (cffi:foreign-type-size :pointer)) :uint64) (t (error "Failed type lisp-pointer-type")))) Is this general enough to be trusted everywhere? If so, should it be part of CFFI, or at least mentioned in the manual? The current text in the manual doesn’t seem to be working for me, and this is a frequent issue when I port a new foreign library and forget what I did in the past … first thing I do is (apropos “size-t” :cffi) and (apropos “size_t” :cffi) and nothing shows up. Best regards, J.K.

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

cffi-devel April 2020