RE: Target-specific CFLAGS

2004-02-24 Thread Drummonds, Scott B
I didn't. But I do now. Thanks, Scott > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > On Behalf Of Ben Pfaff > Sent: Tuesday, February 24, 2004 1:43 PM > To: [EMAIL PROTECTED] > Subject: Re: Target-specific CFLAGS > >

RE: Target-specific CFLAGS

2004-02-24 Thread Drummonds, Scott B
From: [EMAIL PROTECTED] > > noinst_LIBRARIES = normal.a normal-feature.a > > normal_a_SOURCES = [bunch of files] > normal_feature_a_SOURCES = $(normal_a_SOURCES) > normal_feature_a_CFLAGS = -DFEATURE > ... > Where have I gone wrong? Of course, when my source files are C++ files the _CFLAGS ext

Target-specific CFLAGS

2004-02-24 Thread Drummonds, Scott B
Hi, everyone, A couple of weeks back I posted my problems with getting an ancient version of Automake to build two libraries. Each was to use the same source but one should have it's objects compiled with "-DFEATURE". I attempted to use the following setup: noinst_LIBRARIES = normal.a normal-f

Automake 1.7 Bug?

2004-02-11 Thread Drummonds, Scott B
Hi, everyone, My efforts to update this build environment continue. Running automake (1.7) on my existing configure.in reports the following error: /tmp/t4qaYxc3/traces.m4:873: /usr/bin/m4: Error matching regular expression `^ *\(.*\) *$' Use of uninitialized value at .../bin/automake line 5044

RE: AM_INIT_AUTOMAKE Call in Automake 1.7

2004-02-11 Thread Drummonds, Scott B
From: [EMAIL PROTECTED] > I'm not sure, but I think another possibility might be that the > right aclocal program is still finding the old 1.4 macros. Hmmm... I think you're on to something. The previous build owner added some additional macros to the default source of aclocal macros. He put t

RE: AM_INIT_AUTOMAKE Call in Automake 1.7

2004-02-11 Thread Drummonds, Scott B
From: [EMAIL PROTECTED] > It's not complaining about your configure.in, but rather that the > old Automake-1.4 macros are still in your aclocal.m4 file. With > luck, rerunning (the 1.7 version of) the "aclocal" program should > fix that. Actually, I guess my original post wasn't complete. I had

AM_INIT_AUTOMAKE Call in Automake 1.7

2004-02-11 Thread Drummonds, Scott B
Hi, everyone, Replies I got from this group with regards to a problem I was having in my build environment (that used Automake 1.4) led me to request a version upgrade. I am now able to use Automake 1.7. (Better, eh?) After running automake on my existing configure.in, I received the following

RE: Conditional Library Compilation

2004-02-05 Thread Drummonds, Scott B
From: Frederik Fouvry [mailto:[EMAIL PROTECTED] > You can install it on other places than /usr/share or /usr/local > (forgot which one is the default) with But I don't own the large software project that I'm trying to modify. If I upgrade the version of Automake to provide a feature I need in the

RE: Conditional Library Compilation

2004-02-05 Thread Drummonds, Scott B
From: Alexandre Duret-Lutz [mailto:[EMAIL PROTECTED] > Sorry to insist, but you still haven't answered the most basic > question: what automake version are you using? Begging your pardon, but this is a quote from my reply to your message that was sent both to the group and to you directly: > I'm

[automake] Multiple Compilations of Same Library

2004-02-04 Thread Drummonds, Scott B
Title: [automake] Multiple Compilations of Same Library Hi again, all, I figured out a workaround to my conditional build problem yesterday and am now stuck on a different problem.  Given my lack of experience with automake, I'm hoping that one of you can help me out. Remember that I want

RE: Conditional Library Compilation

2004-02-04 Thread Drummonds, Scott B
From: Alexandre Duret-Lutz [mailto:[EMAIL PROTECTED] > What are the symptoms? (i.e., what "doesn't work" means?) To follow up with even more detail about this, Makefile.am looks like this: noinst_LIBRARIES = libNormal.a if FEATURE noinst_LIBRARIES += libNormalFeature.a endif libNormal_a_SO

RE: Conditional Library Compilation

2004-02-03 Thread Drummonds, Scott B
From: Alexandre Duret-Lutz [mailto:[EMAIL PROTECTED] > Which version of Automake are you using? What make implementation? I'm always afraid to answer this question, because our distributed development environment is old and impossible (for me) to update. But, here goes: 1194> /usr/bin/automa

RE: Conditional Library Compilation

2004-02-03 Thread Drummonds, Scott B
From: [EMAIL PROTECTED] > One possibility: > > noinst_LIBRARIES = libfoo.a > libfoo_a_SOURCES = foo.c bar.c > > if FEATURE > noinst_LIBRARIES += libMyLib.a > libMyLIB_a_CPPFLAGS = -DMyLibExtraFlags > libMyLib_a_SOURCES = $(libfoo_a_SOURCES) > endif This seems to suffer from the same problem as

Conditional Library Compilation

2004-02-03 Thread Drummonds, Scott B
Hi, everyone, I've been playing around with the conditionals as defined in the documentation but have been unable to achieve one of my build environment goals. I'm hoping someone can help me with this: I want to be able to build an additional library (using the same source as an existing library

[automake] Two CVS Projects, One Build Environment

2003-07-22 Thread Drummonds, Scott B
Hi, everyone, I was wondering if someone out there could give me some advice on setting up the build environment for a project I'm working on. For this project I have some code that I want to share between two separate software projects. I would like each of these software projects to conditiona