From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH/next 1/2] package/wlroots: new package
Date: Fri, 17 May 2019 09:48:23 +0200 [thread overview]
Message-ID: <20190517094823.4dab419d@windsurf> (raw)
In-Reply-To: <20190516220836.24543-2-aperez@igalia.com>
Hello,
On Fri, 17 May 2019 01:08:35 +0300
Adrian Perez de Castro <aperez@igalia.com> wrote:
> diff --git a/package/wlroots/Config.in b/package/wlroots/Config.in
> new file mode 100644
> index 0000000000..45db63f62c
> --- /dev/null
> +++ b/package/wlroots/Config.in
> @@ -0,0 +1,65 @@
> +config BR2_PACKAGE_WLROOTS
> + bool "wlroots"
> + depends on !BR2_STATIC_LIBS # mesa3d, wayland
You're not selecting "mesa3d", so this "mesa3d" comment doesn't make
sense.
> + depends on BR2_INSTALL_LIBSTDCPP # freedrp, mesa3d
You're not selecting freerdp nor mesa3d, so the comment doesn't make
sense either. This dependency doesn't seem to be needed at all.
> + depends on BR2_TOOLCHAIN_HAS_THREADS # libdrm, wayland
> + depends on BR2_TOOLCHAIN_HAS_SYNC_1 # mesa3d
This dependency doesn't seem to be needed, at least you don't use
mesa3d, and none of the packages you select has a "depends on
BR2_TOOLCHAIN_HAS_SYNC".
> + depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL # mesa3d
Same.
> +if BR2_PACKAGE_WLROOTS
> +
> +config BR2_PACKAGE_WLROOTS_RDP
> + bool "RDP backend support"
> + depends on BR2_PACKAGE_FREERDP
If you "depends on" something...
> + depends on BR2_USE_WCHAR # freerdp
> + depends on BR2_USE_MMU # libglib2
> + depends on BR2_TOOLCHAIN_HAS_SYNC_4 # freerdp
... there's no point in replicating its dependencies.
> +WLROOTS_VERSION = 0.6.0
> +WLROOTS_SITE = https://github.com/swaywm/wlroots/archive
> +WLROOTS_SOURCE = $(WLROOTS_VERSION).tar.gz
> +WLROOTS_LICENSE = MIT
> +WLROOTS_INSTALL_STAGING = YES
> +
> +WLROOTS_DEPENDENCIES = host-pkgconf host-wayland libegl libinput \
> + libxkbcommon mesa3d pixman udev \
Ah, so you have mesa3d in your dependencies, but you don't select it ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-17 7:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 22:08 [Buildroot] [RFC PATCH/next 0/2] Add Cage and wlroots packages Adrian Perez de Castro
2019-05-16 22:08 ` [Buildroot] [RFC PATCH/next 1/2] package/wlroots: new package Adrian Perez de Castro
2019-05-17 7:48 ` Thomas Petazzoni [this message]
2019-06-12 23:41 ` Adrian Perez de Castro
2019-05-18 15:47 ` François Perrad
2019-06-12 23:31 ` Adrian Perez de Castro
2019-05-16 22:08 ` [Buildroot] [RFC PATCH/next 2/2] package/cage: " Adrian Perez de Castro
2019-05-17 9:21 ` Thomas Petazzoni
2019-06-12 22:43 ` Adrian Perez de Castro
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=20190517094823.4dab419d@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.