Plugin is built-in in the VM. But freetype library is coming as
separate dynamic library.
Is this ok?
There can be another option, but it would require to change the
plugin
code - to not link VM with import lib, but to load freetype.dll on
demand. The plugin can simply check if this .dll available and start
using it, or if not - fail to initialize, telling the system that
plugin functionality is not available.
I'm convinced that I'm not an expert here. I have the impression
that the second
option is better, May be we should wait for other feedback on the
idea.
I do not think Pharo's users will mind to use a different VM or add
a .dll beside their VM. Feel free to chose the simplest way for you,
and do not hesitate to ask for feedback.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
