From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 8C28AC433EF for ; Sun, 9 Jan 2022 10:04:29 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id 1904E60B28; Sun, 9 Jan 2022 10:04:29 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HCyB7uwF7TPT; Sun, 9 Jan 2022 10:04:27 +0000 (UTC) Received: from ash.osuosl.org (ash.osuosl.org [140.211.166.34]) by smtp3.osuosl.org (Postfix) with ESMTP id 4A97A60767; Sun, 9 Jan 2022 10:04:26 +0000 (UTC) Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by ash.osuosl.org (Postfix) with ESMTP id 607781BF4DD for ; Sun, 9 Jan 2022 10:04:25 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id 4F3164034C for ; Sun, 9 Jan 2022 10:04:25 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l4Te19Jrcp7i for ; Sun, 9 Jan 2022 10:04:23 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0 Received: from relay6-d.mail.gandi.net (relay6-d.mail.gandi.net [IPv6:2001:4b98:dc4:8::226]) by smtp4.osuosl.org (Postfix) with ESMTPS id 0F1DC40342 for ; Sun, 9 Jan 2022 10:04:22 +0000 (UTC) Received: (Authenticated sender: thomas.petazzoni@bootlin.com) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id 56E5BC0004; Sun, 9 Jan 2022 10:04:19 +0000 (UTC) Date: Sun, 9 Jan 2022 11:04:18 +0100 From: Thomas Petazzoni To: Romain Naour Message-ID: <20220109110418.0c7fc038@windsurf> In-Reply-To: <310621ef-6a6e-f7e6-18d1-20ace14a81b7@smile.fr> References: <20220106210000.397694-1-thomas.petazzoni@bootlin.com> <20220106210000.397694-6-thomas.petazzoni@bootlin.com> <310621ef-6a6e-f7e6-18d1-20ace14a81b7@smile.fr> Organization: Bootlin X-Mailer: Claws Mail 4.0.0 (GTK+ 3.24.31; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Subject: Re: [Buildroot] [PATCH v3 05/11] package/pkg-cargo.mk: introduce the cargo package infrastructure X-BeenThere: buildroot@buildroot.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion and development of buildroot List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Matt Weber , Patrick Havelange , James Hilliard , Buildroot List , "Yann E. MORIN" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: buildroot-bounces@buildroot.org Sender: "buildroot" On Fri, 7 Jan 2022 22:07:26 +0100 Romain Naour 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