cmeel
Create Wheel from CMake projects
Decision gist · record as of 2026-08-14
Yes, if you maintain a CMake project and want to distribute it on PyPI without duplicating build logic. The low install friction, active maintenance, permissive license, and zero known vulnerabilities make it a solid choice. Not applicable if your project is pure Python or uses a different build system.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires CMake and a C++ compiler to build projects; Python 3.9 or later required.
- Low friction: single pure-Python dependency (tomli), distributed as a wheel.
- Active maintenance with recent commits and no known vulnerabilities.
License · maintenance · safety
BSD-2-Clause (permissive) — BSD-2-Clause is permissive; you can use, modify, and distribute cmeel-packaged projects with minimal restrictions, provided you retain the license notice.
last release 2026-05-11 (95 days) · last repo commit 2026-08-01 · 27 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 918,215 downloads/mo, #4,724 on PyPI
Alternatives
Verify before relying
# In pyproject.toml of a CMake project:
[build-system]
build-backend = "cmeel"
requires = ["cmeel[build]"]
# Then build with:
pip install --build-backend cmeel .- Whether cmeel handles all CMake project configurations or has known limitations with specific build patterns.
- Performance characteristics when packaging large or complex CMake projects.
- Compatibility with Windows builds (classifiers list MacOS and POSIX Linux only).
What it is and what it does
cmeel bridges CMake-based C++ projects and Python's packaging ecosystem by acting as a PEP 517 build backend. Instead of writing custom setup.py or setup.cfg, you declare your CMake project in pyproject.toml and cmeel handles the build, test, and wheel creation. It installs CMake artifacts into a namespaced directory within the Python site-packages, making dependencies discoverable to downstream CMake builds.
The package is designed for teams maintaining C++ libraries or tools that want to distribute them on PyPI without maintaining dual build systems. It follows modern Python packaging standards (PEP 517, 518, 621, 660) and supports editable installs for development workflows. Runtime dependencies are minimal—only tomli for TOML parsing—keeping installation lightweight.
Use it for
- Package a C++ library with Python bindings as a single wheel for distribution on PyPI.
- Build a CMake-based command-line tool and expose its executables through Python entry points.
- Create a dependency chain where one cmeel package depends on another, with CMake automatically finding transitive dependencies.
- Develop a hybrid project locally with editable installs while maintaining a single CMake build system.
- Distribute platform-specific binaries for MacOS and POSIX Linux as wheels without manual platform tagging.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you maintain a CMake project and want to distribute it on PyPI without duplicating build logic.
The low install friction, active maintenance, permissive license, and zero known vulnerabilities make it a solid choice. Not applicable if your project is pure Python or uses a different build system.
Install
cmeel on PyPI
Before you install
Low friction: single pure-Python dependency (tomli), distributed as a wheel. Active maintenance with recent commits and no known vulnerabilities. Requires Python 3.9 or later.
Requires CMake and a C++ compiler to build projects; Python 3.9 or later required.
License in practice
BSD-2-Clause is permissive; you can use, modify, and distribute cmeel-packaged projects with minimal restrictions, provided you retain the license notice.
Quickstart
# In pyproject.toml of a CMake project:
[build-system]
build-backend = "cmeel"
requires = ["cmeel[build]"]
# Then build with:
pip install --build-backend cmeel .Verify before relying
- Whether cmeel handles all CMake project configurations or has known limitations with specific build patterns.
- Performance characteristics when packaging large or complex CMake projects.
- Compatibility with Windows builds (classifiers list MacOS and POSIX Linux only).
Package facts
| License | BSD-2-Clause permissive |
| Python support | Supports the current Python release >=3.9 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 1 packagetomli |
| Maintenance | Actively maintained 95 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 918,215 / month, #4,724 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Operating System :: MacOSOperating System :: POSIX :: LinuxProgramming Language :: C++Programming Language :: Python :: 3Topic :: Software Development :: Build ToolsTopic :: System :: Archiving :: PackagingTopic :: System :: Software Distribution |
Evidence: cmeel-0.60.1-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “cmake wheel build backend”
- cmeelcmeel is a PEP 517 build backend that packages CMake projects as…
- scikit-build-coreA build backend that uses CMake to compile Python extension modules…
- cmakeDistributes CMake 4.4.2 as a Python package, making the cmake,…
Give your agent the search over MCP, or paste the wish link into any chat.
More Build Tools packages
Provides reusable utilities for Python packaging interoperability, including version handling, specifiers, markers, requirements, tags, and metadata parsing according to standards like PEP 440 and PEP 425.
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
pip is the standard installer for Python packages, enabling you to download and install packages from the Python Package Index and other indexes into your Python environment.
Hatchling is a standards-compliant Python build backend that handles packaging, metadata, and distribution of Python projects when configured in a project's pyproject.toml file.
Generates Python gRPC service stubs and message classes from Protocol Buffer definitions, enabling developers to build gRPC clients and servers.
pre-commit is a framework for installing and running git hooks written in any language before commits are made, automating code quality and validation checks across multi-language projects.
Install it if your team needs consistent, automated validation at commit time.
See also cmeel-boost · whey · cmeel-console-bridge · cmeel-zlib · tippecanoe · swig · wheel · cmeel-tinyxml · cmeel-tinyxml2 · build