From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/weston: needs headers >= 4.4
Date: Mon, 10 Jun 2019 12:01:12 +0200 [thread overview]
Message-ID: <20190610100112.GE13603@scaer> (raw)
In-Reply-To: <20190610093702.GD13603@scaer>
Fabrice, All,
On 2019-06-10 11:37 +0200, Yann E. MORIN spake thusly:
> On 2019-06-10 00:27 +0200, Fabrice Fontaine spake thusly:
> > weston includes input-event-codes.h since version 5.0.91 and
> > https://github.com/wayland-project/weston/commit/6e229ca26381bc8191fd9af1e439c311da709aff
>
> Actually, that include is in fact not needed. Just remove it, and it
> still builds! ;-)
So, even with a toolchain with headers 4.20, it is not needed to include
linux/input-event-codes.h.
That's because it is pulled in from linux/input.h, which it self is
pulled in from libevdev/libevdev.h.
So, the patch I suggested earlier is probably the better technically,
but one that just includes linux/input.h instead is simpler.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2019-06-10 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 22:27 [Buildroot] [PATCH 1/1] package/weston: needs headers >= 4.4 Fabrice Fontaine
2019-06-10 9:37 ` Yann E. MORIN
2019-06-10 10:01 ` Yann E. MORIN [this message]
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=20190610100112.GE13603@scaer \
--to=yann.morin.1998@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox