[squeak-dev] Linking a plugin with a library

John Daniels jd at syntropy.co.uk
Mon Apr 27 13:23:02 UTC 2009


Thanks Igor, that was exactly the information I needed.

--John

====
Original message
From: Igor Stasenko <siguctua at gmail.com>
Date: 27 April 2009
Time: 12:39:42 PM
Subject: [squeak-dev] Linking a plugin with a library
----
2009/4/27 John Daniels <jd at syntropy.co.uk>:
>> A common way is to link the required library statically. That way your
>> users do not have to worry about dependencies, installing DLLs with
>> the right versions etc. To do that, add the mylibrary.a file to the
>> linker command line.
>
> That's what I'd like to do but I don't have a makefile for my plugin,
> or at least, I haven't created one. It just seems to get made
> automatically. What would be in such a makefile, and where would I put
> it? The default makefile (assuming that's what's being used) is mostly
> doing what I want except for the specification of the extra library.
>
> Sorry to be such a dunce!
>

Just add a 'makefile' file to the directory where platform files of
plugin are located
(platforms/win32/plugins/YourPluginName/makefile)


here an example of makefile, for freetype plugin:
---------------
include ../../Makefile.plugin

# This seems broken, but in the generated FT2Plugin.c there is an
# include<tttables.h> which should be include<freetype/tttables.h>
# so we simply add it to the include path. Eeek.
INCLUDES+= -I$(WIN32DIR)/freetype

# Add the freetype libs to the build
EXTRALIBS=$(WIN32DIR)/freetype.a
-----------------


> Thanks again,
>
> --John
>
>
>



-- 
Best regards,
Igor Stasenko AKA sig.




More information about the Squeak-dev mailing list