Am 28.11.07, 20:54 -0000 schrieb imm: > On 28 Nov 2007, at 20:38, Kai-Uwe Behrmann wrote: > > > o modifying the include path would be out of scope for most projects > Remember also that fltk-config "knows" where the version of fltk it > refers to is actually installed, so as long as you access fltk via > the fltk-config script, the changes to the paths are transparent to > you. Just use fltk-config in your Makefiles to get the "right" > version for any given task.
Having worked long times with autotools the path order seems under less control. I wonder always what the gcc ilne will be in the end. So if one version appears under /usr/include/FL/... it will probably be choosen, regardless if this was a packagers intention in the first place. > > o adding a new prefix to the UTF-8 version requires some amount of > > work in > > the projects, which like to use the nice feature. Anyway this > > would be > > possible. > > My hacked up UTF-8 fltk-1.1.8 code has renamed the libs and fltk- > config script to include the utf modified (e.g. fltk-config becomes > fltk-utf8-config, etc...) That would generally be good to deploy. > This keeps the installed libraries from overwriting the "regular" > libs. The only issue then is to install the utf-8 variant headers in > some "non-standard" place, and then access them via fltk-utf8-config. > This has been working fine for me, thus far! Distribution means almost a /usr/lib /usr/include combo box. So two FLTK's installing into one include path wont work. kind regards Kai-Uwe Behrmann -- developing for colour management www.behrmann.name + www.oyranos.org _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
