Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
> jtc> I've since learned that the problem isn't in autoconf, but in
> jtc> automake.
>
> It was. More than one year ago.
Perhaps I'm misunderstanding your response, but it seems like you're
saying that there was a bug which has long been fixed.
>>> "J" == J T Conklin <[EMAIL PROTECTED]> writes:
J> I've since learned that the problem isn't in autoconf, but in
J> automake.
It was. More than one year ago.
--
Alexandre Duret-Lutz
Hi Stepan,
The solution is to not list the file in the list of files to be configured.
Instead, in your Makefile.am:
mumble-sh.in : $(mumble_PREDECESSORS)
create-mumble-sh-in
mumble.sh : mumble-sh.in
$(SHELL) $(top_builddir)/config.status --file mumble.sh:mumble-sh.in
Someon
Bruce Korb <[EMAIL PROTECTED]> writes:
>> However, if I add foo.pc to AC_CONFIG_FILES, autoconf complains that
>> foo.pc.in does not exist (which it does not). However, if I omit it,
>> foo.pc.in is generated at configure-time, but foo.pc is not.
>>
>> Does anyone have any clue how to use this ma
Stepan Kasal <[EMAIL PROTECTED]> writes:
> On Thu, Dec 30, 2004 at 08:19:41PM -0800, J.T. Conklin wrote:
>> However, if I add foo.pc to AC_CONFIG_FILES, autoconf complains that
>> foo.pc.in does not exist (which it does not). However, if I omit it,
>> foo.pc.in is generated at configure-time, but
Konstantin Osipov wrote:
How do people work around the lack of 'include' directive of ctags?
I put this in the Makefile.am in the project's src subdir:
tags:
find . -name TAGS -o -name tags -exec rm {} \;
ctags `pwd`/*/*.cpp `pwd`/*/*.h
find . -type d -mindepth 1 -exec ln tags {} \;
cta
