kumquat-buildroot/package/gettext/Config.in

config BR2_PACKAGE_GETTEXT
	bool "gettext"
	depends on BR2_NEEDS_GETTEXT
	depends on BR2_USE_WCHAR
	help
	  The GNU `gettext' utilities are a set of tools that provide a
	  framework to help other GNU packages produce multi-lingual
	  messages.

	  Only the libintl library will be installed in the
	  target. The full gettext suite, including tools, will be
	  installed in the staging directory.

	  http://www.gnu.org/software/gettext/

comment "gettext needs a toolchain w/ wchar"
	depends on BR2_NEEDS_GETTEXT
	depends on !BR2_USE_WCHAR
final step in buildroot facelift 2004-10-09 08:13:40 +02:00			`config BR2_PACKAGE_GETTEXT`
merge help descriptions written by Tom Cameron 2004-12-24 10:23:11 +01:00			`bool "gettext"`
gettext: make only available if BR2_NEEDS_GETTEXT is set This allows to make sure that an user, or a randpackageconfig, will not select the gettext or libintl package when using an external toolchain based on glibc/eglibc. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> 2010-05-14 09:46:21 +02:00			`depends on BR2_NEEDS_GETTEXT`
package: gettext needs WCHAR support gettext needs WCHAR support in the toolchain, and as libglib2 depends on gettext and lots of stuff depends on libglib2, quite a lot of packages needs to have their dependencies adjusted. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk> 2010-05-25 23:38:44 +02:00			`depends on BR2_USE_WCHAR`
final step in buildroot facelift 2004-10-09 08:13:40 +02:00			`help`
fix gettext so it will actually compile and install 2007-01-10 07:05:18 +01:00			The GNU `gettext' utilities are a set of tools that provide a
			`framework to help other GNU packages produce multi-lingual`
merge help descriptions written by Tom Cameron 2004-12-24 10:23:11 +01:00			`messages.`
final step in buildroot facelift 2004-10-09 08:13:40 +02:00
gettext: convert to autotools-package Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Tested-by: "Yann E. MORIN" <yann.morin.1998@free.fr> [yann.morin.1998@free.fr: add license info, build libintl if locales disabled] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> CC: Samuel Martin <s.martin49@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk> 2012-09-16 14:57:50 +02:00			`Only the libintl library will be installed in the`
gettext: remove libintl handling Now, the gettext package always: * install everything to the staging directory * install the libraries to the target directory Note that this commit removes BR2_PACKAGE_LIBINTL without updating the packages, it is done in a separate commit to ease the review process. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Tested-by: "Yann E. MORIN" <yann.morin.1998@free.fr> [yann.morin.1998@free.fr: keep BR2_PACKAGE_LIBINTL as blind option] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Tested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> CC: Samuel Martin <s.martin49@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk> 2012-09-16 14:57:48 +02:00			`target. The full gettext suite, including tools, will be`
			`installed in the staging directory.`

merge help descriptions written by Tom Cameron 2004-12-24 10:23:11 +01:00			`http://www.gnu.org/software/gettext/`
add option to select target installation per case 0000519 2006-01-25 18:47:03 +01: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 "gettext needs a toolchain w/ wchar"`
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_NEEDS_GETTEXT`
			`depends on !BR2_USE_WCHAR`