50dfaef6ec
The basic rule for a package is to have its options named after the package name. There is no reason this should not also be the case for virtual packages. Besides, this will allow us to switch luainterpreter to use the soon-to-be-introduced virtual-package infrastructure. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Eric Le Bihan <eric.le.bihan.dev@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Thomas De Schampheleire <patrickdepinguin@gmail.com> Cc: Mike Zick <minimod@morethan.org> Cc: Francois Perrad <fperrad@gmail.com> Reviewed-by: Samuel Martin <s.martin49@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
15 lines
543 B
Plaintext
15 lines
543 B
Plaintext
config BR2_PACKAGE_LUAPOSIX
|
|
bool "luaposix"
|
|
depends on BR2_PACKAGE_HAS_LUAINTERPRETER
|
|
select BR2_PACKAGE_LUABITOP if BR2_PACKAGE_LUA_5_1
|
|
# LuaBitOp is already included in LuaJIT
|
|
help
|
|
luaposix is a POSIX binding, including curses, for Lua 5.1
|
|
and 5.2; Like most libraries it simply binds to C APIs on
|
|
the underlying system, so it won't work on a non-POSIX
|
|
system. However, it does try to detect the level of POSIX
|
|
conformance of the underlying system and bind only available
|
|
APIs
|
|
|
|
https://github.com/luaposix/luaposix
|