On 05.01.2009, at 21:15, Brian wrote: > Hi Mathias, > > I downloaded 1.3.x-r6618 this evening and looked at the output of > fltk-config. > > br...@cruncher ~ > $ fltk-config --use-images --ldstaticflags > -mwindows -mno-cygwin /usr/local/lib/libfltk_images.a > /usr/local/lib/libfltk_png.a /usr/local/lib/libfltk_z.a > /usr/local/lib/libfltk_jpeg.a > /usr/local/lib/libfltk.a -lole32 -luuid -lcomctl32 > > --ldstaticflags option does not have -lwsock32 as part of output, > Was this intentional or is this another bug?
That is intentional. FLTK has optional network support, and since wsock32 exists on all Windows machines anyway, we thought there is no harm in linking with it. But users complained that customers felt spied on, because they found FLTK programs linking to a communication library, even for programs that do not use sockets. FLTK 1.3 no only links to wsock32 if required. It does that transparently, so no changes needed. Matthias ---- http://robowerk.com/ _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
