Mention CMake Log Parser in README
This commit is contained in:
parent
70e6800a50
commit
270bb7be68
1 changed files with 2 additions and 0 deletions
|
@ -2,6 +2,8 @@
|
||||||
|
|
||||||
This proof-of-concept detects which packages are used in a CMake project without having to modify the project at all (in most cases.) This could be used to generate dependency data for KDE libraries and also 3rd party dependencies.
|
This proof-of-concept detects which packages are used in a CMake project without having to modify the project at all (in most cases.) This could be used to generate dependency data for KDE libraries and also 3rd party dependencies.
|
||||||
|
|
||||||
|
See my [CMake Log Parser](https://invent.kde.org/redstrate/cmake-package-installer) for another idea of how to parse dependency data from CMake. I think this is a better solution though.
|
||||||
|
|
||||||
## How it works
|
## How it works
|
||||||
|
|
||||||
As you may have seen before, lots of CMake projects (including KDE software) uses a module called `FeatureSummary`. It prints out what packages are used in a project and also a whole host of other configurable information.
|
As you may have seen before, lots of CMake projects (including KDE software) uses a module called `FeatureSummary`. It prints out what packages are used in a project and also a whole host of other configurable information.
|
||||||
|
|
Reference in a new issue