Hi Ibukun,
I've updated entrance this week and I look into configure.in.
There are 2 tests: one that is generic and clean :
AC_ARG_WITH(ecore,
[ --with-ecore=DIR use ecore in <DIR>],
[ CFLAGS="$CFLAGS -I$withval/include"
LIBS="-L$withval/lib $LIBS"])
And one that doesn't help much than the first and that fails:
have_ecore=no
AC_CHECK_HEADER(Ecore.h,,
AC_MSG_ERROR([Ecore.h not found! Have you installed Ecore?]))
AC_CHECK_LIB(ecore, ecore_list_new,
[have_ecore=yes],
AC_MSG_ERROR([Ecore check failed! Make sure you have the latest version of
Ecore installed.]))
Is this really needed ? If you zap this test entrance could be built with a very
simple scheme (ecore-config in PATH). Whereas with this test I must insert in my
generic scripts for Lunar Linux a workaround line :
export CPPFLAGS="$CPPFLAGS -I$MODULE_PREFIX/include"
Best regards,
Michel
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
