Re: including autoconf paths in source

2008-12-11 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Monty Taylor on 12/11/2008 1:38 PM: > Hey all, > > I'm wondering if there is a best practice for getting paths such as > locaeldir or datadir into source code. Best practice is to use the Makefile to do the expansion into another file th

Re: including autoconf paths in source

2008-12-11 Thread Jan Engelhardt
On Thursday 2008-12-11 21:38, Monty Taylor wrote: >Hey all, > >I'm wondering if there is a best practice for getting paths such as >locaeldir or datadir into source code. As it stands now in the Makefile >I've got: > >prefix= /usr/local >datarootdir= ${prefix}/share >localedir = ${datarootdir}/lo

including autoconf paths in source

2008-12-11 Thread Monty Taylor
Hey all, I'm wondering if there is a best practice for getting paths such as locaeldir or datadir into source code. As it stands now in the Makefile I've got: prefix= /usr/local datarootdir= ${prefix}/share localedir = ${datarootdir}/locale To get localedir into a source file, I've got a section

RE: GNU Make Extensions

2008-12-11 Thread Bob Friesenhahn
On Thu, 11 Dec 2008, Duft Markus wrote: There is a philosophical stance that the software we develop is intended for the software users rather than the software developer. There is a problem if build behavior is different for the user than for the software developer. Build behaviour wouldn't c