From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] package/xenomai: Pull from git
Date: Thu, 12 Dec 2019 21:52:01 +0100 [thread overview]
Message-ID: <20191212215201.7761bccd@windsurf> (raw)
In-Reply-To: <5404679c83c28260c53e2fc54cdbeafda2929914.1576176280.git.jan.kiszka@siemens.com>
Hello Jan,
On Thu, 12 Dec 2019 19:44:38 +0100
Jan Kiszka <jan.kiszka@siemens.com> wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> This allows to pick also git revisions via XENOMAI_VERSION.
You don't have tarballs for new releases? We generally prefer to use
tarballs when available.
> XENOMAI_VERSION = $(call qstrip,$(BR2_PACKAGE_XENOMAI_VERSION))
> ifeq ($(XENOMAI_VERSION),)
> -XENOMAI_VERSION = 3.0.9
> +XENOMAI_VERSION = v3.0.9
The version needs to stay 3.0.9, i.e without the "v" prefix.
> else
> BR_NO_CHECK_HASH_FOR += $(XENOMAI_SOURCE)
> endif
>
> -XENOMAI_SITE = http://xenomai.org/downloads/xenomai/stable
> +XENOMAI_SITE = https://gitlab.denx.de/Xenomai/xenomai/-/archive/$(XENOMAI_VERSION)
.. which can be done by changing this to:
XENOMAI_SITE = https://gitlab.denx.de/Xenomai/xenomai/-/archive/v$(XENOMAI_VERSION)
We want this so that our XENOMAI_VERSION value matches the
release-monitoring.org entry for Xenomai:
https://release-monitoring.org/project/18451/. BTW, it seems like they
don't know about version 3.0.10, as they are checking
https://xenomai.org/downloads/xenomai/stable/ and there is no tarball
for 3.0.10. I guess we need to change the Xenomai entry in
release-monitoring.org to make it use the Git repository.
> +define XENOMAI_BOOTSTRAP
> + (cd $(@D); ./scripts/bootstrap)
> +endef
> +
> +XENOMAI_PRE_CONFIGURE_HOOKS += XENOMAI_BOOTSTRAP
This is not good, because nothing guarantees you autoconf/automake are
available. Our preferred way of handling this is to use:
XENOMAI_AUTORECONF = YES
which simply calls autoreconf on the project. However, I can imagine
that Xenomai is a bit special, so if AUTORECONF = YES doesn't work, you
can keep your PRE_CONFIGURE_HOOKS, but you need to add host-autoconf
and host-automake to XENOMAI_DEPENDENCIES, and possibly host-libtool if
libtool is used to build the libraries.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-12-12 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 18:44 [Buildroot] [PATCH 0/4] package/xenomai: Fixes, updates, enhancements Jan Kiszka
2019-12-12 18:44 ` [Buildroot] [PATCH 1/4] package/xenomai: Smokey's not a skin Jan Kiszka
2019-12-12 20:48 ` Thomas Petazzoni
2019-12-13 6:24 ` Jan Kiszka
2019-12-12 18:44 ` [Buildroot] [PATCH 2/4] package/xenomai: Pull from git Jan Kiszka
2019-12-12 20:52 ` Thomas Petazzoni [this message]
2019-12-13 6:32 ` Jan Kiszka
2019-12-12 18:44 ` [Buildroot] [PATCH 3/4] package/xenomai: Bump version to 3.0.10 Jan Kiszka
2019-12-12 18:44 ` [Buildroot] [PATCH 4/4] package/xenomai: Clean up wrappers cleanup Jan Kiszka
2019-12-12 20:45 ` [Buildroot] [PATCH 0/4] package/xenomai: Fixes, updates, enhancements 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=20191212215201.7761bccd@windsurf \
--to=thomas.petazzoni@bootlin.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 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.