From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Romain Naour <romain.naour@smile.fr>
Cc: Matt Weber <Matthew.Weber@rockwellcollins.com>,
Patrick Havelange <patrick.havelange@essensium.com>,
James Hilliard <james.hilliard1@gmail.com>,
Buildroot List <buildroot@buildroot.org>,
"Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH v3 05/11] package/pkg-cargo.mk: introduce the cargo package infrastructure
Date: Sun, 9 Jan 2022 11:04:18 +0100 [thread overview]
Message-ID: <20220109110418.0c7fc038@windsurf> (raw)
In-Reply-To: <310621ef-6a6e-f7e6-18d1-20ace14a81b7@smile.fr>
On Fri, 7 Jan 2022 22:07:26 +0100
Romain Naour <romain.naour@smile.fr> wrote:
> > +endif # ifeq ($(4),target)
> > +endif # ifndef $(2)_BUILD_CMDS
> > +
>
> is _INSTALL_STAGING_CMDS is missing here ?
>
> Rust package may wand to install *.rlib files [1] (similar to .a)
But will Cargo pick up .rlib files from STAGING_DIR ? I don't see how
Cargo/Rust knows about STAGING_DIR. Aren't those .rlib files anyway
installed in CARGO_HOME, and Cargo picks them up from here, or
something like that?
Installing to STAGING_DIR is one thing, but what's important is to
figure out if Cargo is really going to use what we install in
STAGING_DIR.
Do we have a specific example where one package installs a .rlib and
another package uses it?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-09 10:04 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 20:59 [Buildroot] [PATCH v3 00/11] Support for Cargo and Go vendoring Thomas Petazzoni
2022-01-06 20:59 ` [Buildroot] [PATCH v3 01/11] support/download/dl-wrapper: add concept of download post-processing Thomas Petazzoni
2022-01-07 10:28 ` Yann E. MORIN
2022-01-06 20:59 ` [Buildroot] [PATCH v3 02/11] package/pkg-download.mk: add <pkg>_DOWNLOAD_POST_PROCESS variable Thomas Petazzoni
2022-01-07 10:35 ` Yann E. MORIN
2022-01-06 20:59 ` [Buildroot] [PATCH v3 03/11] support/download/post-process-helpers: add helper function for post process scripts Thomas Petazzoni
2022-01-07 10:36 ` Yann E. MORIN
2022-01-06 20:59 ` [Buildroot] [PATCH v3 04/11] package/pkg-golang.mk: implement Go vendoring support Thomas Petazzoni
2022-01-09 11:49 ` Romain Naour
2022-01-06 20:59 ` [Buildroot] [PATCH v3 05/11] package/pkg-cargo.mk: introduce the cargo package infrastructure Thomas Petazzoni
2022-01-07 1:12 ` James Hilliard
2022-01-07 9:52 ` Thomas Petazzoni
2022-01-07 22:30 ` James Hilliard
2022-01-07 22:59 ` Thomas Petazzoni
2022-01-08 3:21 ` James Hilliard
2022-01-08 13:52 ` Juergen Stuber
2022-01-07 10:05 ` Romain Naour
2022-01-07 10:26 ` Romain Naour
2022-01-07 10:44 ` Yann E. MORIN
2022-01-07 11:03 ` Romain Naour
2022-01-07 21:07 ` Romain Naour
2022-01-07 21:53 ` Thomas Petazzoni
2022-01-09 10:04 ` Thomas Petazzoni [this message]
2022-01-06 20:59 ` [Buildroot] [PATCH v3 06/11] docs/manual/cargo: document the cargo-package infrastructure Thomas Petazzoni
2022-01-06 20:59 ` [Buildroot] [PATCH v3 07/11] package/ripgrep: convert to cargo infrastructure Thomas Petazzoni
2022-01-06 20:59 ` [Buildroot] [PATCH v3 08/11] package/sentry-cli: re-add package Thomas Petazzoni
2022-01-06 22:04 ` Christian Stewart via buildroot
2022-01-06 22:29 ` Thomas Petazzoni
2022-01-06 22:38 ` Christian Stewart via buildroot
2022-01-06 22:59 ` Thomas Petazzoni
2022-01-06 20:59 ` [Buildroot] [PATCH v3 09/11] package/tinifier: new package Thomas Petazzoni
2022-01-06 22:30 ` Christian Stewart via buildroot
2022-01-06 20:59 ` [Buildroot] [PATCH v3 10/11] package/embiggen-disk: " Thomas Petazzoni
2022-01-06 22:11 ` Christian Stewart via buildroot
2022-01-06 20:59 ` [Buildroot] [PATCH v3 11/11] package/gocryptfs: " Thomas Petazzoni
2022-01-06 22:26 ` [Buildroot] [PATCH v3 00/11] Support for Cargo and Go vendoring Christian Stewart via buildroot
2022-01-06 22:29 ` Thomas Petazzoni
2022-01-08 22:39 ` Thomas Petazzoni
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=20220109110418.0c7fc038@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=Matthew.Weber@rockwellcollins.com \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=patrick.havelange@essensium.com \
--cc=romain.naour@smile.fr \
--cc=yann.morin.1998@free.fr \
/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;
as well as URLs for NNTP newsgroup(s).