kumquat-buildroot/package/libcurl/Config.in

config BR2_PACKAGE_LIBCURL
	bool "libcurl"
	help
	  cURL is a tool for getting files from FTP, HTTP, Gopher, Telnet,
	  and Dict servers, using any of the supported protocols.

	  http://curl.haxx.se/

if BR2_PACKAGE_LIBCURL

config BR2_PACKAGE_CURL
	bool "curl binary"
	help
	  Install curl binary as well

config BR2_PACKAGE_LIBCURL_VERBOSE
	bool "enable verbose strings"
	help
	  Enable verbose text strings

endif
Add new packages. 2007-05-07 05:58:30 +02:00			`config BR2_PACKAGE_LIBCURL`
			`bool "libcurl"`
			`help`
			`cURL is a tool for getting files from FTP, HTTP, Gopher, Telnet,`
			`and Dict servers, using any of the supported protocols.`

curl: fix homepage cURL's homepage is curl.haxx.se and not curl.haxx.nu Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com> 2013-11-06 11:21:34 +01:00			`http://curl.haxx.se/`
curl: convert to Makefile.autotools.in format, bump version 2008-12-28 14:50:53 +01:00
Config.in files: use if/endif instead of 'depends on' for main symbol In the Config.in file of package foo, it often happens that there are other symbols besides BR2_PACKAGE_FOO. Typically, these symbols only make sense when foo itself is enabled. There are two ways to express this: with depends on BR2_PACKAGE_FOO in each extra symbol, or with if BR2_PACKAGE_FOO ... endif around the entire set of extra symbols. The if/endif approach avoids the repetition of 'depends on' statements on multiple symbols, so this is clearly preferred. But even when there is only one extra symbol, if/endif is a more logical choice: - it is future-proof for when extra symbols are added - it allows to have just one strategy instead of two (less confusion) This patch modifies the Config.in files accordingly. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> 2013-12-20 22:31:30 +01:00			`if BR2_PACKAGE_LIBCURL`

curl: convert to Makefile.autotools.in format, bump version 2008-12-28 14:50:53 +01:00			`config BR2_PACKAGE_CURL`
			`bool "curl binary"`
			`help`
			`Install curl binary as well`
Config.in files: use if/endif instead of 'depends on' for main symbol In the Config.in file of package foo, it often happens that there are other symbols besides BR2_PACKAGE_FOO. Typically, these symbols only make sense when foo itself is enabled. There are two ways to express this: with depends on BR2_PACKAGE_FOO in each extra symbol, or with if BR2_PACKAGE_FOO ... endif around the entire set of extra symbols. The if/endif approach avoids the repetition of 'depends on' statements on multiple symbols, so this is clearly preferred. But even when there is only one extra symbol, if/endif is a more logical choice: - it is future-proof for when extra symbols are added - it allows to have just one strategy instead of two (less confusion) This patch modifies the Config.in files accordingly. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> 2013-12-20 22:31:30 +01:00
libcurl: optional verbose strings config This patch enables a config to set --enable-verbose during the configuration of libcurl. The option is triggered by setting BR2_PACKAGE_LIBCURL_VERBOSE. Signed-off-by: Judd Meinders <judd.meinders@rockwellcollins.com> Signed-off-by: Matt Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> 2017-01-31 18:26:53 +01:00			`config BR2_PACKAGE_LIBCURL_VERBOSE`
			`bool "enable verbose strings"`
			`help`
			`Enable verbose text strings`

Config.in files: use if/endif instead of 'depends on' for main symbol In the Config.in file of package foo, it often happens that there are other symbols besides BR2_PACKAGE_FOO. Typically, these symbols only make sense when foo itself is enabled. There are two ways to express this: with depends on BR2_PACKAGE_FOO in each extra symbol, or with if BR2_PACKAGE_FOO ... endif around the entire set of extra symbols. The if/endif approach avoids the repetition of 'depends on' statements on multiple symbols, so this is clearly preferred. But even when there is only one extra symbol, if/endif is a more logical choice: - it is future-proof for when extra symbols are added - it allows to have just one strategy instead of two (less confusion) This patch modifies the Config.in files accordingly. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> 2013-12-20 22:31:30 +01:00			`endif`