Curtis L. Olson writes: > Christian Mayer writes: > > PS: So there's just the #include <zlib.h> issue left to be > > fully MSVC "friendly"... > > Typically in the unix world, you would install packages like zlib into > a place where the compiler expects to see them, or some other place > and inform the compiler where to look. > > In the linux world, the packaged version of zlib would typically > install the library in /usr/lib/libzlib.a and the header in > /usr/include/zlib.h > > If you were compiling and building the package from source yourself, > the convention is 'usually' that you put it in /usr/local, so > /usr/local/lib/libzlib.a and /usr/local/include/zlib.h > > The "configure" script automatically tells the make system to tell the > command line compiler to look in /usr/local/ for includes and libs: > -I/usr/local/include and -L/usr/local/lib > > I would think that in MSVC you should be able to do something > analogous. Either install the libs and headers someplace where the > MSVC compiler expects to find these things, or install them someplace > else and tell the compiler where to find them. >
Surely you can just put libzlib.a in vc\lib and zlib.h in vc\include? Cheers - Dave -- [EMAIL PROTECTED] _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
