On 11 Jul 2009, at 16:45, pawel wrote: > Looking over things I notice that maybe I should have ran ./ > configure before the make... > > Any easy ways to make this work? > (I was thinking of deleting everything installed by fltk and then > starting over from ./confgure, but aren't sure that I know where > all the installed files are.)
There is a "make uninstall" option too, in the build, but if you are intending to re-install anyway then I wouldn't bother. A new "make install" will overwrite the existing installation. However, I'd caution *against* installing fltk-1.3 at this stage. The libraries and headers that it installs have the same names as the ones that fltk-1.1 installs, but have a slightly different API and an incompatible ABI. Probably this does not matter, but I think there are a few things in F10 and F11 that depend on the fltk .so files (maybe CUPS and etc, and a few others) and they *might break* if you install the fltk-1.3 libs and those other tools are expecting to find the fltk-1.1 libs there... So, what I'd recommend is, until we sort out the formal release of 1.3, that you only install it into a local folder for your developer use (see the --prefix option to configure), or even simpler, do what I do and use fltk-1.3 directly from its build tree. Fltk is designed to work correctly from its build tree (fltk-config has code specifically to detect this use-case, for example), and so this is the simplest and easiest option, no installation is required. You just have to tell your tools (I think you said you were using code::blocks) what include and library paths to add, and then it Just Works. -- Ian _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
