[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

MinGW DLLs and autoconf parsing

From: Jason Curl
Subject: MinGW DLLs and autoconf parsing
Date: Fri, 11 Jul 2008 22:24:33 +0200 (CEST)


Recently some info was posted about using resource files with Windows 
compilers. I'm trying to generate a reasonably simple Version resource and 
there's some information I'm not sure how I can extract from the build process. 
I'm using libtool-1.5.27a on MSYS-1.0.10 with MinGW-5.1.4.

Question 1:
One of the fields is "OriginalFilename". When the shared DLL is built, it is 
installed "libfoo-1.dll". I've created a "" file that autoconf 
generates for me, substituting information from the build process directly into 
this resource file.

However, how might I get the name of the library before it is built?

Question 2:
The second task is the versioning. There are two fields, both of the format:
FILEVERSION major,minor,revision,build

I need to substitute them based on the version information given to libtool 
during the linking phase.

How can I convert the string "1:0:0" to a major.minor.revision field? How does 
this work?

Question 3:
As the libtool --tag=RC doesn't work for 1.5.27a (it complained about an 
unknown tag), I wrote the rule:

        $(LIBTOOL) $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --tag=CC --mode=compile 
$(RC) $(RCFLAGS) $< -o $@

where RC=windres and RCFLAGS is empty. It works, but is it safe? I don't know 
when MinGW will upgrade the autotools.

Thanks & Best Regards,

Jetzt komfortabel bei Arcor-Digital TV einsteigen: Mehr Happy Ends, mehr 
Herzschmerz, mehr Fernsehen! Erleben Sie 50 digitale TV Programme und optional 
60 Pay TV Sender, einen elektronischen Programmf├╝hrer mit Movie Star 
Bewertungen von TV Movie. Au├čerdem, aktuelle Filmhits und spannende Dokus in 
der Arcor-Videothek. Infos unter

reply via email to

[Prev in Thread] Current Thread [Next in Thread]