From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v10 09/10] docs/manual: document cargo-based packages
Date: Mon, 05 Feb 2018 11:29:13 +0100 [thread overview]
Message-ID: <877errwwzq.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180204180749.29942-10-eric.le.bihan.dev@free.fr> (Eric Le Bihan's message of "Sun, 4 Feb 2018 19:07:48 +0100")
>>>>> "Eric" == Eric Le Bihan <eric.le.bihan.dev@free.fr> writes:
> Add instructions for adding a package which uses Cargo as build system.
> Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr>
> ---
> docs/manual/adding-packages-cargo.txt | 110 ++++++++++++++++++++++++++++++++++
> docs/manual/adding-packages.txt | 2 +
> 2 files changed, 112 insertions(+)
> create mode 100644 docs/manual/adding-packages-cargo.txt
> diff --git a/docs/manual/adding-packages-cargo.txt b/docs/manual/adding-packages-cargo.txt
> new file mode 100644
> index 0000000000..8de7c97cb9
> --- /dev/null
> +++ b/docs/manual/adding-packages-cargo.txt
> @@ -0,0 +1,110 @@
> +// -*- mode:doc; -*-
> +// vim: set syntax=asciidoc:
> +
> +=== Integration of Cargo-based packages
> +
> +Cargo is the package manager for the Rust programming language. It allows the
> +user to build programs or libraries written in Rust, but it also downloads and
> +manages their dependencies, to ensure repeatable builds. Cargo packages are
> +called "crates".
> +
> +[[cargo-package-tutorial]]
> +
> +==== Cargo-based package's +Config.in+ file
> +
> +The +Config.in+ file of Cargo-based package 'foo' should contain:
> +
> +---------------------------
> +01: config BR2_PACKAGE_FOO
> +02: bool "foo"
> +03: depends on BR2_PACKAGE_HOST_RUSTC_ARCH_SUPPORTS
> +04: select BR2_PACKAGE_HOST_CARGO
> +05: help
> +06: This is a comment that explains what foo is.
The indentation here is wrong. It should be <tab>help and
<tab><space><space>This is a comment..
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-02-05 10:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-04 18:07 [Buildroot] [PATCH v10 00/10] Add support for the Rust programming language Eric Le Bihan
2018-02-04 18:07 ` [Buildroot] [PATCH v10 01/10] rustc: new virtual package Eric Le Bihan
2018-02-08 22:52 ` Thomas Petazzoni
2018-02-09 8:49 ` Eric Le Bihan
2018-02-09 8:56 ` Thomas Petazzoni
2018-02-09 18:11 ` Eric Le Bihan
2018-02-04 18:07 ` [Buildroot] [PATCH v10 02/10] rust-bin: new package Eric Le Bihan
2018-02-04 18:07 ` [Buildroot] [PATCH v10 03/10] cargo-bin: " Eric Le Bihan
2018-02-04 18:07 ` [Buildroot] [PATCH v10 04/10] rust: " Eric Le Bihan
2018-02-04 18:07 ` [Buildroot] [PATCH v10 05/10] libssh2: add host variant Eric Le Bihan
2018-02-04 18:07 ` [Buildroot] [PATCH v10 06/10] libhttpparser: " Eric Le Bihan
2018-02-04 18:07 ` [Buildroot] [PATCH v10 07/10] libcurl: " Eric Le Bihan
2018-02-04 18:07 ` [Buildroot] [PATCH v10 08/10] cargo: new package Eric Le Bihan
2018-02-05 10:26 ` Peter Korsgaard
2018-02-05 13:11 ` Sam Voss
2018-02-05 13:58 ` Peter Korsgaard
2018-02-04 18:07 ` [Buildroot] [PATCH v10 09/10] docs/manual: document cargo-based packages Eric Le Bihan
2018-02-05 10:29 ` Peter Korsgaard [this message]
2018-02-04 18:07 ` [Buildroot] [PATCH v10 10/10] support/testing: add tests for Rust Eric Le Bihan
2018-02-05 14:03 ` [Buildroot] [PATCH v10 00/10] Add support for the Rust programming language Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877errwwzq.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox