Re: probing for compiler attributes?

2007-08-08 Thread Luca Dionisi
On 8/8/07, John W. Eaton <[EMAIL PROTECTED]> wrote: > On 7-Aug-2007, Joshua Hoblitt wrote: > > | Is there a pre-canned AC macro or other reliable means of testing for > | compiler attributes? > | > | I have an awful lot of code that looks something like this: > | > | void *myfunc(char *myvar

A General-Purpose Configuration Macro

2007-08-08 Thread Eric Lemings
Greetings, I need to write a general-purpose M4 macro for Autoconf that reads in a simple C++ source file that is assumed to make a simple configuration check (as opposed to doing the same directly in M4) after which the M4 macro compiles, links, and executes (yeah I'm throwing cross-compiling ou

test in a m4 macro and variable created from pushdef

2007-08-08 Thread Vincent Torri
hey I have written that code in my configure.ac: if test "x${use_pcf_driver}" = "xyes"; then AC_MSG_NOTICE([Creating pcf driver...]) rm -f src/lib/drv_pcf.c echo "/* CAUTION! NEVER EDIT THIS FILE */" > src/lib/drv_pcf.c sed 's/bdf/pcf/g' src/lib/drv_bdf.c | sed 's/BDF

Re: test in a m4 macro and variable created from pushdef

2007-08-08 Thread Andreas Schwab
Vincent Torri <[EMAIL PROTECTED]> writes: > AC_DEFUN([AS_CREATE_DRIVER], [ > > pushdef([UP], translit([$1], [a-z], [A-Z]))dnl > pushdef([DOWN], translit([$1], [A-Z], [a-z]))dnl > > pushdef([SRCUP], translit([$2], [a-z], [A-Z]))dnl > pushdef([SRCDOWN], translit([$2], [A-Z], [a-z]))dnl > > if test "

Re: test in a m4 macro and variable created from pushdef

2007-08-08 Thread Benoit SIGOURE
On Aug 8, 2007, at 7:03 PM, Vincent Torri wrote: if test "x${use_pcf_driver}" = "xyes"; then AC_MSG_NOTICE([Creating pcf driver...]) rm -f src/lib/drv_pcf.c echo "/* CAUTION! NEVER EDIT THIS FILE */" > src/ lib/drv_pcf.c sed 's/bdf/pcf/g' src/lib/drv_bdf.c | sed 's/BDF

Re: probing for compiler attributes?

2007-08-08 Thread Joshua Hoblitt
On Wed, Aug 08, 2007 at 10:16:18AM +0200, Luca Dionisi wrote: > On 8/8/07, John W. Eaton <[EMAIL PROTECTED]> wrote: > > On 7-Aug-2007, Joshua Hoblitt wrote: > > > > | Is there a pre-canned AC macro or other reliable means of testing for > > | compiler attributes? > > | > > | I have an awful lot of

Re: probing for compiler attributes?

2007-08-08 Thread Joshua Hoblitt
On Tue, Aug 07, 2007 at 08:43:54PM -0400, John W. Eaton wrote: > Ugh. Don't do it like that. Instead, write something like > > your-config-header.h: > > #ifdef __GNUC__ > #define ATTR_MALLOC __attribute__((malloc)) > #else > #define ATTR_MALLOC > #endif > > an

Whys is `make dist` packaging gmo files?

2007-08-08 Thread Andrew Smith
Hi I inherited a project that uses autotools. It didn't have any .po files when I got it but I added a couple, so now there is this in configure.in: dnl Add the languages which your application supports here. ALL_LINGUAS="sv zh_TW" AM_GLIB_GNU_GETTEXT They compile and install and run fine. Bu

Re: test in a m4 macro and variable created from pushdef

2007-08-08 Thread Vincent Torri
On Wed, 8 Aug 2007, Andreas Schwab wrote: if test "x${use_]DOWN[_driver}" = "xyes"; then The outer pairs of quotes are removed before the AC_DEFUN macro is called, thus the argument does not contain the word DOWN any more, but rather use_DOWN_driver. You need to fix the quoting that they su