Currently in Buildroot we have a BR2_PACKAGE_QT_ARCH_SUPPORTS_WEBKIT variable indicating which architectures support Qt Webkit. We also make Qt Script depending on that variable, so we are assuming that Qt Script is supported for exactly the same architectures which support Qt Webkit, and that's not true. For instance, Qt Webkit is not supported for MIPS64 when using the n32 ABI, but Qt Script is actually supported. So, if we make BR2_PACKAGE_QT_ARCH_SUPPORTS_WEBKIT depending on !BR2_MIPS_NABI32 we will also disable Qt Script, because as I said before, Qt Script depends on BR2_PACKAGE_QT_ARCH_SUPPORTS_WEBKIT, and we don't want that because Qt Script works. We fix this by creating another variable called BR2_PACKAGE_QT_ARCH_SUPPORTS_SCRIPT to state which architectures support Qt Script, so now we can differentiate them from the ones supporting Qt Webkit. Related: http://lists.busybox.net/pipermail/buildroot/2014-November/112605.html Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
18 lines
679 B
Plaintext
18 lines
679 B
Plaintext
config BR2_PACKAGE_GRANTLEE
|
|
bool "grantlee"
|
|
depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL # Qt Script
|
|
depends on (BR2_PACKAGE_QT_ARCH_SUPPORTS_SCRIPT && BR2_PACKAGE_QT) || BR2_PACKAGE_QT5
|
|
select BR2_PACKAGE_QT_STL if BR2_PACKAGE_QT
|
|
select BR2_PACKAGE_QT_SCRIPT if BR2_PACKAGE_QT
|
|
select BR2_PACKAGE_QT_GUI_MODULE if BR2_PACKAGE_QT
|
|
select BR2_PACKAGE_QT5SCRIPT if BR2_PACKAGE_QT5
|
|
select BR2_PACKAGE_QT5BASE_GUI if BR2_PACKAGE_QT5
|
|
help
|
|
Qt implementation of the Django template framework
|
|
|
|
http://www.grantlee.org
|
|
|
|
comment "grantlee needs a toolchain with NPTL"
|
|
depends on !BR2_TOOLCHAIN_HAS_THREADS_NPTL
|
|
depends on BR2_PACKAGE_QT_ARCH_SUPPORTS_SCRIPT || BR2_PACKAGE_QT5
|