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||
I suggest one of two things:
a) Use 'fltk-config' to build your app so you get the proper
linker flags.
(Since your app needs images, be sure to include the
'--use-images' flag.
For more info, see 'fltk-config --help')
If your app is a simple .cxx/.h file, this could be as easy
as:
fltk-config --use-images --compile yourapp.cxx
If you have a more complicated app that has lots of custom
flags
and modules, then you can use fltk-config this way:
http://www.fltk.org/doc-1.3/basics.html#basics_makefile
-- OR --
b) Look at the flags FLTK uses to build its own demos
If you don't want to know what all the flags are, and just want it to
work,
then take the (a) approach.
Or, if you're an 'under the hood' kind of guy who wants to know all the
flags and libs being used, take the (b) approach. To do that:
1) Edit the makeinclude file in the fltk main directory,
and comment out the .SILENT line so that 'make' will
print the compiler/linker commands.
2) Touch the fltk/test/images.cxx file, and rebuild the test
program. eg:
cd test ; touch images.cxx; make images
3) 'make' will print out the full compile/link lines so that
you can see the names of all the flags and correct linker
order
which you can then copy/paste into your build files.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
