dll links or pkgconfig/libtool information is wrong

Dave Korn dave.korn.cygwin@googlemail.com
Tue May 26 15:48:00 GMT 2009

jean-luc malet wrote:
> hi!
> I'm creating a dll using gcc and cygwin
> this dll use 2 others dll : -lglut -lGL
> $pkg-config.exe --libs gl
> -lGL
> but /bin/ contain cygGL-1.dll
> when static linking with -lGL this works fine because libGL.a exist
> when creating the dll -lGL don't work at all, I have to specify -lGL-1
> doing
> /bin/$ ln -s cygGL-1.dll cygGL.dll
> solve the issue
> I have similar issue with some libtool based library

  Normally for every /bin/cygDLLNAME-VERSION.dll, there should be a
/usr/lib/libDLLNAME.dll.a that contains import stubs, allowing you to link
against whatever DLL is current without needing to specify the version number
as you have done.  Generally these import libraries live in the corresponding
-devel package for whichever package you got the DLL from, and GL is no
exception; using the package search page


to search for "libGL.dll.a" suggests that you need to install the
"libGL-devel" package, to go alongside your already-installed "libGL1" package
where the DLL came from.


Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

More information about the Cygwin mailing list