Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quicklisp, asdf and loading sequence - proper usage and loading order #23

Open
stacksmith opened this issue Oct 30, 2017 · 1 comment
Open

Comments

@stacksmith
Copy link

stacksmith commented Oct 30, 2017

I am still having trouble using this library - as well as related cl-xcb-xlib (and -demos). I think I am not understanding the intended use case.

The problem is that the libraries seem to require explicit runtime loading - the asdf dependencies don't seem to be enough. Is there some kind of swig or cffi requirement? Also the sequence of loading seems to be important - cl-xcb-xlib must be loaded first?

@rpav
Copy link
Owner

rpav commented Oct 31, 2017

Well, cl-xcb-xlib isn't required and at this point likely doesn't work. I had actually written c2ffi to address the unmaintainability of its SWIG configuration, but perhaps ironically never got around to actually applying it (in part due to only recently implementing SBV in autowrap).

cl-cairo2 itself is usable as-is and you can use it to draw into memory. Most of the time this is sufficient; if you're using GL or similar it's the most straightforward way.

I'm not 100% certain on the examples; the PNG ones should work, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants