NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
a6bba674a2
kumquat-buildroot/package/libgail/Config.in

25 lines
897 B
Plaintext
Raw Normal View History

package: add libgail package This package include a patch for directfb support. This patch has been proposed for upstream integration (https://bugzilla.gnome.org/show_bug.cgi?id=614199). Signed-off-by: Lionel Landwerlin <llandwerlin@gmail.com>
2010-04-14 01:06:08 +02:00
config BR2_PACKAGE_LIBGAIL
bool "libgail"
libglib2: needs threads This commit adds a dependency of the libglib2 package on thread support in the toolchain, since upstream libglib2 doesn't build without thread support. The commit is rather large as it involves propagating the dependency on thread support to all reverse dependencies of the libglib2 package. [Thomas: squash all patches into one, make a few minor fixes, the most important one being to not add comments about MMU requirement when a package doesn't work on !MMU platforms.] Signed-off-by: Spenser Gilliland <spenser@gillilanding.com>
2013-07-15 21:47:50 +02:00
depends on BR2_USE_WCHAR # pango -> libglib2
depends on BR2_TOOLCHAIN_HAS_THREADS # pango -> libglib2
package: add libgail package This package include a patch for directfb support. This patch has been proposed for upstream integration (https://bugzilla.gnome.org/show_bug.cgi?id=614199). Signed-off-by: Lionel Landwerlin <llandwerlin@gmail.com>
2010-04-14 01:06:08 +02:00
depends on BR2_PACKAGE_LIBGTK2
select BR2_PACKAGE_PANGO
help
GAIL provides accessibility support for gtk+ and
libgnomecanvas by implementing AtkObjects for widgets in
gtk+ and libgnomecanvas.
The GAIL library is a GTK+ module. For example, if the
module is loaded in a program which calls
gtk_widget_get_accessible() for a GtkEntry an instance of
GailEntry is returned. This module is normally used with the
atk-bridge GTK+ module from at-spi to allow an assistive
technology, e.g a screenreader, to query or drive the
program.
http://developer.gnome.org/projects/gap
libglib2: needs threads This commit adds a dependency of the libglib2 package on thread support in the toolchain, since upstream libglib2 doesn't build without thread support. The commit is rather large as it involves propagating the dependency on thread support to all reverse dependencies of the libglib2 package. [Thomas: squash all patches into one, make a few minor fixes, the most important one being to not add comments about MMU requirement when a package doesn't work on !MMU platforms.] Signed-off-by: Spenser Gilliland <spenser@gillilanding.com>
2013-07-15 21:47:50 +02:00
Config.in files: unify comments of toolchain option dependencies This patch lines up the comments in Config.in files that clarify which toolchain options the package depends on. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-10-13 16:55:32 +02:00
comment "libgail needs a toolchain w/ wchar, threads"
Config.in files: add missing dependencies to toolchain option comments When a package A depends on config option B and toolchain option C, then the comment that is given when C is not fulfilled should also depend on B. For example: config BR2_PACKAGE_A depends on BR2_B depends on BR2_LARGEFILE depends on BR2_WCHAR comment "A needs a toolchain w/ largefile, wchar" depends on !BR2_LARGEFILE || !BR2_WCHAR This comment should actually be: comment "A needs a toolchain w/ largefile, wchar" depends on BR2_B depends on !BR2_LARGEFILE || !BR2_WCHAR or if possible (typically when B is a package config option declared in that same Config.in file): if BR2_B comment "A needs a toolchain w/ largefile, wchar" depends on !BR2_LARGEFILE || !BR2_WCHAR [other config options depending on B] endif Otherwise, the comment would be visible even though the other dependencies are not met. This patch adds such missing dependencies, and changes existing such dependencies from depends on BR2_BASE_DEP && !BR2_TOOLCHAIN_USES_GLIBC to depends on BR2_BASE_DEP depends on !BR2_TOOLCHAIN_USES_GLIBC so that (positive) base dependencies are separate from the (negative) toolchain dependencies. This strategy makes it easier to write such comments (because one can simply copy the base dependency from the actual package config option), but also avoids complex and long boolean expressions. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> (untested) Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-11-07 09:24:37 +01:00
depends on BR2_PACKAGE_LIBGTK2
depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS
Reference in New Issue Copy Permalink