---snip-- > When I ran cmake it said it found cairo, python, libxml2, etc... yet at the > end it's looking for variables that are only set if the dev libraries are > installed. With Craig's advice and with my experience and a little searching > on the web I was able to find the solutions. But would it not make more sense > to have the cmake script actually look for the dev libraries and output an > error if it didn't find them? Then there would of been no question that that > was the problem. This isn't a rant, just a suggestion to improve and make it > easier for people like me that are generally spoiled by Mac and Windows > installer applications ;-)
That would make sense if all Linux distributions, BSD releases, and Mac OS X all separated development headers from executables. As I mentioned in response to another thread on this list, Slackware and Slackware-based Linux distributions include development headers in packages automatically. Maybe the RPM-based and Debian-based Linux distributions can take a hint from Slackware and include the development headers automatically instead of putting executables and development headers into separate packages. FWIW, CMake is working as designed, in that it didn't find the headers in the INCLUDE path until the development packages were installed. FWIW (about $0.02), John
