DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2180 Version: 1.3-feature > And apparently a hell to maintain if we want FLTK to be still used correctly I'm not sure what you mean by "hell to maintain". configure script will fill it with needed data and files should be installed on ordinary place. Since FLTK already uses configure to replace library names and paths, this could be used in .pc files too. For example, there could be created pc directory, with fltk.pc.in, fltk-images.pc.in, fltk-opengl.pc.in and rest will be done by the scripts. I don't see how difficult is to maintain this file (e.g. fltk.pc.in): -------------------------------- pref...@prefix@ exec_prefix=${prefix} libdir=${exec_prefix}/lib includedir=${prefix}/include Name: fltk Description: FLTK Library Version: @FLTK_API_VERSION@ URL: http://www.fltk.org -------------------------------- or this (e.g. fltk-images.pc.in) -------------------------------- pref...@prefix@ exec_prefix=${prefix} libdir=${exec_prefix}/lib includedir=${prefix}/include Name: fltk-images Description: FLTK Library Version: @FLTK_API_VERSION@ URL: http://www.fltk.org Requires: @FLLIBNAME@ -------------------------------- > Are we sure that all users have the pkg-config package installed even in the Linux/Cygin/Mingw world Yes. In Linux world, pkg-config is always installed with anything that has *-dev in some distribution. Cairo, D-BUS, even latest X are comming with .pc files. I'm not saying how fltk-config should be dumped in favour of pkg-config, but how .pc files could be optional; if pkg-config does not exists, user could use fltk-config, or if does exists, user can choose what to do. Link: http://www.fltk.org/str.php?L2180 Version: 1.3-feature _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
