Then (yes, captain obvious) there is some problem when loading the library :) Now, if you exchange the dylib from cairo and it works, there is a problem in how the library is packaged/compiled. I would not say a VM problem, nor a NativeBoost one. Esteban? :) On Thu, Jun 19, 2014 at 12:49 PM, Stephan Eggermont <stephan@stack.nl> wrote:
Guiile wrote:
Just to understand a bit more... Mayne I'm wrong, but I think Cairo is loaded dynamically by the VM, as it is a library used in FFI and it is not a plugin. So it will appear in that list, just after you use it.
I made the list after I tried using it, and it failed to find cairo. "Error: failed to get a symbol address: cairo_image_surface_create" And I have 26 dylibs in the plugins directory. If I replace the libcairo.2.dylib by that from the december version, (and force the use of free type fonts...) Roassal2 works (with the text size issues)
Stephan