On 30 Jan 2009, at 10:31, Jeremy Henty wrote: >> 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. > > It was dropped??? I always assumed that it was an omission in > fltk-config that was fixed in fltk2-config. I never imagined it might > have been taken out.
Oh, OK. Yes, it used to be in fltk-1, but was later removed. The fltk-2 fork had already happened by that point, and the mechanism remained in there. >> Maybe we should lobby for the reintroduction of the --prefix option. > > I would! Though even that wouldn't handle a system configured with > --prefix=<something> --includedir=<something_else>. That seems like a fair point, so we'd really need a couple of extra options to fltk-config to get the things you need. If you were to file an STR against 1.3... I would try and fix it myself, but my configure-fu is weak... Patches welcome, of course! >> 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. >> > Unfortunately no. My system uses --prefix=/usr and -I/usr/include > does not appear the --cxxflags output. OK - that is inconvenient... -- Ian _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
