forked from enlightenment/efl
efl: fix a neon build break.
We found a some build break problem due to a build system. In efl configuration, our efl configure enables neon if it's available, but neon gonna partially turned off on evas compilation if the build system has a non neon CFLAG option (ie, mfpu=vfpv..). In the end, neon is partially enabled and it turns out a build break. It's non-sense but we can't allow this breakage. There is no way to ignore build system option nor override our neon option perfectly, so, Let efl package ruled by build system overall.
This commit is contained in:
parent
d458101a41
commit
77d2e0cb95
|
@ -593,7 +593,7 @@ case $host_cpu in
|
|||
build_cpu_neon="yes"
|
||||
AC_MSG_CHECKING([whether to use NEON instructions])
|
||||
CFLAGS_save="${CFLAGS}"
|
||||
CFLAGS="${CFLAGS} -mfpu=neon -ftree-vectorize"
|
||||
CFLAGS="-mfpu=neon -ftree-vectorize ${CFLAGS}"
|
||||
AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[#include <arm_neon.h>]], [[asm volatile ("vqadd.u8 d0, d1, d0\n")]])],[
|
||||
AC_MSG_RESULT([yes])
|
||||
AC_DEFINE([BUILD_NEON], [1], [Build NEON Code])
|
||||
|
|
Loading…
Reference in New Issue