Re: maude_ vs LIBRARY_

Hello William, * William Pursell wrote on Sun, Nov 23, 2008 at 10:05:06AM CET: In the documentation, generic items appear as maude_PRIMARY and LIBRARY_PRIMARY. This strikes me as inconsistent. I suggest changing, eg, LIBRARY_LIBTOOLFLAGS to libmaude_LIBTOOLFLAGS. Well, one point of using

Re: maude_ vs LIBRARY_

Ralf Wildenhues wrote: * William Pursell wrote on Sun, Nov 23, 2008 at 10:05:06AM CET: I suggest changing, eg, LIBRARY_LIBTOOLFLAGS to libmaude_LIBTOOLFLAGS. Unless we can come up with a definite improvement in consistency, I wouldn't want to change things. What about changing

Re: maude_ vs LIBRARY_

* William Pursell wrote on Sun, Nov 23, 2008 at 03:04:36PM CET: Ralf Wildenhues wrote: * William Pursell wrote on Sun, Nov 23, 2008 at 10:05:06AM CET: I suggest changing, eg, LIBRARY_LIBTOOLFLAGS to libmaude_LIBTOOLFLAGS. Unless we can come up with a definite improvement in consistency, I

[PATCH] documentation errors

Ralf, here's another set of corrections to the documentation. There was a question I had that I notated by adding comments to the .texi file which appears in the patch below re: AM_PROG_CC_C_O. The documentation claims that one must invoke AM_PROG_CC_C_O in order to use program_CFLAGS, but I

Re: [PATCH] documentation errors

Hello William, * William Pursell wrote on Sun, Nov 23, 2008 at 06:18:47PM CET: here's another set of corrections to the documentation. Thanks. There was a question I had that I notated by adding comments to the .texi file which appears in the patch below re: AM_PROG_CC_C_O. The