cffi-devel

cffi-devel@common-lisp.net

1113 discussions

What Is Wrong With This Common Lisp Allegro5 Code?
by oleg harput 19 Jul '23

19 Jul '23

I wanted to use al:show-native-message-box which is equivalent of (defcfun ("al_show_native_message_box" show-native-message-box) :int (display :pointer) (title :string) (heading :string) (text :string) (buttons :string) (flags messagebox-flags)) But when i wrote: (in-package #:al-tut) (defvar *created-display*) (defun main () (unless (al:init) (al:show-native-message-box (c:null-pointer) (c:null-pointer) (c:null-pointer) "allegro init failed." (c:null-pointer) (c:null-pointer)) 'AL-INIT-FAILED) (setf *created-display* (al:create-display 800 600)) (unless *created-display* (al:show-native-message-box (c:null-pointer) (c:null-pointer) (c:null-pointer) "window init failed. " (c:null-pointer) (c:null-pointer)) 'AL-CREATE-DISPLAY-FAILED) (c:with-foreign-string (text "MessageBox Title") (al:show-native-message-box *created-display* text (c:foreign-enum-value 'al::messagebox-flags :error) (c:foreign-enum-value 'al::filechooser-modes :show-hidden) (c:null-pointer) (c:null-pointer))) (al:destroy-display *created-display*)) where (defcenum messagebox-flags (:warn 1) (:error 2) (:ok-cancel 4) (:yes-no 8) (:question 16)) in the source code. But SBCL gives me the error: 2 is not a Lisp string or pointer. [Condition of type SIMPLE-ERROR] Need help. Thanks

2 1

New failure in cl-libuv I don't understand
by Zach Beane 09 Jun '23

09 Jun '23

Full log is here: http://report.quicklisp.org/2023-05-29/failure-report/cl-libuv.html#cl-libuv Here's part of it: ; file: /home/quicklisp/quicklisp-controller/dist/build-cache/cl-libuv/9f0aced1c6a2ef1737696a9a577f65fbf922334a/cl-libuv-20230529-git/bindings.lisp ; in: DEFCFUN ("uv_loop_size" UV-LOOP-SIZE) ; (CFFI:DEFCFUN ("uv_loop_size" LIBUV::UV-LOOP-SIZE) ; LIBUV::SIZE-T) ; ; caught ERROR: ; (during macroexpansion of (DEFCFUN ("uv_loop_size" UV-LOOP-SIZE) ...)) ; Unknown CFFI type SIZE-T If I try compiling the library in isolation, it seems to work. Is it possible I've got some kind of stale fasl environment going on? Is there more research I can do to understand why this happens? Thanks, Zach

7 12

Re: New failure in cl-libuv I don't understand
by Martin Simmons 09 Jun '23

09 Jun '23

Yes, that works generally. An implementation is not permitted to implement (values) by returning NIL because that would be detectable by multiple-value-list for example. The "primary value" is used in cases where a form has to yield a value, such as in a let binding or as an argument to a function. In those cases, nil is used if there are zero values. (when nil (values)) will always return one value, nil, because (values) is never evaluated there. Likewise, (when t (values)) will always return zero values. __Martin >>>>> On Fri, 9 Jun 2023 08:35:29 -0500, Robert P Goldman said: > > Does that generally work, or is an implementation permitted to implement (values) by returning NIL? > > In the description of “primary value” in the hyper spec, I see the following: > > primary value n. (of values resulting from the evaluation of a form) the first value, if any, or else nil if there are no values. ``The primary value returned by truncate is an integer quotient, truncated toward zero.'' > > Does that license `(when nil (values))` to return NIL? > > -- > Robert P. Goldman > > On June 9, 2023 at 08:23:46, Martin Simmons (martin@lispworks.com(mailto:martin@lispworks.com)) wrote: > > > Another possible fix is to always return zero values, e.g. > > > > #.(progn > > (when (uiop:getenv "HOMEBREW_PREFIX") > > (pushnew :homebrew *features*)) > > (values)) > > > > __Martin > > > > > > > > > > > On Thu, 08 Jun 2023 16:32:36 -0500, Robert Goldman said: > > > > > > This one was my fault. I did the PR with this patch, because cl-libuv wouldn't build on my Mac. Since there's no testing, apparently, it slipped through. > > > > > > I don't know how to fix this, because I have never used CFFI-grovel, so no idea how to put Madhu's advice into practice. > > > > > > As an aside, doesn't this kind of break Faré's design principle that the person who has the information is the one who should be configuring the software? It seems like we are expecting the programmer to guess ahead of time what are all of the possible locations for the foreign library and includes. Wouldn't it make more sense for this to be configurable? > > > > > > Of course, this is partly my fault, since ASDF does not support configuring operations, except with gross dynamic variables. > > > > > > On 8 Jun 2023, at 15:32, Attila Lendvai wrote: > > > > > > > FTR, Madhu's analysis has been forwarded to the author: > > > > > > > > https://github.com/orthecreedence/cl-libuv/issues/23 > > > > > > > > -- > > > > • attila lendvai > > > > • PGP: 963F 5D5F 45C7 DFCD 0A39 > > > > -- > > > > “Nobody in the world, nobody in history, has ever gotten their freedom > > > > by appealing to the moral sense of the people who were oppressing > > > > them.” > > > > — Assata Shakur (1947–) > > > > > > >

1 0

Why does it does not work?
by oleg harput 08 Jun '23

08 Jun '23

Hi. I want to use the following C function: ;; void ClearBackground(Color color); Color is C Struct: ;; typedef struct Color { ;; unsigned char r; // Color red value ;; unsigned char g; // Color green value ;; unsigned char b; // Color blue value ;; unsigned char a; // Color alpha value ;; } Color; So I wrote: (cffi:defcstruct %color (r :uint8) (g :uint8) (b :uint8) (a :uint8)) (defvar *%lightgray* (cffi:foreign-alloc '(:struct %color))) (cffi:with-foreign-slots ((r g b a) *%lightgray* (:struct %color)) (setf (cffi:foreign-slot-value *%lightgray* '(:struct %color) 'r) 200) (setf (cffi:foreign-slot-value *%lightgray* '(:struct %color) 'g) 200) (setf (cffi:foreign-slot-value *%lightgray* '(:struct %color) 'b) 200) (setf (cffi:foreign-slot-value *%lightgray* '(:struct %color) 'a) 255) (format t "~s ~s ~s ~s" r g b a)) ;; void ClearBackground(Color color); (cffi:defcfun ("ClearBackground" %clear-background) :void (color (:struct %color))) (defun clear-background (color) (%clear-background color)) But when i run (clear-background *%lightgray*) That does not work, I have already added my .asd file ":cffi-libffi" as dependency. What is the problem? If this issue has no solution, is there an alternate way?

2 1

load-foreign-library behaviour
by Madhu 16 May '22

16 May '22

LOAD-FOREIGN-LIBRARY and USE-FOREIGN-LIBRARY have the undesirable side-effect of closing the library first before loading it. While unloading doesn't seem to work on ccl, on Lispworks, mkcl and ecl this actually does what is intended, but it has unfortunate consequences with some libraries which perform initializations which are not undone when they are unloaded. reloading the library is disastrous. the names LOAD-FOREIGN and USE-FOREIGN have nothing to suggest there is unloading involved. The expectation is that unloaded libraries are loaded. If a library is already loaded there is no expectation that it will be touched. This is the desired behaviour. In my case I have been bitten by USE-FOREIGN-LIBRARY and I changed it to not unload with the following patch. Can anyone suggest anything better? [Please don;t ask me to open a github issue, I've tried using the github channels since 2019 absolutely no success]

2 1

commit: Allow local names in WITH-FOREIGN-SLOTS
by Madhu 06 Sep '21

06 Sep '21

I notice this commit to CFFI: * commit 743a90251e5a4407147a20bd8354df03a87ca46d Author: stacksmith <stacksmith(a)users.noreply.github.com> AuthorDate: Thu Aug 19 06:34:28 2021 -0700 Commit: GitHub <noreply(a)github.com> CommitDate: Thu Aug 19 14:34:28 2021 +0100 Allow local names in WITH-FOREIGN-SLOTS It remains compatible with existing code, but accepts additional formats for bindings: 1) (name slot-name) - just like WITH-SLOTS; 2) (name :pointer slot-name) - a pointer version. On Thu, 16 Apr 2020 15:24:52 +0530 I had propsed a similar patch to Luis With a slightly different signature. | https://github.com/enometh/cffi/commit/023676a25128786174bbaa8a5df7fdc1d27c… | It seems a natural extension to me, though I was not able to | document it to my satisfaction and I don't know if it would be too | confusing to others. WDYT - (could clean it up and push it on a | separate branch if you had comments.) The doctring from that patch is reproduced here: -- (with-foreign-slots (bindings ptr type) body) - Now each binding can be one of these forms: SLOT-NAME -- binds SLOT-NAME to (FOREIGN-SLOT-VALUE SLOT-NAME) (:POINTER SLOT-NAME) -- binds SLOT-NAME to (FOREIGN-SLOT-POINTER SLOT-NAME) (VAR-NAME SLOT-NAME) -- binds VAR-NAME to (FOREIGN-SLOT-VALUE SLOT-NAME) (:POINTER (VAR-NAME SLOT-NAME)) -- binds VAR-NAME to (FOREIGN-SLOT-POINTER SLOT-NAME) (VAR-NAME (:POINTER SLOT-NAME)) -- binds VAR-NAME to (FOREIGN-SLOT-POINTER SLOT-NAME) --- This proposed syntax is different from what has been implemented by stacksmith: The last two forms above correspond to the form (name :pointer slot-name) Common Lisp bindings follow a standard syntax LHS RHS and should always be destructurable to a LHS RHS I believe introducing a nonstandard binding form with 3 elements is not in the spirit of common lisp syntax and it will only necessitate unnecessary special-casing for further macrology I would encourage stacksmith to consider this point and try to adopt the syntax I proposed for extending with-foreign-slots Or would it be possible to support both these forms in addition to the new 3 element binding form It is still early and perhaps that the syntax can be fixed before it is cast in stone - I'm hoping Luis can cooperate

2 2

Detect float type for :auto type in grovel
by Song Wei 24 Mar '21

24 Mar '21

Just checked the https://github.com/cffi/cffi/blob/master/grovel/common.h , there is a SLOT_SIGNED_P macro, which looks very interesting. I'm wondering is it a good idea to use similar trick to detect float and double for the auto type?

2 2

INT-SAP is NIL when using translate-into-foreign-memory on SBCL
by Steven Nunez 06 Nov '20

06 Nov '20

Greetings all, I first sent this message to SBCL-bugs, since the code works on CCL. where they suggested it's an issue in CFFI. I'm hoping that someone here has an idea of what the problem is. I'm wrapping some of the complex math functions in openlibm, and encounter the following stack trace when calling them: The value NIL is not of type SB-SYS:SYSTEM-AREA-POINTER when binding SB-ALIEN::VALUE ... 0: (CFFI::LIBFFI/CALL #.(SB-SYS:INT-SAP #X027C0610) NIL #.(SB-SYS:INT-SAP #X0574FFE0) #.(SB-SYS:INT-SAP #X0574FFF0)) Locals: AVALUES = #.(SB-SYS:INT-SAP #X0574FFF0) FFI-CIF = #.(SB-SYS:INT-SAP #X027C0610) FUNCTION = NIL RVALUE = #.(SB-SYS:INT-SAP #X0574FFE0) The FUNCTION parameter, which SBCL expects to be a INT-SAP, is NIL. All the other (non complex number) functions work, but those going through the foreign-memory functions fail. Openlibm is is available on any linux distribution via the package manager, and on MS Windows via MSYS2. This is with SBCL 2.0.10 on MS Windows 10.To reproduce the issue: (ql:quickload '(:cffi :cffi-libffi)) (cffi:define-foreign-library libm ;; (:windows (:or "libopenlibm" ;; #.(cl:merge-pathnames "libopenlibm.dll" cl:*compile-file-pathname*))) (t (:default "libopenlibm"))) (cffi:load-foreign-library 'libm) #+unix (cffi:define-foreign-library libm (t (:default "libopenlibm"))) (cffi:defcstruct (complex-double-c :class complex-double-type) (dat :double :count 2)) (cl:defmethod cffi:translate-into-foreign-memory ((value cl:complex) (type complex-double-type) p) (cffi:with-foreign-slots ((dat) p (:struct complex-double-c)) (cl:setf (cffi:mem-aref dat :double 0) (cl:realpart value) (cffi:mem-aref dat :double 1) (cl:imagpart value)))) (cl:defmethod cffi:translate-from-foreign (p (type complex-double-type)) (cffi:with-foreign-slots ((dat) p (:struct complex-double-c)) (cl:complex (cffi:mem-aref dat :double 0) (cffi:mem-aref dat :double 1)))) (cffi:defcfun "cacos" (:struct complex-double-c) (c (:struct complex-double-c))) ;;; Try to call the function via CFFI (cacos #C(0.16340015462715485d0 0.35359829928359165d0)) ;;; Lower level version of the above (cl:defun complex-acos (c) (cffi:foreign-funcall "casos" (:struct complex-double-c) c (:struct complex-double-c))) (complex-acos #C(0.16340015462715485d0 0.35359829928359165d0)) Any ideas?

2 1

I need your CFFI help.
by oleg harput 04 Nov '20

04 Nov '20

*In cl-raylib library (cffi version of raylib game development library) * *there are many constants inside* *https://github.com/longlene/cl-raylib/blob/master/src/raylib.lisp <https://github.com/longlene/cl-raylib/blob/master/src/raylib.lisp>* *like* (define-constant +lightgray+ '(200 200 200 255) :test #'equal) (define-constant +gray+ '(130 130 130 255) :test #'equal) ... *I can call those constants in my program like* cl-raylib:+lightgray+ cl-raylib:+gray+ ... *Inside that file there are many things like * (defcstruct (%vector2 :class vector2-type) "Vector2 type" (x :float) (y :float)) (defstruct vector2 x y) (defmethod translate-from-foreign (pointer (type vector2-type) (with-foreign-slots ((x y) pointer (:struct %vector2)) (make-vector2 :x x :y y))) *In cl-raylib there are functions that take "vector2" type as input for example: *DrawTriangleLines(Vector2 v1, Vector2 v2, Vector2 v3, Color color); *But i can not reach them.* *How can i call them if i can call them directly?, do i need to create them? What must i do? What is the solution? What must i do?*

2 1

How can we get an optimized surface in cl-sdl2?
by oleg harput 26 Oct '20

26 Oct '20

(let* ((SURFACE (sdl2:load-bmp "/home/huseyin/quicklisp/local-projects/sdl2-made-easy/assets/gods.bmp")) (OPTIMIZED-SURFACE (sdl2:convert-surface SURFACE sdl2:+pixelformat- unknown+))) as i understand, in order to get an optimized surface the second argument of "sdl2:convert-surface" must be one of many constants in "constants.lisp" file: (defconstant +pixelformat-unknown+ sdl2-ffi:+sdl-pixelformat-unknown+) (defconstant +pixelformat-index1lsb+ sdl2-ffi:+sdl-pixelformat-index1lsb+) (defconstant +pixelformat-index1msb+ sdl2-ffi:+sdl-pixelformat-index1msb+) ... Here i choosed the first one because i have no idea which one i must choose. Is that enough in order to get an optimized surface in cl-sdl2?

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

cffi-devel