cargo-make | Rust task runner and build tool | Continous Integration library

by sagiegurari Rust Version: 0.36.10 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | cargo-make Summary

cargo-make is a Rust library typically used in Devops, Continous Integration applications. cargo-make has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

The cargo-make task runner enables to define and configure sets of tasks and run them as a flow. A task is a command, script, rust code or other sub tasks to execute. Tasks can have dependencies which are also tasks that will be executed before the task itself. With a simple toml based configuration file, you can define a multi platform build script that can run build, test, generate documentation, run bench tests, run security validations and more, executed by running a single command.

Support

Quality

Security

License

Reuse

Support

cargo-make has a medium active ecosystem.

It has 2009 star(s) with 104 fork(s). There are 13 watchers for this library.

It had no major release in the last 12 months.

There are 19 open issues and 467 have been closed. On average issues are closed in 22 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of cargo-make is 0.36.10

Quality

cargo-make has 0 bugs and 0 code smells.

Security

cargo-make has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

cargo-make code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

cargo-make is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

cargo-make releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of cargo-make

Get all kandi verified functions for this library.

cargo-make Key Features

No Key Features are available at this moment for cargo-make.

cargo-make Examples and Code Snippets

No Code Snippets are available at this moment for cargo-make.

Community Discussions

Trending Discussions on cargo-make

Using an ld version script in a cdylib Rust crate

QUESTION

Using an ld version script in a cdylib Rust crate

Asked 2021-Aug-28 at 04:27

I am attempting to use a version script while building a cdylib Rust crate, however I am running into issues due to the anonymous version script created by the Rust compiler. I followed this forum post on how to add a version script, but they never mentioned this issue.

Execution

I'm using cargo-make to build my project. In my Makefile.toml I have this task:

...

ANSWER

Answered 2021-Aug-28 at 04:27

Solution provided by itamarst on the Rust forums.

Explanation

As shown in the question, ld does not support multiple version scripts. However, lld does so we can use that instead. (Can be installed with sudo apt install lld on ubuntu). To use lld instead of ld, pass -Clink-arg=-fuse-ld=lld to rustc.

However, this is not enough on its own. The version script Rust generates will take precedence and the version node will not be applied as specified in our version script. To get around this, functions can be given a temporary name and a new symbol can be linked to it via linker args (--defsym). In the version script the new symbol can be freely used and the original function name can be marked as local to prevent a duplicate symbols from being uploaded.

Rust Code

Source https://stackoverflow.com/questions/68789250

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install cargo-make

In order to install, just run the following command. This will install cargo-make in your ~/.cargo/bin. Make sure to add ~/.cargo/bin directory to your PATH variable. You will have two executables available: cargo-make and makers. See Cli Options section for full CLI instructions.
cargo-make - This is a cargo plugin invoked using cargo make ...
makers - A standalone executable which provides same features and cli arguments as cargo-make but is invoked directly and not as a cargo plugin.
Only one type of installation will be invoked per task. The following defines the installation types sorted by priority for which cargo-make uses to decide which installation flow to invoke:. In case multiple installation types are defined (for example both install_crate and install_script) only one installation type will be invoked based on the above priority list.
install_crate - Enables to install crates and rustup components.
install_script - Custom script which can be used to install or run anything that is needed by the task command.
automatic cargo plugin - In case the command is cargo, cargo-make will check which cargo plugin to automatically install (if needed).

Support

In case cargo-make detects that the current working directory is a workspace root (A directory with Cargo.toml which defines a workspace and its members), it will not invoke the requested tasks in that directory. Instead, it will generate a task definition in runtime which will go to each member directory and invoke the requested task on that member. For example if we have the following directory structure:. And we ran cargo make mytask, it will go to each workspace member directory and execute: cargo make mytask at that directory, where mytask is the original task that was requested on the workspace level. The order of the members is defined by the member attribute in the workspace Cargo.toml. This flow is called a workspace flow, as it identifies the workspace and handles the request for each workspace member, while the root directory which defines the workspace structure is ignored. We can use this capability to run same functionality on all workspace member crates, for example if we want to format all crates, we can run in the workspace directory: cargo make format. Member crate makefiles can also automatically extend the workspace directory makefile. See more info at the relevant section.

Find more information at: