Nicholas Schwarz wrote:
> 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.
Good reason for static builds.
Most vendors statically build with libs they're sure might not be
on the target user's machine (unless they include their own lib
directory).
To build FLTK into your app statically, the easy way is to just
link with the .a file (eg. "/path/to/fltk-1.x.x/lib/libfltk.a")
to get FLTK included as part of your binary, regardless of if
end users have any FLTK stuff installed or not on their target
machines.
Do this for any other external libs you're dependent on as well
("libfltk_images.a", "libpng.a", etc) that might not be on the
target machines.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
