All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Adrian Perez de Castro <aperez@igalia.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/3] package/wlroots: bump to version 0.15.1
Date: Wed, 08 Feb 2023 14:54:06 +0100	[thread overview]
Message-ID: <877cws5kld.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220422214919.367067-2-aperez@igalia.com> (Adrian Perez de Castro's message of "Sat, 23 Apr 2022 00:49:17 +0300")

>>>>> "Adrian" == Adrian Perez de Castro <aperez@igalia.com> writes:

 > Update to version 0.15.1, and adapt to upstream changes:
 > - Adapted from the old -Dfoo-backend Meson option to the new -Dbackends
 >   one, which is an array. The set of always enabled backends matches the
 >   previous selection: drm+libinput always enabled, x11 only if selected.
 > - Removed the libpng and ffmpeg dependency, which are no longer needed
 >   with examples disabled (which is always the case for Buildroot).
 > - Changed homepage and download site URLs to the FreeDesktop.org GitLab.

 > This release changes the API/ABI, and applications which use wlroots
 > must be adapted and rebuilt. Currently in Buildroot we have only the
 > cage compositor, to be updated in a follow-up patch.

 > Signed-off-by: Adrian Perez de Castro <aperez@igalia.com>

Old patch, but while testing the recently added sway package I notice
that wlroots fails to build with X11 support:

Found CMake: /usr/bin/cmake (3.18.4)
Run-time dependency xwayland found: NO (tried pkgconfig and cmake)
Program Xwayland found: NO

How is this supposed to work? We don't have a Xwayland package in
Buildroot, so no pkgconfig file. I see there is some fallback logic in
wlroots to look for an Xwayland binary (on the host presumably), but
that doesn't work for hosts without it and will again fail at runtime.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-02-08 13:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22 21:49 [Buildroot] [PATCH 0/3] Update wlroots to the latest release Adrian Perez de Castro
2022-04-22 21:49 ` [Buildroot] [PATCH 1/3] package/wlroots: bump to version 0.15.1 Adrian Perez de Castro
2023-02-08 13:54   ` Peter Korsgaard [this message]
2022-04-22 21:49 ` [Buildroot] [PATCH 2/3] package/cage: add upstream patch for wlroots 0.15.x Adrian Perez de Castro
2022-04-22 21:49 ` [Buildroot] [PATCH 3/3] package/wlroots: enable vulkan renderer if possible Adrian Perez de Castro
2022-04-25 19:34 ` [Buildroot] [PATCH 0/3] Update wlroots to the latest release Arnout Vandecappelle

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=877cws5kld.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=aperez@igalia.com \
    --cc=buildroot@buildroot.org \
    /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.