warning about GNU make extension with automake 1.10

Hi, I upgraded automake from 1.9.6 to 1.0 and get some warnings about make-rules which are GNU make extensions. I would like to remove the warnings. One warning is about: %.cpp: %.h %.ui $(UIC) -o $@ -i $^ gives ... `%'-style pattern rules are a GNU make extension and another

automake and DualCore

Hi, do Makefiles created from automake benefit from dualcore CPUs and is the build process speeded up ? Are there any measurement data available ? (Background is that I plan to buy a new PC and would like to know if it is worthwhile to consider such a system.) Regards, Thomas --

Re: makeinfo problem

Am Thu, 30 Mar 2006 10:41:07 +0200 schrieb Stepan Kasal [EMAIL PROTECTED]: Hello, a quick answer, you might get a better one from Karl, the maintainer. which version of makeinfo introduced HTML support ? I think we have to check in configure if the makeinfo tool is able the handle

Re: makeinfo problem

Hello Stepan, Am Thu, 30 Mar 2006 11:32:42 +0200 schrieb Stepan Kasal [EMAIL PROTECTED]: Hello Thomas, On Thu, Mar 30, 2006 at 11:05:22AM +0200, Thomas Porschberg wrote: Am Thu, 30 Mar 2006 10:41:07 +0200 schrieb Stepan Kasal [EMAIL PROTECTED]: a quick answer, actually, my answer

makeinfo problem

Hi, in our project(auto[make/conf] based) we introduced texinfo format for documentation (in favor of our old static HTML doc). We create HTML files from texi files which are integrated in our GUI application. The directory structure looks like: project-root/doc/help/*.texi in project-root/doc

Re: output directory of generated files

Am Tue, 28 Mar 2006 15:36:36 +0200 schrieb Stepan Kasal [EMAIL PROTECTED]: Hello, On Thu, Mar 09, 2006 at 02:48:13PM +0100, Thomas Porschberg wrote: %.qm: %.ts $(PROG1) $ foo.h: foo.qm $(top_srcdir)/utils/PROG2 $ $@ ... PROG2 expected foo.qm now in BUILDDIR/src

output directory of generated files

Hi, we have the following project structure and a file foo.ts: project/ +--src/foo.ts | | +--utils/PROG2 The goal is 1) to translate foo.ts to foo.qm (with an external program, say PROG1) 2) to create a header file from the created foo.qm (with another helper script

Re: best aclocal include practice wanted

Am Sat, 04 Mar 2006 16:43:37 -0500 schrieb Braden McDaniel [EMAIL PROTECTED]: On Sat, 2006-03-04 at 19:52 +0100, Thomas Porschberg wrote: what is the recommended way to include project-written m4 macros ? I include the macros in project-root/config/m4 and call in autogen.sh aclocal -I

best aclocal include practice wanted

Hi, what is the recommended way to include project-written m4 macros ? I include the macros in project-root/config/m4 and call in autogen.sh aclocal -I config/m4 The config directory itself is configured in configure.ac with AC_CONFIG_AUX_DIR(config). Is there something wrong with this

question regarding EXTRA_DIST

Hi, I have a problem with the EXTRA_DIST target from Makefile.am. In the project we list dirs an files there. But some files are not included in the distribution when built with make dist. E.g. we have files like BUGS, LICENSE, some header/source files included and they do not appear in the

Re: question regarding EXTRA_DIST

Sorry for my posting. One missing backslash caused my error... Thomas On Mon, Jan 30, 2006 at 09:43:33AM +0100, Ralf Wildenhues wrote: Hi Thomas, * Thomas Porschberg wrote on Mon, Jan 30, 2006 at 09:39:01AM CET: I have a problem with the EXTRA_DIST target from Makefile.am

Re: build paths and generated sources

Execellent, exactly what I was looking for. On Mon, 30 Jan 2006 00:36:46 +0100 Andreas Schwab [EMAIL PROTECTED] wrote: Thomas Porschberg [EMAIL PROTECTED] writes: %.cpp %.h: %.ui @UIC@ -o $(:%.ui=%.h) $ @UIC@ -i $(:%.ui=%.h) -o $(:%.ui=%.cpp) $ You should not use

build paths and generated sources

Hi, we run automake (and autoconf,libtool) in a project which uses the QT library. Programming with QT involves to generate *cpp,*h from so called *ui files and *moc files from header files. The way we do this in Makefile.am is as follows: BUILT_SOURCES = here are all generated moc and