From: Florian Bezdeka <florian.bezdeka@siemens.com>
To: rpm@xenomai.org, clara.kowalsky@siemens.com
Cc: xenomai@lists.linux.dev
Subject: evl: Problems while trying to build up a debianization
Date: Fri, 03 Nov 2023 15:47:30 +0100 [thread overview]
Message-ID: <4481c3ac97badd74e74849a97b049f1bb5c89fb7.camel@siemens.com> (raw)
Hi Philippe,
we're starting with some very first steps regarding EVL here. The idea
was to enable the xenomai-images project to generate images with EVL as
well.
Currently we're failing because there is some confusion about the UAPI
installation here.
The meson build and install steps of libevl refer to some headers
coming from the (sources) of linux-evl.
We're trying to integrate this meson based build into a debianization.
As libevl depends on some headers delivered by the kernel "package" we
would model that as a build dependency. libevl would depend on linux-
evl-headers.
Right now we're failing inside the setup-uapi.sh script because the
sources of linux-evl are not available. We were not able to set -Duapi
correctly.
To my understanding the dance with include/ inside the meson build
directory is necessary to limit the number of "special" include paths.
Is that correct?
Another issue we came across is the installation of the UAPI headers by
the libevl install step. Why is that necessary at all? The only
component that should depend on that headers is libevl itself. No?
Any idea how we could fix that up without breaking your local build
process?
Best regards,
Florian
--
Siemens AG, Technology
Linux Expert Center
next reply other threads:[~2023-11-03 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 14:47 Florian Bezdeka [this message]
2023-11-05 17:23 ` evl: Problems while trying to build up a debianization Philippe Gerum
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=4481c3ac97badd74e74849a97b049f1bb5c89fb7.camel@siemens.com \
--to=florian.bezdeka@siemens.com \
--cc=clara.kowalsky@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).