v1.6 RC1 on Win64
nightstrike at gmail.com
Fri Sep 4 06:27:08 CEST 2009
2009/9/3 Lukáš Lalinský <lalinsky at gmail.com>:
> 2009/9/4 NightStrike <nightstrike at gmail.com>:
>> 2009/9/3 Lukáš Lalinský <lalinsky at gmail.com>:
>>> 2009/9/3 NightStrike <nightstrike at gmail.com>:
>>>> Also, please see these two (very small) patches for consideration from 1.5:
>>> Definitely not, we are building dll by default. A patch to add support
>>> for static library would be welcome, though.
>> Well, I could add that in to your auto* system, although it'd probably
>> be a good idea to update a lot of the old constructs with current
>> autoconf. I can do both if you like.
> The autotools build system will go away right after the 1.6 release. I
> have no problem accepting a patch for it in 1.6, but combined with the
> KDE-specific configuration it's so bad that I don't think updating the
> autoconf script to newer constructs is worth the work.
What are you replacing your build system with?
>> So basically, you don't support building a static library on windows at all?
It looks like just adding --enable-static did the trick. I'm left
with a few .a files, at least.
More information about the taglib-devel