|
From: Daniel J S. <dan...@ie...> - 2006-07-30 19:57:02
|
James R. Van Zandt wrote: > Daniel J Sebald <dan...@ie...> wrote: > > >> 4) Could the following warnings be removed? >> >> checking for CAIRO... Package cairo was not found in the >> pkg-config search path. >> Perhaps you should add the directory containing `cairo.pc' to the >> PKG_CONFIG_PATH environment variable >> No package 'cairo' found >> configure: WARNING: Cairo can't be found. The wxWidgets terminal >> will not be compiled. > > ... > >> Isn't it the job of the auto-build tools to sort out what should >> and shouldn't be built? This isn't a valid situation for warnings >> from my perspective. > > > I for one appreciate these warnings. If I am interested in the > missing functionality, they tell me what other software I should look > for. Yes, but the key word there being "if". I mean, why can't this: checking for CAIRO... Package cairo was not found in the pkg-config search path.Perhaps you should add the directory containing `cairo.pc' to the PKG_CONFIG_PATH environment variable No package 'cairo' found configure: WARNING: Cairo can't be found. The wxWidgets terminal will not be compiled. be summarized as: checking for CAIRO... no As with the several other cases where "no" comes up in the ./configure operation, logic tells me that configure could not find the package and therefore it will not be included in the compilation. Why does there need to be a WARNING to tell me that? The only real bit of info in the above message is "Perhaps you should add the directory containing `cairo.pc' to the PKG_CONFIG_PATH environment variable" and even that is wordy. And, once that is stated it becomes redundant information when it is displayed several more times later. And this one: checking for PANGO... Requested 'pango >= 1.10' but version of Pango is 1.6.0 could be: checking for PANGO... found 1.6.0, require >= 1.10 Most people understand the ramification of that. We don't then need to know: configure: WARNING: Pango can't be found. The wxWidgets terminal will not be compiled. which in fact seems like a conflicting report to me. Pango WAS found, it just isn't a recent enough version. Perhaps there should be a verbose mode for configure. Dan |