On Tue, Dec 13, 2011 at 10:24 AM, Ryan Johnson wrote: > On 13/12/2011 1:16 PM, Brian Craft wrote: >> >> I'm building a few libraries which are dependencies of a program I'm >> building. Most of them build via autotools. Doing "make install" >> installs files *.a, *.la, *.dll.a. Linking the executable succeeds >> without error, however when running it, the loader complains that it >> can't find cyg*.dll files. E.g. if it was libfoo.a that was installed, >> the executable wants cygfoo-6.dll to run. >> >> These cyg-*.dll files exist in the build directories, generally in >> src/.libs . The program will run if I add all of these to the PATH. >> >> Seems like either the link or the install isn't working as it should. >> Are there docs anywhere that explain how this is supposed to work? > > The lib*.a file is a stub which allows proper linking of the actual dll > (exporting symbols, etc.). Linking against it doesn't remove the need to > have the cyg*.dll available at runtime. >
Ok, but why don't autotools know about this? And why don't I see cyg*.dll files, for example, in /usr/lib? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
