A code generator to reduce repetitive tasks and build high-quality Rust libraries.
Part of the Mini Functions family of libraries.
• Website • Documentation • Report Bug • Request Feature • Contributing Guidelines
LibMake
is a tool designed to quickly help creating high-quality Rust
libraries by generating a set of pre-filled and pre-defined templated
files. This opinionated boilerplate scaffolding tool aims to greatly
reduces development time and minimizes repetitive tasks, allowing you to
focus on your business logic while enforcing standards, best practices,
consistency, and providing style guides for your library.
With LibMake
, you can easily generate a new Rust library code base
structure with all the necessary files, layouts, build configurations,
code, tests, benchmarks, documentation, and much more in a matter of
seconds.
The library is designed to be used as a command-line tool. It is available on Crates.io and Lib.rs.
LibMake
offers the following features and benefits:
It takes just a few seconds to get up and running with LibMake
.
To install LibMake
, you need to have the Rust toolchain installed on
your machine. You can install the Rust toolchain by following the
instructions on the Rust website.
Once you have the Rust toolchain installed, you can install LibMake
using the following command:
shell
cargo install libmake
You can then run the help command to see the available options:
shell
libmake --help
The minimum supported Rust toolchain version is currently Rust 1.69.0
or later (stable).
LibMake
is supported and has been tested on the following platforms:
| | Operating System | Target | Description | | --- | --- | --- | --- | | ✅ | Linux | aarch64-unknown-linux-gnu | 64-bit Linux systems on ARM architecture | | ✅ | Linux | i686-unknown-linux-gnu | 32-bit Linux (kernel 3.2+, glibc 2.17+) | | ✅ | Linux | x8664-unknown-linux-gnu | 64-bit Linux (kernel 2.6.32+, glibc 2.11+) | | ✅ | macOS | x8664-apple-darwin | 64-bit macOS (10.7 Lion or later) | | ✅ | Windows | i686-pc-windows-gnu | 32-bit Windows (7 or later) | | ✅ | Windows | i686-pc-windows-msvc | 32-bit Windows (7 or later) | | ✅ | Windows | x8664-pc-windows-gnu | 64-bit Windows (7 or later) | | ✅ | Windows | x8664-pc-windows-msvc | 64-bit Windows (7 or later) |
| | Operating System | Target | Description | | --- | --- | --- | --- | | ✅ | Linux | aarch64-unknown-linux-musl | 64-bit Linux systems on ARM architecture | | ✅ | Linux | arm-unknown-linux-gnueabi | ARMv6 Linux (kernel 3.2, glibc 2.17) | | ✅ | Linux | arm-unknown-linux-gnueabihf | ARMv7 Linux, hardfloat (kernel 3.2, glibc 2.17) | | ✅ | Linux | armv7-unknown-linux-gnueabihf | ARMv7 Linux, hardfloat (kernel 3.2, glibc 2.17) | | ✅ | Linux | mips-unknown-linux-gnu | MIPS Linux (kernel 2.6.32+, glibc 2.11+) | | ✅ | Linux | mips64-unknown-linux-gnuabi64 | MIPS64 Linux (kernel 2.6.32+, glibc 2.11+) | | ✅ | Linux | mips64el-unknown-linux-gnuabi64 | MIPS64 Linux (kernel 2.6.32+, glibc 2.11+) | | ✅ | Linux | mipsel-unknown-linux-gnu | MIPS Linux (kernel 2.6.32+, glibc 2.11+) | | ✅ | macOS | aarch64-apple-darwin | 64-bit macOS (10.7 Lion or later) | | ✅ | Windows | aarch64-pc-windows-msvc | 64-bit Windows (7 or later) |
The GitHub Actions shows the platforms in which the LibMake
library tests are run.
Should you encounter any issues with the library on any of the above platforms, please report a bug. We will do our best to resolve the issue as soon as possible. If you would like to contribute to help us to support additional platforms, please submit a pull request.
ℹ️ Info: Do check out our website for more information. You can find our documentation on docs.rs, lib.rs and crates.io.
LibMake
provides a command-line interface to generate a new library
project. There are a few options available to help you get started.
The following command generates a library template from a CSV file.
Have a look at the tests/data/mylibrary.csv
file for an example and
feel free to use it for your own library as a template.
shell
libmake --csv tests/data/mylibrary.csv
or locally if you have cloned the repository:
shell
cargo run -- --csv tests/data/mylibrary.csv
The following command generates a library template from a JSON file.
Have a look at the tests/data/mylibrary.json
file for an example and
feel free to use it for your own library as a template.
shell
libmake --json tests/data/mylibrary.json
or locally if you have cloned the repository:
shell
cargo run -- --json tests/data/mylibrary.json
The following command generates a library template from a TOML file.
Have a look at the tests/data/mylibrary.toml
file for an example and
feel free to use it for your own library as a template.
shell
libmake --toml tests/data/mylibrary.toml
or locally if you have cloned the repository:
shell
cargo run -- --toml tests/data/mylibrary.toml
The following command generates a library template from a YAML file.
Have a look at the tests/data/mylibrary.yaml
file for an example and
feel free to use it for your own library as a template.
shell
libmake --yml tests/data/mylibrary.yaml
or locally if you have cloned the repository:
shell
cargo run -- --yml tests/data/mylibrary.yaml
The following command generates a library template using the command-line interface.
shell
libmake \
--author "John Smith" \
--build "build.rs" \
--categories "['category 1', 'category 2', 'category 3']" \
--description "A Rust library for doing cool things" \
--documentation "https://docs.rs/my_library" \
--edition "2021" \
--email "john.smith@example.com" \
--homepage "https://my_library.rs" \
--keywords "['rust', 'library', 'cool']" \
--license "MIT" \
--name "my_library" \
--output "my_library" \
--readme "README.md" \
--repository "https://github.com/example/my_library" \
--rustversion "1.69.0" \
--version "0.1.0" \
--website "https://example.com/john-smith"
or locally if you have cloned the repository:
shell
cargo run -- --author "John Smith" \
--build "build.rs" \
--categories "['category 1', 'category 2', 'category 3']" \
--description "A Rust library for doing cool things" \
--documentation "https://docs.rs/my_library" \
--edition "2021" \
--email "john.smith@example.com" \
--homepage "https://my_library.rs" \
--keywords "['rust', 'library', 'cool']" \
--license "MIT" \
--name "my_library" \
--output "my_library" \
--readme "README.md" \
--repository "https://github.com/example/my_library" \
--rustversion "1.69.0" \
--version "0.1.0" \
--website "https://example.com/john-smith"
To get started with LibMake
, you can use the examples provided in the
examples
directory of the project.
To run the examples, clone the repository and run the following command in your terminal from the project root directory.
| Example | Description | Command |
|---------|-------------|---------|
| generate_from_args
| Generates a library template using the command-line interface. | cargo run --example generate_from_args
|
| generate_from_config
| Generates a library template from a configuration file. | cargo run --example generate_from_config
|
| generate_from_csv
| Generates a library template from a CSV file. | cargo run --example generate_from_csv
|
| generate_from_json
| Generates a library template from a JSON file. | cargo run --example generate_from_json
|
| generate_from_toml
| Generates a library template from a TOML file. | cargo run --example generate_from_toml
|
| generate_from_yaml
| Generates a library template from a YAML file. | cargo run --example generate_from_yaml
|
For transparency into our release cycle and in striving to maintain
backward compatibility, libmake
follows semantic versioning.
The project is licensed under the terms of both the MIT license and the Apache License (Version 2.0).
We welcome all people who want to contribute. Please see the contributing instructions for more information.
Contributions in any form (issues, pull requests, etc.) to this project must adhere to the Rust's Code of Conduct.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
A big thank you to all the awesome contributors of libmake for their help and support. A special thank you goes to the Rust Reddit community for providing a lot of useful suggestions on how to improve this project.