Small warning, automake 1.10 incompatible change in DEFAULT_INCLUDES

2007-11-09 Thread Kent Boortz
Hi, Just something that I had to do a work around for in our build, that others might be hit by as well. In case you have several headers with the same name in your source tree you might get problems from that in automake 1.10 the default header search order will differ a bit if doing a build in

How to install only derived file, not its .in?

2007-11-09 Thread Brad Larsen
Hi list, I have a project that requires some shell scripts to be built from .in files (to fill in some path variables). To do this substitution, I followed the directions in section 4.7.2 of the autoconf manual. Basically, use sed to replace @variable@ with its expansion from the generat

Re: How to install only derived file, not its .in?

2007-11-09 Thread Ralf Wildenhues
Hello Brad, * Brad Larsen wrote on Fri, Nov 09, 2007 at 05:44:37PM CET: > In the distribution, I want to include only the .in files and not the > derived files. When installing, I want to install only the derived files > and not the .in files. So far my Makefile.am looks like this: > > [snip]

Re: How to install only derived file, not its .in?

2007-11-09 Thread Brad Larsen
On Fri, 09 Nov 2007 11:50:56 -0500, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: Hi Ralf, Hello Brad, * Brad Larsen wrote on Fri, Nov 09, 2007 at 05:44:37PM CET: In the distribution, I want to include only the .in files and not the derived files. When installing, I want to install only the d

How best to incorporate -Wl,--whole-archives with _PROGRAMS

2007-11-09 Thread Kamaljit Singh
I am trying to build a .so (without libtool) but instead using the _PROGRAMS. If I want to use -Wl,--whole-archives ... -Wl,--no-whole-archives in the _LDLIBS it barfs and if I use it in _LDFLAGS then it doesnt get into the dependencies, unless I explicitly put it. Any ideas on a better mechanism

Re: How to install only derived file, not its .in?

2007-11-09 Thread Ralf Wildenhues
* Brad Larsen wrote on Fri, Nov 09, 2007 at 06:11:11PM CET: > > I guess I wasn't clear enough. In section 4.7.2 of the autoconf manual, > it says: [...] > That's why I'm having the makefile (which autoconf generates) do the > substitution rather than calling AC_OUTPUT_FILES([runme]) or > AC

Re: Small warning, automake 1.10 incompatible change in DEFAULT_INCLUDES

2007-11-09 Thread Ralf Wildenhues
Hello Kent, Thank you for the report. * Kent Boortz wrote on Fri, Nov 09, 2007 at 04:27:38PM CET: > > In case you have several headers with the same name in your source > tree you might get problems from that in automake 1.10 the default > header search order will differ a bit if doing a build i