This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Cygwin's libtool, passing .def file name to gcc during linking

Ha, who'd have thought...

I found it. I can use '--export-symbols plugin.def' for this. Even though the plugin.def doesn't contain exports, but imports... (this is a plugin library that invokes functions contained in the executable that loads the library...)


Maarten Boekhold wrote:


I'm trying to port an application to Cygwin that uses libtool to drive compilation/linking.

This application needs to be linked with a ".def" file during the linking stage, i.e. (formatted to make it readable)

/bin/bash ./libtool --mode=link gcc  -g -O2
                    -o -rpath /usr/local/lib
                    libplugin_la-plugin.lo -lgobject-2.0
                    -lglib-2.0 -lintl -liconv plugin.def
rm -fr  .libs/libplugin.dll.a
gcc -shared  .libs/libplugin_la-plugin.o
    -L/usr/lib /usr/lib/libgobject-2.0.dll.a
    /usr/lib/libglib-2.0.dll.a /usr/lib/libintl.dll.a
    /usr/lib/libiconv.dll.a  -o .libs/cygplugin-0.dll

as you see I'm trying to pass a 'plugin.def' filename to libtool, with the intention this shows up in the GCC command. It doesn't, and I can't figure out how to pass this apart from manually hacking libtool.

Anybody have any suggestions?

(btw. the reason I send this to the cygwin list is that I know the cygwin version of libtool is somewhat hacked. I'm using devel btw.)


Unsubscribe info:
Problem reports:

-- Unsubscribe info: Problem reports: Documentation: FAQ:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]