Keeping source directory structure

Hi all, I have been using automake for a while now, however I recently came across an issue i haven't had to worry about before, which is having duplicate named source files under different directory structures producing conflicting object files. Say i have a source directory structure like:

Re: DISTCLEANFILES with SUBDIR directories

I suppose you can try adding DIST_SUBDIRS = . $(subdirs) but probably you will have to make the latter $(subdirs_without_gcc) and then take care that 'make dist' is handled correctly, by writing a suitable dist-local rule or so (untested). Hope that helps. Thanks, I will give that a

DISTCLEANFILES with SUBDIR directories

Hi all, I have a project using automake and I want to ensure that the distclean target removes a directory that is listed conditionally in the SUBDIRS variable. Is this possible to do this without the distclean target being performed recursively inside the sub directory first? My Makefile.am

Disable make distcheck --help and --version checks

The subject says it all. I have a special example project that i would like to ensure when i use the distcheck target it does NOT check that some or all of the installed applications provide --help or --version. How can i do this? Some people are likely to want to argue that it is important

Re: Disable make distcheck --help and --version checks

These paragraphs say it all: http://www.gnu.org/software/automake/manual/html_node/Options.html#index-Options_002c-_0040option_007bstd_002doptions_007d-854 Thanks. That works exactly as i need. I am surprised google didn't find this paragraph when i searched with various options. I also

Re: Modify Output to look like Linux Kernel

Thomas Dickey wrote: On Thu, 5 Jul 2007, Bob Friesenhahn wrote: A big difference between Automake projects and building the Linux kernel is that building the linux kernel is practically assured to succeed where as building Automake projects may fail and require correction by the end user

Overwriting targets.

Hi all, I have a project using autotools that also has sub-projects. http://edoc.sourceforge.net/ Basically this project requires patched versions of the GCC and doxygen projects. To make life easy for the person compiling from sources i get my configure script to unpack the sources for these

Installation dirs in code

Hi all, I was wondering if there exists a kindof standard way to obtain final installation directory information within code being compiled when using autotools? E.g. I have a program that requires a configuration file that will usually go into the ${prefix}/etc as given by $sysconfdir. So

Re: Installation dirs in code

Brian Dessent wrote: Instead of using an absolute path, you can use a relative path, which makes the binary relocatable. For Win32, this means you can avoid completely the hassle of converting between native and posix-emulated (aka MSYS/Cygwin) paths. It also means the user can install your

Re: Installation dirs in code

Brian Dessent wrote: Brendon Costa wrote: However all these methods of obtaining the directory information seems to fall down for libraries. Huh? Did you read the same email by Bruce Haible that I did? Because it doesn't fall down at all. On Win32 GetModuleFilename works just

Re: Reducing verbosity of automake

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks for that response. I agree fully with your evaluation of the problem at hand with overly verbose log files. I was unaware of that application you mentioned, I may have a look for it later. Thanks again. Due to various reasons, I have decided

Re: Reducing verbosity of automake

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm afraid that I misinterpreted what the original poster wanted to be a way of tidying output on a single development system, and not for all variations of platforms where the build process would be run. The filter would be a quick way of

Reducing verbosity of automake

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi All, I have just recently started using automake and have been attempting to port over a system that uses jam to now use automake. While doing this i have come across a feature i seem unable to find within automake. I have searched the

Re: Reducing verbosity of automake

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ralf Wildenhues wrote: [ I assume you want Cc:s to both addresses? ] Yep. Thanks. By the way. Thanks for the reply. I couldn't believe it was so fast :-) All patches I've seen add quite a bit of bloat to Makefile.in's, for dubious value

Re: Reducing verbosity of automake

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Well i had a small look at the proposal i made last night, and it seems that it is not possible to achieve what i was saying entirely from autoconf by setting the command variables to be prefixed with the script command. Reasons include: 1)