Re: nodist_BUILT_SOURCES?

On 06/10/2010 11:10 AM, Ralf Wildenhues wrote: > Hello Monty, > > first of all, let's ditch the cross-post, this is an Automake question > (and the interested readers read both lists anyway). > > * Monty Taylor wrote on Thu, Jun 10, 2010 at 07:42:13PM CEST: >> How

nodist_BUILT_SOURCES?

Hey all, Potentially odd question... How would I accomplish something like what's in the subject? I have a source file that wants to be built before other files - so including it in BUILT_SOURCES does the right thing, but I do _not_ want to have it included in the dist tarball. I tried removing

Re: relinking error

On 03/05/2010 09:26 AM, Monty Taylor wrote: Hi! I've got an install-time re-linking error happening in two different projects now, and it's confusing me. ltmain.sh (GNU libtool) 2.2.6b automake (GNU automake) 1.11.1 The simple case where it's happening is in libcassan

relinking error

Hi! I've got an install-time re-linking error happening in two different projects now, and it's confusing me. ltmain.sh (GNU libtool) 2.2.6b automake (GNU automake) 1.11.1 The simple case where it's happening is in libcassandra. We have to lib_LTLIBRARIES defined, libgenthrift.la and libcass

registering outputted files for deletion

Hey all, I'm working on a macro which needs to output a file, and I'd like for that file to be deleted on make distclean. I'm trying to avoid AC_CONFIG_FILE in this case because I'm trying to make the macro self contained so that a user doesn't have a to add both the macro and a very very small .i

pod to man

Hey all, I have a build thing that I cannot for the life of me figure out a _good_ way to express. (I can express it with lots of copy and paste) I have several document source files, each ending in pod, which will each produce one more more man pages when run through pod2man. Simply, something l

32-bit/64-bit builds on Solaris

Hey all, I'm wondering if there is either an autotools feature I don't know about or a best practice, because what I'm doing right now feels dirty. Solaris on Sparc supports both 32 and 64 bit binaries, with builds defaulting to 32-bit. (Thanks backwards compatibility for proprietary software!) B

Re: odd aclocal/automake depends issue

Ralf Wildenhues wrote: > Hello Monty, > > * Monty Taylor wrote on Tue, Dec 23, 2008 at 04:48:30AM CET: >> First of all, the answer to my question is going to be "don't do that", >> but just in case it isn't... > > Nope, it isn't, AFAICS. >

Re: odd aclocal/automake depends issue

Ralf Wildenhues wrote: > Hello Monty, > > * Monty Taylor wrote on Tue, Dec 23, 2008 at 04:48:30AM CET: >> First of all, the answer to my question is going to be "don't do that", >> but just in case it isn't... > > Nope, it isn't, AFAICS. >

odd aclocal/automake depends issue

Hey all, First of all, the answer to my question is going to be "don't do that", but just in case it isn't... I'm working on a project which allows plugins (project==Drizzle... fork of MySQL, we have inherited the system from them). The plugin system is such that you can drop a directory into the

including autoconf paths in source

Hey all, I'm wondering if there is a best practice for getting paths such as locaeldir or datadir into source code. As it stands now in the Makefile I've got: prefix= /usr/local datarootdir= ${prefix}/share localedir = ${datarootdir}/locale To get localedir into a source file, I've got a section

Re: CFLAGS for one file?

Bernd Jendrissek wrote: > On Tue, Oct 28, 2008 at 12:24 PM, Monty Taylor <[EMAIL PROTECTED]> wrote: >> Is there a sensible way to set CFLAGS for a single file? Right now I'm >> breaking it out into an LT convenience lib that gets linked in to the >> final output...

CFLAGS for one file?

Hi! Is there a sensible way to set CFLAGS for a single file? Right now I'm breaking it out into an LT convenience lib that gets linked in to the final output... but I just had the thought that perhaps there was a simple piece of declarative goo I was missing... Monty

Re: AM Conditional for SUBDIRS

Vikram Ambrose wrote: > I have a problem trying to conditional include a subdir into a build > configuration or not. > > I have tried two things. > 1) > - > SUBDIRS = pkgA pkgB > > if BUILD_pkgC > SUBDIRS += pkgC > endif >

include directory structure

Hey all, I read through the docs and I think there may be no good way to do this... but I thought I'd ask. I've got this: drizzle/ mystrings/ foo.h mysys/ bar.h libdrizzle/ libdrizzle.h drizzled/ global.h plugin.h In each dir are header files. The total include path

Re: best practice for injecting include dir across a project

Raja R Harinath wrote: > Hi, > > Monty Taylor <[EMAIL PROTECTED]> writes: > >> I've got a project that has 24 Makefile.am files. At the top of all of >> them at the moment, I've got: >> >> AM_CPPFLAGS = -I$(top_builddir)/include -I$(top

Re: best practice for injecting include dir across a project

Ralf Wildenhues wrote: > Hello Monty, > > * Monty Taylor wrote on Thu, Jul 24, 2008 at 08:43:39PM CEST: >> I've got a project that has 24 Makefile.am files. At the top of all of >> them at the moment, I've got: >> >> AM_CPPFLAGS = -I$(top_builddi

best practice for injecting include dir across a project

Hey all, I've got a project that has 24 Makefile.am files. At the top of all of them at the moment, I've got: AM_CPPFLAGS = -I$(top_builddir)/include -I$(top_srcdir)/include Which seems a bit ridiculous. I would love to inject those two into DEFAULT_INCLUDES, but I can't find any handles to do t