Angus Leeming <[EMAIL PROTECTED]> writes:
| Jean-Marc and other m4 wizards,
>
| I have been trying to make sense of the configure magic stuff. Black magic
| more like. Yuch.
>
| Am I right to say that the entire test should be wrapped up so:
>
| dnl Check whether to use the the image loading facilities of the gui library.
| AC_DEFUN(LYX_USE_GUI_IMAGE_LOADER,
| [AC_MSG_CHECKING([whether to use the the gui library to load images])
I guess you should write a test for each of the guis possible.
that means for now you only write.
LYX_USE_XFORMS_GUI_LOADER and this should only be called in the
xforms part of the case in configure.in.
| This declares the test. How do I invoke it?
>
| Moving on...
>
| Are we meant to use LYX_CHECK_DECL? I see that it is defined, but noone else
| seems to use it. What does it return? "yes"/"no"? Do these macros "return"
| anything or have I got the wrong end of the stick.
>
| I was imagining a test like:
>
| if test $lyx_use_frontend = "xforms" -a
| LYX_CHECK_DECL(flimage_dup, FORMS_H_LOCATION) = "yes" -a
| LYX_CHECK_DECL(flimage_to_pixmap, FORMS_H_LOCATION) = "yes"
Why can't you use CHECK_FUNC ?
Do you really have to check that it is declared?
>
| Angus
>
| ps why do you keep shoving an "x" on both sides of a conditional
| if test x$some_test = xyes; then ...
imagine $some_test to be ""
without the x's you would have "if test = yes ; then"
with you get "if test x = xyes ; then"
--
Lgb
