LibTiff Mailing List
TIFF and LibTiff Mailing List Archive
April 2009
Previous Thread
Next Thread
Previous by Thread
Next by Thread
Previous by Date
Next by Date
Contact
The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems
Thread
2009.04.08 20:31 "Re: cannot link to my own libtiff.lib", by Christian Henning
Thanks Bob, that was the solution. Unfortunately, for TIFFSetErrorHandler and TIFFSetWarningHandler I still get the linker error. I wonder how the Win32 libtiff binaries are build, since here everything works flawless. Regards, Christian On Wed, Apr 8, 2009 at 11:47 AM, Bob Friesenhahn <bfriesen@simple.dallas.tx.us> wrote: > On Wed, 8 Apr 2009, Christian Henning wrote: > >> Hi there, I have compiled the beta3 of libtiff-4.0. As the makefile.vc >> states, all I have to do is to: >> >> nmake /f makefile.vc >> >> I did that and everything went ok. Meaning I created a libtiff.lib and >> libtiff.dll. But I cannot link to it. I get the following errors: >> >> 1>read_image.obj : error LNK2019: unresolved external symbol >> __imp__TIFFClose referenced in function _wmain > > This sounds like a dllimport/dllexport issue. Since libtiff does not > decorate the code with dllimport/dllexport, it seems likely that including > libtiff/libtiff.def into your project will help. This will tell MSVC which > functions are exported. > > Bob > -- > Bob Friesenhahn > bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ > GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ >