* Steffen Dettmer wrote on Tue, Feb 02, 2010 at 01:44:50PM CET: > On Fri, Jan 29, 2010 at 11:39 PM, wrote: > > I think cscope can parse declarations as well; git Automake > > provides a 'make cscope' rule. > > stef...@raven:/tmp/steffen_exp/new-autotools/systest_exp # make cscope > make: *** No rule to make target `cscope'. Stop. > stef...@raven:/tmp/steffen_exp/new-autotools/systest_exp # grep -i scope Mak* > stef...@raven:/tmp/steffen_exp/new-autotools/systest_exp # head -1 Makefile > # Makefile.in generated by automake 1.11.1 from Makefile.am.
> What do I wrong? 1.11.1 is not git master. This feature will appear in the 1.12 release. > > I don't think either of those distinguish between functions > > that you also define and those that you don't define, but why > > should you declare functions from third parties? > > Typically, when the headers do not compile, clash, use wrong > types, are missing `const' qualifiers or generate warnings (if > files should not be changed, and only one or very very few > declarations of it are needed). > > But back to `make tags', how it is intended to be used, should > users have something like `export ETAGS_ARGS=--declarations' in > their ~/.profile? But this does not work (does not influence > $(ETAGS_ARGS)). You could use `make -e', but that has typically causes problems. > Is there something like `./configure ETAGS_ARGS=--declarations' > (which unfortunately does not work with autoconf-2.65)? Well, you could AC_SUBST([ETAGS_ARGS]) in your configure.ac, but then you'd require users of non-GNU make to set it already at configure time or use `make -e'. Cheers, Ralf
