> I am working on a new Ruby/FLTK binding (for FLTK-1.1.x) and my build > system parses the FLTK header files to extract things like the > contents of enumerations etc. So, I'd like to know the most portable > way of finding where the headers are in the file system. > > At the moment I'm preprocessing a wrapper file that #include-s the > header I'm interested in. However, parsing the preprocessed output > has turned out to be a pain, so I'd like to just open the header > directly and read it. That means finding it. Unfortunately it > doesn't seem to be possible to query fltk-config to find out where the > headers were installed. (Unless I've missed a trick.) > > So, how do I find things like Enumerations.H in the most portable way > possible?
Well, fltk-config used to (and fltk2-config still does) have a --prefix option that returned exactly that info., but it was dropped at some point. This annoyed me at the time, as I had a bunch of makefiles that depended on that option to do dodgy things with selecting between different fltk variants... Maybe we should lobby for the reintroduction of the --prefix option. That said, you can (as I ended up doing back then) parse the wanted path out of the --cxxflags option by looking for the -I... Option. Any good? SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
