makex
Makex is a new and simplified build and automation tool.
It makex stuff happen. 🙂
What Makex is used for
- Compiling software/applications/firmware
- Building file systems/trees/images/file archives
- Building and deploying websites and web applications
- Running things repeatably
- Replacing most or all of the other build systems
Features 🍩
- Task based
- Familiar Syntax
- File Hashing and Checksums
- Dependency Graphs
- Caching
- Workspaces
- Copy on Write
Links 🔗
- Documentation
- Installation Instructions
- Troubleshooting
- Support: Google Groups or makex@googlegroups.com
Requirements
- Python >= 3.9
Quick Start
- Install:
pip install makex
- Define a Makex file and name it
Makexfile( ormakexfileif you prefer):
task(
name="hello-world",
steps=[
write("hello-world.txt", "Hello World!"),
# or, you can use the shell, but it is not recommended:
# shell(f"echo 'Hello World!' > {self.path}/hello-world.txt"),
# you may also execute things:
# execute("echo", "Hello World!"),
# or just print things:
# print("Hello World!"),
# more actions can go here; such as copying, mirroring or archiving...
],
outputs=[
"hello-world.txt",
],
)
- Run makex, specifying the task name:
makex run :hello-world
- A file at
$PWD/_output_/hello-world/hello-world.txtshall have the following contents:
Hello World!
Read the documentation to learn more.
Limitations
- Mac support is not tested.
- Windows is not tested or supported (yet).
Pronunciation 🗣
Makex is pronounced "makes", ˈmeɪks, ˈmeɪkˈɛks (or just "make" 🙂)
Related
Coming Soon
- Dynamic Task/Resource Allocation
- Task Tags/Labels
- Regular Expressions
- Intellij/VSCode integration
This is an early release of Makex. Things may change. Those changes will be noted in the HISTORY file (especially major ones).
With that, Makex is being used extensively by us. We've created many tasks and Makex files, and we don't want to create more work. 🫡
If you have any problems, feel free to contact us.
Metadata
Release files for makex 20250101
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| makex-20250101.tar.gz | 141.3 kB | Without provenance | Details for makex-20250101.tar.gz |
Release files / makex-20250101.tar.gz
| Download URL | makex-20250101.tar.gz |
|---|---|
| Size | 141.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
64e1f252f4742260c2d3e4a7b5868bf5e08877efc0f12e1b4ede1e5a1eee06dc
|
|
BLAKE2b-256 checksum How to use checksums |
0ffe1de81aaf9c2fc48df99bdfed5e8172678686388df65f726c69fde03ff758
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.21
|
Security for makex 20250101
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.