All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Khem Raj <raj.khem@gmail.com>, openembedded-core@lists.openembedded.org
Cc: Bartosz Golaszewski <brgl@bgdev.pl>
Subject: [OE-core][PATCH 2/4] cargo: run in --offline mode
Date: Mon,  6 Jun 2022 15:26:51 +0200	[thread overview]
Message-ID: <20220606132653.60232-3-brgl@bgdev.pl> (raw)
In-Reply-To: <20220606132653.60232-1-brgl@bgdev.pl>

We fetch sources ourselves in do_fetch, don't let cargo fetch anything
else on its own during the build stage.

Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>
---
 meta/classes/cargo.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/cargo.bbclass b/meta/classes/cargo.bbclass
index 4a780a501f..7cfd4a2666 100644
--- a/meta/classes/cargo.bbclass
+++ b/meta/classes/cargo.bbclass
@@ -32,7 +32,7 @@ MANIFEST_PATH ??= "${S}/${CARGO_SRC_DIR}/Cargo.toml"
 
 RUSTFLAGS ??= ""
 BUILD_MODE = "${@['--release', ''][d.getVar('DEBUG_BUILD') == '1']}"
-CARGO_BUILD_FLAGS = "-v --target ${HOST_SYS} ${BUILD_MODE} --manifest-path=${MANIFEST_PATH}"
+CARGO_BUILD_FLAGS = "-v --target ${HOST_SYS} ${BUILD_MODE} --manifest-path=${MANIFEST_PATH} --offline"
 
 # This is based on the content of CARGO_BUILD_FLAGS and generally will need to
 # change if CARGO_BUILD_FLAGS changes.
-- 
2.34.1



  parent reply	other threads:[~2022-06-06 13:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 13:26 [OE-core][PATCH 0/4] cargo: improve the build process and add a new recipe Bartosz Golaszewski
2022-06-06 13:26 ` [OE-core][PATCH 1/4] cargo: don't update git submodules in --offline mode Bartosz Golaszewski
2022-06-06 15:20   ` Alexander Kanavin
2022-06-06 13:26 ` Bartosz Golaszewski [this message]
2022-06-06 13:26 ` [OE-core][PATCH 3/4] cargo: pass PACKAGECONFIG_CONFARGS to cargo build Bartosz Golaszewski
2022-06-06 13:26 ` [OE-core][PATCH 4/4] gstreamer1.0-plugins-rs: new package Bartosz Golaszewski
2022-06-06 15:22   ` Alexander Kanavin
2022-06-06 15:36     ` Bartosz Golaszewski

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=20220606132653.60232-3-brgl@bgdev.pl \
    --to=brgl@bgdev.pl \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.