Greg Ercolano wrote:
> Paul R wrote:
>> Well here is an excerpt from the log now
>> it is 14 errors in total, all almost the same..all about png and i have
>> added every library now..so it is linking order or something??
>>
>> .\fltk13rc2\lib\libfltk_png.a(pngread.o):pngread.c|| undefined reference to
>> `inflateInit_'|
>> .\fltk13rc2\lib\libfltk_png.a(pngread.o):pngread.c||
Oh, you're using windows. (I missed those backslashes).
My (a) approach won't work for you.
For the (b) approach, just rebuild the 'images' demo program
in Visual Studio and look at the "Build Log" to see all the
linker flags and lib order.
Note that in FLTK, the images routines are separated from the
main fltk.lib, so that apps that don't need images don't have
to include all that overhead of image libs and such.
When you build an app that uses images, you need not only fltk.lib
and fltk_images.lib, but the png/jpeg/zlib libs as well.
The Visual Studio "Build Log" will show you what FLTK uses to build
itself.
The reason these extra libs aren't included in fltk_images
is to allow you to optionally build with either FLTK's own
copies of the png/jpeg/zlib libs, or external ones provided by
your OS or by your own custom builds of these libs.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
