[CMake] cmake corresponding config.log gile?

[Andreas Pakulat]

On 23.01.08 19:12:02, Zé wrote:
> Em Quarta, 23 de Janeiro de 2008 07:03:37, Eric Noulard escreveu:
> > 2008/1/23, Zé <mmodem00 at gmail.com>:
> > > When using automake i could see in config.log if when building an app
> > > there were missing some buildrequires but now with cmake im totally lost.
> >
> > Usually CMake print (command line cmake)
> > or pop-up (GUI cmake) messages regarding problem
> > during configuration, with an appropriate explanation:
> > missing header or lib, etc...
> Im not refering about the buildrequires that are indeed needed, but those 
> buildrequires that are optional, and that in sone cases having some 
> buildrequires can cause to have more files, and in a config.log that is easy 
> to see, in cmake its totally the opposite.

Hmm, I disagree. I always considered config.log to be quite unreadable.
Also it relies on the autoconf macro's to be written in a way that they
output the information needed. The same thing is true for CMake
buildsystems, if the author didn't care to create proper messages when
it doesn't find an optional dependecy then you should blame that author,
not cmake. There are ways to inform the user about optional dependecies.

Andreas

-- 
You have an ability to sense and know higher truth.