In configure.in, why is it LIBFLTK_LIBS=`fltk2-config --use-images --ldflags` if we use the system png/jpeg/etc. libraries and not the fltk ones? I just tried removing the --use-images argument, and everything still works for me.
On Wed, Jan 05, 2011 at 09:46:29PM +0000, corvid wrote:
In configure.in, why is it LIBFLTK_LIBS=`fltk2-config --use-images --ldflags` if we use the system png/jpeg/etc. libraries and not the fltk ones? I just tried removing the --use-images argument, and everything still works for me.
Probably because that way it worked with an older version. Does the generated binary size change? Or is there a change with ldd? If the button icons load OK, and the file chooser works, there should be no problems. Those widgets *may* need the internal image handling (but I don't know for sure). -- Cheers Jorge.-
Jorge wrote:
On Wed, Jan 05, 2011 at 09:46:29PM +0000, corvid wrote:
In configure.in, why is it LIBFLTK_LIBS=`fltk2-config --use-images --ldflags` if we use the system png/jpeg/etc. libraries and not the fltk ones? I just tried removing the --use-images argument, and everything still works for me.
Probably because that way it worked with an older version. Does the generated binary size change? Or is there a change with ldd?
No difference. (I was hoping it might make it a bit smaller.)
If the button icons load OK, and the file chooser works, there should be no problems. Those widgets *may* need the internal image handling (but I don't know for sure).
participants (2)
-
corvid＠lavabit.com -
jcid＠dillo.org