"External" Libraries in KDE4 apps

Christian Ehrlicher Ch.Ehrlicher at gmx.de
Wed Sep 26 22:34:05 CEST 2007


Andreas Pakulat schrieb:
> On 26.09.07 21:27:45, Christian Ehrlicher wrote:
>> Andreas Pakulat schrieb:
>>> I'd like to get some clarifications about the various issues with
>>> libraries on win32.
>>>
>>> Is it possible to use static libraries on win32? If so whats needed for
>>> that, I guess 2 separate builds for mingw and msvc?
>>>
>> it is possible as long as you use the same compiler switches for all
>> libs you want to combine.
> 
> Well, I suspect thats not going to happen if plugin == lib (I'm going to
> use the svn stuff in a kdevelop plugin).
> 
You need to use the same switches for foo.lib and foo2.dll when you want
to link static foo.lib to foo.dll
>>> Is it relatively easy to convert a static lib into a shared lib when
>>>
>>> - its a shared lib on unix already (but seemingly not using gcc
>>> visibility)
>>> - the list of to-be-exported classes is very clearly defined
>>> ?
>> Imho there's no chance to convert a shared lib to a static one and vice
>> versa.
> 
> What I meant is, convert the MSVC buildsystem to create a shared lib
> instead of a static one, which should only need to declare the exported
> classes properly I think...
> 
Ok, that's possible as long as you use .vcproj. Changing a Makefile
project is more complicated.
You just need to declare the export classes, correct.


Christian



More information about the Kde-windows mailing list