On 28 Nov 2007, at 20:38, Kai-Uwe Behrmann wrote: > o modifying the include path would be out of scope for most projects
This is my preferred option, however. I have at least 4 different hacks of fltk-1.1.8 on the go, all in different locations, and it works pretty well. It is trivial to set the prefix options when running configure to install the different versions into different places. 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. > 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...) 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! > Still I am not shure if this makes sense to a plug-in / host > relation with one part being old style linked to say FLTK-1.1.7 and > one to > the UTF-8 enabled version. Would they fail badly or see I problems > where > no is to be expected? This probably will not work - the UTF8 libs have a different binary API to the regular fltk libs (some key items in the widgets have different sizes, for example) so they can not be used interchangeably. You must compile your code against the appropriate libs for each case. -- Ian _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
