cargo-nuget

Pack native Rust libraries as .NET Nuget packages.

Build Status

Platform | Channel | Status ------------------------------ | ------- | ------------- Linux (Debian x64) / OSX (x64) | Stable | Windows (MSVC x64) | Stable |

Progress

• [x] Package builds for local target
• [x] Release as cargo tool
• [ ] Package builds for cross-platform targets

Installation

shell $ cargo install cargo-nuget

Usage

Running cargo-nuget pack will attempt to pack a crate in the current directory as a nupkg:

shell $ cargo-nuget $ tree . ├── Cargo.lock ├── Cargo.toml ├── your_crate.0.1.0-dev.1489461345.nupkg ├── src │   └── lib.rs └── target

For a complete set of commands:

shell cargo-nuget --help

The process

Here's the basic workflow we want to support:

1. Write a Cargo-based Rust library
2. Populate your Cargo.toml crate metadata
3. Run cargo-nuget to run a cargo build and get a nupkg containing a dev build for your current platform
4. Reference your crate name as a dependency in your .NET project file
5. DllImport your crate name

Some additional options may be supplied:

shell $ cargo-nuget pack --test $ cargo-nuget pack --cargo-dir=some-crate/path/ $ cargo-nuget pack --nupkg-dir=some-folder/nuget/ $ cargo-nuget pack --release

About

This is a tool for packaging Rust libraries as a Nuget package for consuming in .NET. The basic idea is to use the native Rust target for a development build and write the package to some local feed

In general the tool should:

• Support typical Rust and .NET build pipelines
• Work

Why use packages?

The new .NET Core tooling for packages is a big improvement over the old rubbish we had to deal with. I think it's possible to support development workflows using packages in .NET in a way we couldn't do before. Being able to referernce native assemblies using packages has the benefit of working the exact same way in dev as it would in the wild.