Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH v5 2/6] at-spi2-atk: new package
Date: Mon, 25 Jun 2018 23:10:45 +0200	[thread overview]
Message-ID: <20180625231045.27dbf4be@windsurf.home> (raw)
In-Reply-To: <20180622003340.10859-3-joseph.kogut@gmail.com>

Hello,

On Thu, 21 Jun 2018 17:33:36 -0700, Joseph Kogut wrote:

> diff --git a/package/at-spi2-atk/Config.in b/package/at-spi2-atk/Config.in
> new file mode 100644
> index 0000000000..599913c7df
> --- /dev/null
> +++ b/package/at-spi2-atk/Config.in
> @@ -0,0 +1,21 @@
> +config BR2_PACKAGE_AT_SPI2_ATK
> +	bool "at-spi2-atk"
> +	depends on BR2_PACKAGE_XORG7 # at-spi2-core
> +	depends on BR2_TOOLCHAIN_HAS_THREADS # glib2
> +	depends on BR2_USE_MMU # glib2
> +	depends on BR2_USE_WCHAR # glib2
> +	select BR2_PACKAGE_ATK
> +	select BR2_PACKAGE_AT_SPI2_CORE
> +	select BR2_PACKAGE_LIBGLIB2
> +	help
> +	  The At-Spi2 Atk package contains a library that bridges
> +	  ATK to At-Spi2 D-Bus service.
> +
> +	  https://www.freedesktop.org/wiki/Accessibility/AT-SPI2/
> +
> +comment "at-spi2-atk needs a toolchain w/ wchar, threads"
> +	depends on BR2_USE_MMU
> +	depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS
> +
> +comment "at-spi2-atk depends on X.org"

Just like at-spi2-core, I've added:

	depends on BR2_USE_MMU

for the same reason.

> +	depends on !BR2_PACKAGE_XORG7

> +AT_SPI2_ATK_VERSION_MAJOR = 2.26
> +AT_SPI2_ATK_VERSION = $(AT_SPI2_ATK_VERSION_MAJOR).2
> +AT_SPI2_ATK_SOURCE = at-spi2-atk-$(AT_SPI2_ATK_VERSION).tar.xz
> +AT_SPI2_ATK_SITE =  http://ftp.gnome.org/pub/gnome/sources/at-spi2-atk/$(AT_SPI2_ATK_VERSION_MAJOR)
> +AT_SPI2_ATK_LICENSE = LGPL-2.0+
> +AT_SPI2_ATK_LICENSE_FILES = COPYING
> +AT_SPI2_ATK_INSTALL_STAGING = YES
> +AT_SPI2_ATK_INSTALL_STAGING_OPTS = DESTDIR=$(STAGING_DIR) install

This line was not needed, it's the default behavior of the
autotools-package infrastructure for staging installation.

> +AT_SPI2_ATK_DEPENDENCIES = atk at-spi2-core libglib2 host-pkgconf
> +
> +$(eval $(autotools-package))

Any reason to use autotools here instead of meson ?

Anyway, I've applied to master with the fixes detailed above.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-06-25 21:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22  0:33 [Buildroot] [RFC PATCH v5 0/6] chromium: new package Joseph Kogut
2018-06-22  0:33 ` [Buildroot] [RFC PATCH v5 1/6] at-spi2-core: " Joseph Kogut
2018-06-25 21:09   ` Thomas Petazzoni
2018-06-25 21:20     ` Joseph Kogut
2018-06-22  0:33 ` [Buildroot] [RFC PATCH v5 2/6] at-spi2-atk: " Joseph Kogut
2018-06-25 21:10   ` Thomas Petazzoni [this message]
2018-06-25 21:18     ` Joseph Kogut
2018-06-22  0:33 ` [Buildroot] [RFC PATCH v5 3/6] libgtk3: convert atk-bridge to optional dependency Joseph Kogut
2018-06-22  0:33 ` [Buildroot] [RFC PATCH v5 4/6] llvm: add config to build backend for host arch Joseph Kogut
2018-06-22 10:09   ` Valentin Korenblit
2018-06-22  0:33 ` [Buildroot] [RFC PATCH v5 5/6] lld: new package Joseph Kogut
2018-06-22  0:33 ` [Buildroot] [RFC PATCH v5 6/6] chromium: " Joseph Kogut

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=20180625231045.27dbf4be@windsurf.home \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox