Re: AM_CFLAGS usage

2006-06-12 Thread Ralf Wildenhues
Hello Norbert, * Norbert Sendetzky wrote on Mon, Jun 12, 2006 at 06:42:15PM CEST: > > Ehm, where do I find the documentation to config.site? Oh, sorry, I forgot to mention that config.site is an Autoconf feature. Its manual has the information. (The current manual isn't online, but let's hope t

Re: AM_CFLAGS usage

2006-06-12 Thread Norbert Sendetzky
On Monday 12 June 2006 12:53, Ralf Wildenhues wrote: > : ${CFLAGS='-Wall -ansi -pedantic'} > > before AC_PROG_CC in configure.ac. Users with non-GCC compilers won't > like you because they will have to set CFLAGS to override this, and > users (with any kind of compiler) won't like you because yo

Re: AM_CFLAGS usage

2006-06-12 Thread Ralf Wildenhues
* Norbert Sendetzky wrote on Mon, Jun 12, 2006 at 11:06:36AM CEST: > On Monday 12 June 2006 10:28, Ralf Corsepius wrote: > > > > Note though that > > > > -Wall -ansi -pedantic > > > > > > > > is pretty GCC specific, and will make many other compilers barf > > > > heavily. So if your package targ

Re: AM_CFLAGS usage

2006-06-12 Thread Norbert Sendetzky
On Monday 12 June 2006 10:28, Ralf Corsepius wrote: > > > Note though that > > > -Wall -ansi -pedantic > > > > > > is pretty GCC specific, and will make many other compilers barf > > > heavily. So if your package targets portability, it'd be nice > > > to allow your users to override these flags

Re: AM_CFLAGS usage

2006-06-12 Thread Ralf Corsepius
On Mon, 2006-06-12 at 10:16 +0200, Norbert Sendetzky wrote: > Hi Ralf > > > > Norbert Sendetzky wrote: > > > > This works, but as soon as I move AM_CFLAGS to the Makefile.am in the > > > > parent directory, they aren't set any more. Is this the way it was > > > > intended and the only way to set t

Re: AM_CFLAGS usage

2006-06-12 Thread Norbert Sendetzky
Hi Ralf > > Norbert Sendetzky wrote: > > > This works, but as soon as I move AM_CFLAGS to the Makefile.am in the > > > parent directory, they aren't set any more. Is this the way it was > > > intended and the only way to set them globally is to AC_SUBST them or > > > is there something wrong in my

Re: AM_CFLAGS usage

2006-06-11 Thread Ralf Wildenhues
Hello Norbert, Marc, > Norbert Sendetzky wrote: > > > > This works, but as soon as I move AM_CFLAGS to the Makefile.am in the > > parent > > directory, they aren't set any more. Is this the way it was intended and > > the > > only way to set them globally is to AC_SUBST them or is there someth

Re: AM_CFLAGS usage

2006-06-11 Thread Marc Alff
Hi Norbert Sendetzky wrote: > Hi all > > I've tried to set the C flags for my package globally and used AM_CLFAGS for > this. Unfortunately AM_CLFAGS is only honored if it is defined in the same > Makefile.am. > > AM_CFLAGS = -Wall -ansi -pedantic > pkglib_LTLIBRARIES = libmysqlbackend.la > li

AM_CFLAGS usage

2006-06-11 Thread Norbert Sendetzky
Hi all I've tried to set the C flags for my package globally and used AM_CLFAGS for this. Unfortunately AM_CLFAGS is only honored if it is defined in the same Makefile.am. AM_CFLAGS = -Wall -ansi -pedantic pkglib_LTLIBRARIES = libmysqlbackend.la libmysqlbackend_la_SOURCES = mysqlbackend.c libmy

AM_CFLAGS usage

2006-06-10 Thread Norbert Sendetzky
Hi all I've tried to set the C flags for my package globally and used AM_CLFAGS for this. Unfortunately AM_CLFAGS is only honored if it is defined in the same Makefile.am. AM_CFLAGS = -Wall -ansi -pedantic pkglib_LTLIBRARIES = libmysqlbackend.la libmysqlbackend_la_SOURCES = mysqlbackend.c libmy