> > > > What is it that you don't like about Fl::lock() and Fl::unlock()? > > > > I think that Fl::lock() and Fl::unlock() are very useful. The reason I don't > want to use them is because I'll mostly be deploying this software on SuSE > systems. The default install of FLTK on SuSE doesn't include thread support > for some reason. Although it's not that big of a deal for me to re-build FLTK > or to install a different rpm on my system, my users aren't computer > programmers. They don't know how to compile things or what threads are. Also, > they don't have administrator access to their computers. So, the less changes > that have to be made to their systems the easier my life is in the long run. >
Yes, indeed. So, don't use the SuSe .so file - just static link your app to fltk, including thread support, and be done with it. For fltk, the overhead of the gui lib is so small that dynamically linking it is seldom a win. And static linking neatly dodges exactly the sort of .so issues you describe, with no end-user intervention required. And means you always get the version of fltk you expect, into the bargain! _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
