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

17 lines
288 B
Plaintext
Raw Normal View History

package/libidn: Add a new package (required by later WebKits...) GNU Libidn is a fully documented implementation of the Stringprep, Punycode and IDNA specifications. Libidn's purpose is to encode and decode internationalized domain names. The native C, C# and Java libraries are available under the GNU Lesser General Public License version 2.1 or later. Not quite sure I've put it in the correct menu but it will work. Signed-off-by: Daniel Laird <daniel.j.laird@nxp.com>
2009-01-13 17:36:16 +01:00
config BR2_PACKAGE_LIBIDN
bool "libidn"
help
libidn: fix build with config.cache, autoconf and emacs libidn contains a few elisp files, and it's configure script checks for emacs to know if it should install them. This is not important for BR as we don't have emacs, but configure fails if it's available on the host, config.cache is used and autoconf has already been used as that loads EMACS="no" into the cache. Fix it by also setting EMACS="no" here. At the same time, fix up trailing spaces in Config.in. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-06-05 08:10:13 +02:00
Libidn's purpose is to encode and decode internationalized
domain names.
package/libidn: Add a new package (required by later WebKits...) GNU Libidn is a fully documented implementation of the Stringprep, Punycode and IDNA specifications. Libidn's purpose is to encode and decode internationalized domain names. The native C, C# and Java libraries are available under the GNU Lesser General Public License version 2.1 or later. Not quite sure I've put it in the correct menu but it will work. Signed-off-by: Daniel Laird <daniel.j.laird@nxp.com>
2009-01-13 17:36:16 +01:00
package/libidn/Config.in: Fix layout of text as per coding guidelines. Update description to match required -> help Description Empty line Homepage Signed-off-by: Daniel Laird <daniel.j.laird@nxp.com>
2009-01-14 09:31:41 +01:00
http://www.gnu.org/software/libidn/
libidn: Update Config.in to fulfill LIBIDN_BINARY Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2009-11-16 13:33:16 +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_LIBIDN
libidn: Update Config.in to fulfill LIBIDN_BINARY Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2009-11-16 13:33:16 +01:00
config BR2_PACKAGE_LIBIDN_BINARY
bool "idn binary"
help
Install idn command line tool
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
Reference in New Issue Copy Permalink