RFC: replacing MacroLogFeature.cmake with FeatureSummary.cmake
David Jarvie
djarvie at kde.org
Tue Jul 19 09:30:37 BST 2011
On Mon, July 18, 2011 8:48 pm, Alexander Neundorf wrote:
> On Monday 18 July 2011, David Jarvie wrote:
>> On Wednesday 13 July 2011 20:16:58 Alexander Neundorf wrote:
> ...
>> > What do you think of this ?
>> > More wishes ?
>> > Should it do it in a different way ?
>>
>> Something else which would be useful would be to output the actual file
>> names (library files, header files etc.) which were checked for but not
>> found when looking for the missing packages. Trying to determine which
>> distro package to install to satisfy the dependency isn't always
>> straightforward, since distro package names aren't always the same as
>> the
>> cmake package names. In these cases, I quite often have to find the
>> cmake
>> module used to locate the package, and then look through the cmake
>> module
>> to work out the files it's looking for, in order to then be able to do a
>> package search for my distro to find which package to install.
>
> I agree that this would be useful, but this is just too much to present in
> the
> summary.
> It would have to contain for which files it checked, and in which
> directories.
> This is a lot.
> This should be done in the success/failure message during the cmake run,
> not
> in the summary at the end IMO.
Yes, outputting it at the point it is found to be missing would be fine.
The main thing is to provide an alternative to trawling through the cmake
modules for the information.
--
David Jarvie.
KDE developer.
KAlarm author - http://www.astrojar.org.uk/kalarm
More information about the kde-core-devel
mailing list