summaryrefslogtreecommitdiff
path: root/python/CMakeLists.txt
Commit message (Collapse)AuthorAgeFilesLines
* Avoid unnecessary variables for cmake target data, part 1Panu Matilainen2022-11-281-2/+1
| | | | | | The foo_SOURCES style isn't really in cmake ethos, and is wholly unnecessary here: target_sources() achieves the same exact thing in a slightly more straightforward way.
* Generate Python egg-info from cmake buildsPanu Matilainen2022-10-201-0/+5
| | | | | | To compensate for the loss of egg-info from the python distutils build, create one by ourselves. Not bothering with autotools for this, we need to start sunsetting that side of things and that starts right here.
* Add an experimental CMake build systemPanu Matilainen2022-06-281-0/+27
This is an incomplete release-early version, NOT intended or suitable for production use. It is intended to replace the autotools based buildsystem in rpm 4.20, until then it'll be developed alongside it. This causes some extra complications of course, but then we avoid a huge flag-day, and that matters more. To those wondering why cmake and not ${myfavorite}: the community around us effectively made that choice for us. We've made a lot of noise about bootstrap dependencies. When libsolv, dnf and all the related stack is powered by cmake build, it'd be just foolish to go with anything else. This way people working on the rpm stack have only one build system to learn, there's peer support available nearby and bootstrap dependencies are reduced, not increased. It also doesn't hurt that cmake is actually and actively maintained.