|
From: Daniel J S. <dan...@ie...> - 2006-07-30 20:14:34
|
Timoth=E9e Lecomte wrote: > James R. Van Zandt wrote: >=20 >> Daniel J Sebald <dan...@ie...> wrote: >> >> =20 >> >>> 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. >>> =20 >> >> ... >> =20 >> >>> 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. >>> =20 >> >> >> I for one appreciate these warnings. If I am interested in the >> missing functionality, they tell me what other software I should look >> for. >> - Jim Van Zandt >> =20 >=20 > Daniel, would it satisfy you if I replace the "WARNING" by "NOTE" ? Not really. In my opinion, be more terse. Here there are three warnings= : configure: WARNING: Pango can't be found. The wxWidgets terminal will not= be compiled. configure: WARNING: Cairo can't be found. The wxWidgets terminal will not= be compiled. configure: WARNING: Cairo rendering support for Pango can't be found. The= wxWidgets terminal will not be compiled. stating wxWidgets terminal will not be included. Too wordy and redundant. Ethan, what kind of warning messages are given when JPEG, PNG, etc. aren'= t available? Can this be summarized at the bottom of ./configure along w= ith all the other items listed? E.g., Do not build wxWidgets (requires Cairo, Pango or CairoPango) Dan |