Once I sent the same patch on June 8, but I have not had any response yet. So let me send it again. If it was/is rejected, please let me know so that I won't inadvertently bother you again with it. (On the same day, I sent another patch for another configure.ac. Perhaps, this was confusing...)
The patch is made against core/base/configure.ac in the CVS of June 18.
The patch adds the options --with-ffcall-include=PATH and --with-ffcall- library=PATH to the script configure. The naming follows the standard and thus explains what they do.
I hope these options are useful for those who have installed the ffcall library in nonstandard places such as /usr/local/lib, /opt/lib etc.
Regards, Kazunobu Kuriyama
2003-06-18 Kazunobu Kuriyama <[EMAIL PROTECTED]>
* configure.ac: Add --with--ffcall-include=PATH and
--with-ffcall-library=PATH options
--- configure.ac 2003-06-18 13:57:50.000000000 +0900
+++ configure.ac.rev 2003-06-18 13:58:03.000000000 +0900
@@ -860,6 +860,22 @@
[ --disable-do Compile even if DO-dependencies are not met],,
enable_do=yes)
+AC_ARG_WITH(ffcall-include,
+ [ --with-ffcall-include=PATH include path for ffcall headers],
+ ffcall_incdir="$withval", ffcall_incdir="no")
+if test ${ffcall_incdir} != "no"; then
+ ffcall_check_lib_save_cppflags="$CPPFLAGS"
+ CPPFLAGS="-I${ffcall_incdir} $CPPFLAGS"
+fi
+
+AC_ARG_WITH(ffcall-library,
+ [ --with-ffcall-library=PATH library path for ffcall libraries],
+ ffcall_libdir="$withval", ffcall_libdir="no")
+if test ${ffcall_libdir} != "no"; then
+ ffcall_check_lib_save_libs="$LIBS"
+ LIBS="-L${ffcall_libdir} $LIBS"
+fi
+
AC_CHECK_HEADER(ffi.h, , enable_libffi=no)
AC_MSG_CHECKING("for forwarding callback in runtime")
_______________________________________________ Bug-gnustep mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gnustep
