gitolite/buildrootschalter
gitolite
/
buildrootschalter
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
buildrootschalter/package/pppd/Config.in

30 lines
616 B
Plaintext
Raw Normal View History

final step in buildroot facelift
2004-10-09 08:13:40 +02:00
config BR2_PACKAGE_PPPD
more help updates from Tom Cameron
2004-12-26 08:36:59 +01:00
bool "pppd"
pppd: needs mmu and shared objects The plugin infrastructure is based on shared objects so it won't build for static-only scenarios. And the daemon uses fork() so MMU is required. [Peter: move below suboptions] Signed-off-by: Axel Lin <axel.lin@ingics.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-09-30 11:18:47 +02:00
depends on !BR2_PREFER_STATIC_LIB
depends on BR2_USE_MMU
final step in buildroot facelift
2004-10-09 08:13:40 +02:00
help
more help updates from Tom Cameron
2004-12-26 08:36:59 +01:00
An implementation of the Point-to-point protocol.
final step in buildroot facelift
2004-10-09 08:13:40 +02:00
more help updates from Tom Cameron
2004-12-26 08:36:59 +01:00
http://www.samba.org/ppp/
Enable multilink PPP (no reason to disable it) Add configuration item to enable filtering (requires libpcap)
2009-02-19 06:31:05 +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_PPPD
Enable multilink PPP (no reason to disable it) Add configuration item to enable filtering (requires libpcap)
2009-02-19 06:31:05 +01:00
config BR2_PACKAGE_PPPD_FILTER
select BR2_PACKAGE_LIBPCAP
bool "filtering"
help
Packet filtering abilities for pppd. If enabled,
the pppd active-filter and pass-filter options
are available.
pppd: convert to gentargets, properly add radius support, fix l2tp for 2.6.35 headers Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-10-06 19:34:47 +02:00
config BR2_PACKAGE_PPPD_RADIUS
bool "radius"
help
Install RADIUS support for pppd
pppd: needs mmu and shared objects The plugin infrastructure is based on shared objects so it won't build for static-only scenarios. And the daemon uses fork() so MMU is required. [Peter: move below suboptions] Signed-off-by: Axel Lin <axel.lin@ingics.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-09-30 11:18:47 +02: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
endif
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 "pppd needs a toolchain w/ dynamic library"
pppd: needs mmu and shared objects The plugin infrastructure is based on shared objects so it won't build for static-only scenarios. And the daemon uses fork() so MMU is required. [Peter: move below suboptions] Signed-off-by: Axel Lin <axel.lin@ingics.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-09-30 11:18:47 +02:00
depends on BR2_PREFER_STATIC_LIB
depends on BR2_USE_MMU