Skip to content

Packaging does not use the same entrypoint that make package does #4519

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
gamesh411 opened this issue Apr 4, 2025 · 0 comments
Open

Packaging does not use the same entrypoint that make package does #4519

gamesh411 opened this issue Apr 4, 2025 · 0 comments

Comments

@gamesh411
Copy link
Collaborator

Describe the bug
The intended entry point based on the Makefile build system is bin/CodeChecker.py, but setup.py states that the CodeChecker command should be provided by the codechecker_common.cli:main.

CodeChecker version
current dev branch

To Reproduce
Steps to reproduce the behaviour:
python3 setup.py sdist
then install inside a virtualenv
python3 setup.py install
see the contents of the installed codechecker script
cat $(which CodeChecker)
verify that the contents are not the same as bin/CodeChecker.py

Expected behaviour
The content of the file installed during the setuptools install should be the same as bin/CodeChecker.py

Desktop (please complete the following information)

  • OS: Linux WSL
  • Version: Ubuntu 24.04

Additional context
The project has its roots in Makefiles, and setuptools packaging is added later on, and got out of sync over time with the makefile-based build system.

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

No branches or pull requests

1 participant