From: CHEN Xiangyu via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: CHEN Xiangyu <xiangyu.chen@aol.com>, Simon Dawson <spdawson@gmail.com>
Subject: [Buildroot] [PATCH] boot/at91bootstrap3: add svn repository method
Date: Tue, 19 Oct 2021 16:05:14 +0800 [thread overview]
Message-ID: <20211019080514.6189-1-xiangyu.chen@aol.com> (raw)
In-Reply-To: 20211019080514.6189-1-xiangyu.chen.ref@aol.com
Since more and more traditional companies are starting using buildroot
with AT91SAM9x chipset as their product firmware, much of them are still
using SVN as their version control system. So add svn repository method
to AT91bootstrap3 package.
Signed-off-by: CHEN Xiangyu <xiangyu.chen@aol.com>
---
boot/at91bootstrap3/Config.in | 14 +++++++++++---
boot/at91bootstrap3/at91bootstrap3.mk | 3 +++
2 files changed, 14 insertions(+), 3 deletions(-)
diff --git a/boot/at91bootstrap3/Config.in b/boot/at91bootstrap3/Config.in
index 650d3a23c8..3cfc0bbe14 100644
--- a/boot/at91bootstrap3/Config.in
+++ b/boot/at91bootstrap3/Config.in
@@ -30,6 +30,14 @@ config BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_GIT
This option allows Buildroot to get the AT91 Bootstrap 3
source code from a Git repository.
+config BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_SVN
+ bool "Custom SVN repository"
+ help
+ This option allows Buildroot to get the AT91 Bootstrap 3
+ source code from a Subversion repository
+
config BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_TARBALL
bool "Custom tarball"
@@ -39,7 +45,7 @@ config BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_TARBALL_LOCATION
string "URL of custom AT91Bootstrap tarball"
depends on BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_TARBALL
-if BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_GIT
+if BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_GIT || BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_SVN
config BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_URL
string "URL of custom repository"
@@ -47,7 +53,7 @@ config BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_URL
config BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_VERSION
string "Custom repository version"
help
- Revision to use in the typical format used by Git
+ Revision to use in the typical format used by Git or SVN
E.G. a sha id, a tag, branch, ..
endif
@@ -57,7 +63,7 @@ config BR2_TARGET_AT91BOOTSTRAP3_VERSION
default "v4.0.0" if BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION
default "v3.10.3" if BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION_3X
default BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_VERSION \
- if BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_GIT
+ if BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_GIT || BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_SVN
default "custom" if BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_TARBALL
config BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_PATCH_DIR
diff --git a/boot/at91bootstrap3/at91bootstrap3.mk b/boot/at91bootstrap3/at91bootstrap3.mk
index 1e2a3a44b0..f609176a3f 100644
--- a/boot/at91bootstrap3/at91bootstrap3.mk
+++ b/boot/at91bootstrap3/at91bootstrap3.mk
@@ -15,6 +15,9 @@ else ifeq ($(BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_GIT),y)
AT91BOOTSTRAP3_SITE = $(call qstrip,$(BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_URL))
AT91BOOTSTRAP3_SITE_METHOD = git
BR_NO_CHECK_HASH_FOR += $(AT91BOOTSTRAP3_SOURCE)
+else ifeq ($(BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_SVN),y)
+AT91BOOTSTRAP3_SITE_METHOD = svn
+BR_NO_CHECK_HASH_FOR += $(AT91BOOTSTRAP3_SOURCE)
else
AT91BOOTSTRAP3_SITE = $(call github,linux4sam,at91bootstrap,$(AT91BOOTSTRAP3_VERSION))
endif
--
2.26.2
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next parent reply other threads:[~2021-10-19 8:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211019080514.6189-1-xiangyu.chen.ref@aol.com>
2021-10-19 8:05 ` CHEN Xiangyu via buildroot [this message]
2021-10-24 16:49 ` [Buildroot] [PATCH] boot/at91bootstrap3: add svn repository method Thomas Petazzoni
[not found] <810116346.3867627.1634462494722.ref@mail.yahoo.com>
2021-10-17 9:21 ` Xiangyu Chen via buildroot
[not found] <1553939413.3863322.1634461967644.ref@mail.yahoo.com>
2021-10-17 9:12 ` Xiangyu Chen via buildroot
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=20211019080514.6189-1-xiangyu.chen@aol.com \
--to=buildroot@buildroot.org \
--cc=spdawson@gmail.com \
--cc=xiangyu.chen@aol.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.