Skip to content

Switch to cmake for c extension building #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jstkdng
Copy link

@jstkdng jstkdng commented Dec 30, 2022

No description provided.

@gokberkgunes
Copy link
Owner

With this pull we're introducing cmake as a dependency, right? I am not sure the advantages it provides compared to current approach. Isn't a simpler approach with a Makefile possible and easier to manage?

With this, ueberzug-tabbed diverges from now not-existent upstream considerably, I am hesitant for such a change.

@jstkdng
Copy link
Author

jstkdng commented Dec 31, 2022

Cmake would be a make dependency in this case, not a runtime one.

The main advantage of using cmake is the creation of a compile_commands.json file, this file is read by clangd and aids in the extension development.

The current setup.py solution doesn't have that functionality afaik. Using makefiles wouldn't help either.

@eylles
Copy link

eylles commented Jan 7, 2023

How about using ninja instead?

@jstkdng
Copy link
Author

jstkdng commented Jan 8, 2023

cmake generates the build files, so it can be used with ninja or with make.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants