From: "Kowalsky, Clara" <clara.kowalsky@siemens.com>
To: "Kiszka, Jan" <jan.kiszka@siemens.com>,
"xenomai@lists.linux.dev" <xenomai@lists.linux.dev>,
"rpm@xenomai.org" <rpm@xenomai.org>
Subject: RE: [xenomai-images][PATCH v1 2/5] libevl: Add libevl recipe
Date: Thu, 21 Dec 2023 16:59:08 +0000 [thread overview]
Message-ID: <AS5PR10MB8173350198E5E7C26CF785C89395A@AS5PR10MB8173.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <967c1b48-a7c8-4420-8178-372e75642b56@siemens.com>
> -----Original Message-----
> From: Kiszka, Jan (T CED) <jan.kiszka@siemens.com>
> Sent: Sonntag, 17. Dezember 2023 17:53
> To: Kowalsky, Clara (T CED SES-DE) <clara.kowalsky@siemens.com>;
> xenomai@lists.linux.dev; rpm@xenomai.org
> Subject: Re: [xenomai-images][PATCH v1 2/5] libevl: Add libevl recipe
>
> On 15.12.23 12:43, Clara Kowalsky wrote:
> > This recipe allows building the evl userspace.
> >
> > Signed-off-by: Clara Kowalsky <clara.kowalsky@siemens.com>
> > ---
> > opt-libevl-master.yml | 17 +++++++++
> > opt-libevl-next.yml | 17 +++++++++
> > recipes-core/libevl/files/debian/changelog | 5 +++
> > recipes-core/libevl/files/debian/compat | 1 +
> > recipes-core/libevl/files/debian/control | 12 ++++++
> > recipes-core/libevl/files/debian/rules | 12 ++++++
> > recipes-core/libevl/libevl_0.1.bb | 44 ++++++++++++++++++++++
> > 7 files changed, 108 insertions(+)
> > create mode 100644 opt-libevl-master.yml create mode 100644
> > opt-libevl-next.yml create mode 100644
> > recipes-core/libevl/files/debian/changelog
> > create mode 100644 recipes-core/libevl/files/debian/compat
> > create mode 100644 recipes-core/libevl/files/debian/control
> > create mode 100755 recipes-core/libevl/files/debian/rules
> > create mode 100644 recipes-core/libevl/libevl_0.1.bb
> >
>
> libevl/ should go to recipes-xenomai/.
>
> > diff --git a/opt-libevl-master.yml b/opt-libevl-master.yml new file
> > mode 100644 index 0000000..b241541
> > --- /dev/null
> > +++ b/opt-libevl-master.yml
> > @@ -0,0 +1,17 @@
> > +#
> > +# Xenomai Real-Time System
> > +#
> > +# Copyright (c) Siemens AG, 2023
> > +#
> > +# Authors:
> > +# Clara Kowalsky <clara.kowalsky@siemens.com> # #
> > +SPDX-License-Identifier: MIT #
> > +
> > +header:
> > + version: 10
> > +
> > +local_conf_header:
> > + libevl-version: |
> > + LIBEVL_BRANCH = "master"
> > diff --git a/opt-libevl-next.yml b/opt-libevl-next.yml new file mode
> > 100644 index 0000000..6b64ac7
> > --- /dev/null
> > +++ b/opt-libevl-next.yml
> > @@ -0,0 +1,17 @@
> > +#
> > +# Xenomai Real-Time System
> > +#
> > +# Copyright (c) Siemens AG, 2023
> > +#
> > +# Authors:
> > +# Clara Kowalsky <clara.kowalsky@siemens.com> # #
> > +SPDX-License-Identifier: MIT #
> > +
> > +header:
> > + version: 10
> > +
> > +local_conf_header:
> > + libevl-version: |
> > + LIBEVL_BRANCH = "next"
> > diff --git a/recipes-core/libevl/files/debian/changelog
> > b/recipes-core/libevl/files/debian/changelog
> > new file mode 100644
> > index 0000000..b8f8279
> > --- /dev/null
> > +++ b/recipes-core/libevl/files/debian/changelog
> > @@ -0,0 +1,5 @@
> > +libevl (0.1) UNRELEASED; urgency=low
> > +
> > + * generated by Isar
> > +
> > + -- Unknown maintainer <unknown@example.com> Thu, 01 Jan 1970
> > + 01:00:00 +0000
> > diff --git a/recipes-core/libevl/files/debian/compat
> > b/recipes-core/libevl/files/debian/compat
> > new file mode 100644
> > index 0000000..f599e28
> > --- /dev/null
> > +++ b/recipes-core/libevl/files/debian/compat
> > @@ -0,0 +1 @@
> > +10
> > diff --git a/recipes-core/libevl/files/debian/control
> > b/recipes-core/libevl/files/debian/control
> > new file mode 100644
> > index 0000000..94d2d8a
> > --- /dev/null
> > +++ b/recipes-core/libevl/files/debian/control
> > @@ -0,0 +1,12 @@
> > +Source: libevl
> > +Section: misc
> > +Priority: optional
> > +Standards-Version: 3.9.6
> > +Maintainer: Unknown maintainer <unknown@example.com>
> > +Build-Depends: debhelper (>= 10), meson, linux-libc-dev (= 6.1+r0)
>
> Ok, that "(= 6.1+r0)" was likely the workaround for sbuild not updating the
> pre-installed linux-libc-dev package with our self-built version.
> Worked only for 6.1, failed for any other other EVL kernel.
>
> I've sent a Isar patch that should resolve the issue, at least for x86.
> We have more fundamental problems in Isar when it comes to using cross
> linux-libc-dev.
>
> Jan
Your Isar patch is working fine.
Clara
>
> > +
> > +Package: libevl
> > +Architecture: any
> > +Depends:
> > +Conflicts:
> > +Description: install libevl related repositories
> > diff --git a/recipes-core/libevl/files/debian/rules
> > b/recipes-core/libevl/files/debian/rules
> > new file mode 100755
> > index 0000000..80e995e
> > --- /dev/null
> > +++ b/recipes-core/libevl/files/debian/rules
> > @@ -0,0 +1,12 @@
> > +#!/usr/bin/make -f
> > +
> > +override_dh_fixperms:
> > + dh_fixperms
> > +
> > +%:
> > + dh $@ --buildsystem=meson
> > +
> > +override_dh_auto_configure:
> > + dh_auto_configure -- \
> > + -Ddeb_host_multiarch=$(shell dpkg-architecture -q \
> > + DEB_HOST_MULTIARCH)
> > diff --git a/recipes-core/libevl/libevl_0.1.bb
> > b/recipes-core/libevl/libevl_0.1.bb
> > new file mode 100644
> > index 0000000..76a45aa
> > --- /dev/null
> > +++ b/recipes-core/libevl/libevl_0.1.bb
> > @@ -0,0 +1,44 @@
> > +#
> > +# Xenomai Real-Time System
> > +#
> > +# Copyright (c) Siemens AG, 2018-2023 # # Authors:
> > +# Clara Kowalsky <clara.kowalsky@siemens.com> # #
> > +SPDX-License-Identifier: MIT #
> > +
> > +DESCRIPTION="install libevl related repositories"
> > +
> > +inherit dpkg
> > +
> > +LIBEVL_BRANCH ?= "master"
> > +
> > +SRCREV = "${LIBEVL_BRANCH}"
> > +PV ?= "${@d.getVar('SRCREV')}"
> > +SRC_URI = " \
> > +
> git://source.denx.de/Xenomai/xenomai4/libevl.git;protocol=https;branch=${L
> IBEVL_BRANCH} \
> > + file://debian \
> > + "
> > +SRCREV = "${AUTOREV}"
> > +
> > +DEPENDS="linux-evl"
> > +
> > +S = "${WORKDIR}/git"
> > +
> > +do_prepare_build[cleandirs] += "${S}/debian"
> > +do_prepare_build() {
> > + cp -r ${WORKDIR}/debian ${S}
> > +
> > + bbplain $(printf "libevl-%s: Building revision %.20s\n" \
> > + ${PV} ${COMMIT})
> > +}
> > +
> > +def get_commit(d):
> > + try:
> > + return bb.fetch2.get_srcrev(d).strip('AUTOINC+')
> > + except bb.fetch2.FetchError:
> > + return ""
> > +
> > +COMMIT="${@get_commit(d)}"
>
> --
> Siemens AG, Technology
> Linux Expert Center
next prev parent reply other threads:[~2023-12-21 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 11:43 [xenomai-images][PATCH v1 0/5] Add evl support to xenomai-images Clara Kowalsky
2023-12-15 11:43 ` [xenomai-images][PATCH v1 1/5] linux-xenomai: Factor out base.inc Clara Kowalsky
2023-12-15 17:28 ` Jan Kiszka
2023-12-15 11:43 ` [xenomai-images][PATCH v1 2/5] libevl: Add libevl recipe Clara Kowalsky
2023-12-15 17:42 ` Jan Kiszka
2023-12-17 16:53 ` Jan Kiszka
2023-12-21 16:59 ` Kowalsky, Clara [this message]
2023-12-15 11:43 ` [xenomai-images][PATCH v1 3/5] evl: Enable evl image build Clara Kowalsky
2023-12-15 17:49 ` Jan Kiszka
2023-12-21 16:54 ` Kowalsky, Clara
2023-12-15 11:43 ` [xenomai-images][PATCH v1 4/5] ci: Add evl test Clara Kowalsky
2023-12-15 11:43 ` [xenomai-images][PATCH v1 5/5] kconfig: Add build options for evl Clara Kowalsky
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=AS5PR10MB8173350198E5E7C26CF785C89395A@AS5PR10MB8173.EURPRD10.PROD.OUTLOOK.COM \
--to=clara.kowalsky@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=rpm@xenomai.org \
--cc=xenomai@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).