This is the mail archive of the cygwin@cygwin.com 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: anyone have implicit linkage of gcc DLLs working in Visual C?


> lib /DEF:foo.def /OUT foo.lib

Hey, thanks!  After a little reverse engineering to verify VC's lib.exe
produces .libs which reference a DLL of the same name as the .def (e.g.
foo.dll) I've got this working.

For reference, the syntax I'm using to build and link Atlas is

gcc -mno-cygwin -shared -o ${dllname} ${defname} \
    ${input_libraries} \
    -Wl,--out-implib=${gcclibname} \
    -Wl,--enable-auto-import \
    -Wl,--no-whole-archive ${clib}
LIBPATH=`cygpath -d "C:\Program Files\Microsoft Visual Studio\VC98\bin"`
VBPATH=`cygpath -d "C:\Program Files\Microsoft Visual
Studio\Common\MSDev98\Bin"`
PATH="${PATH};${VBPATH};${LIBPATH}"
lib /DEF:${defname} /MACHINE:IX86 /OUT:${msvclibname}

and implicit linkage against the import library created by lib in Visual C++
is behaving correctly so far.  However, I haven't yet tested this out
thoroughly.

Todd


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


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