2009.03.04 17:22 "Re: [Tiff] Building Libtiff in Visual Studio under Windows?", by Steven Lehar
If I remove the
Project > Properties > C/C++ > Additional include directories
then the error on build becomes
Error 1 fatal error C1083: Cannot open include file: 'tiffio.h': No such file or directory c:\documents and settings\flight landata\my documents\visual studio 2005\projects\testtifflib\testtifflib\testtifflib.cpp 5 I have tried moving #include "tiffio.h" from stdafx.h to TestLibTiff.cpp but that doesn't fix it.
On Wed, Mar 4, 2009 at 12:17 PM, Steven Lehar <firstname.lastname@example.org> wrote:
Oh, and I forgot to mention (but didn't forget to do)
nmake /f Makefile.vc
which eventually (after some initial problems) completed without errors, so I have compiled the library from source.
On Wed, Mar 4, 2009 at 12:15 PM, Steven Lehar <email@example.com> wrote:
Thanks a lot for your help guys, I'm *ALMOST* there now!
I downloaded LibTiff from ftp.remotesensing.org tiff-3.8.2.zip, installed it in C:\Program Files\tiff-3.8.2,
edited libtiff\tiffconf.h and commented out...
/* #define JPEG_SUPPORT 1 */
/* #define PIXARLOG_SUPPORT 1 */
/* #define ZIP_SUPPORT 1 */
as suggested in the documentation (after discovering it was indeed necessary)
There is no tiff-3.8.2\include folder, but I found a bunch of *.h files in tiff-3.8.2\libtiff. Now in Visual Studio, in my TestLibTiff project I did
Project > Properties > C/C++ > Additional Include Directories, added
Project > Properties > Linker > Additional library directories, added
In stdafx.h added
then [F5] (build solution) and I get this error:
Error 1 error LNK2019: unresolved external symbol _TIFFOpen referenced in function _wmain TestTiffLib.obj
Error 2 fatal error LNK1120: 1 unresolved externals C:\Documents and Settings\Flight Landata\My Documents\Visual Studio 2005\Projects\TestTiffLib\Debug\TestTiffLib.exe 1 Any idea what I might be missing?
On Tue, Mar 3, 2009 at 4:32 PM, Edward Lam <firstname.lastname@example.org> wrote:
For Windows, I suggest just building libtiff yourself from source using nmake. See:
It seems rather backwards to me to use gcc on Windows unless you absolutely have to when you have access to such a great debugger like Visual Studio.