Tim == Tim Van Holder [EMAIL PROTECTED] writes:
Tim On Wed, 2002-11-06 at 11:11, [EMAIL PROTECTED] wrote:
DEFAULT_INCLUDES = -I. -I$(srcdir) -I.
This raises 2 questions in itself:
a. what's wrong with DEFAULT_INCLUDES = -I. -I$(srcdir)
Tim Don't know that,
The third -I gives the
On Thu, 2002-11-07 at 12:57, Alexandre Duret-Lutz wrote:
Tim == Tim Van Holder [EMAIL PROTECTED] writes:
Tim On Wed, 2002-11-06 at 11:11, [EMAIL PROTECTED] wrote:
DEFAULT_INCLUDES = -I. -I$(srcdir) -I.
This raises 2 questions in itself:
a. what's wrong with DEFAULT_INCLUDES =
Well, I guess we all got smarter on the tripple -I. issue. Thanks!
Otherwise, I'm also subscribed on the list, so no need to CC me in every
post :-)
.
--
Miki Shapiro [EMAIL PROTECTED]
Coder - Unixophile - Boarder - Quake God
Aladdin Knowledge Systems
[EMAIL PROTECTED] wrote:
Otherwise, I'm also subscribed on the list, so no need to CC me in every
post :-)
It is a function of the mail client Reply-All event to add you in the
distribution of the response. If you don't wish personal copies as well
as list copies then it is upto you to set
Earnie Boyd writes:
[EMAIL PROTECTED] wrote:
Otherwise, I'm also subscribed on the list, so no need to CC me in every
post :-)
It is a function of the mail client Reply-All event to add you in the
distribution of the response. If you don't wish personal copies as well
as list copies
Earnie Boyd [EMAIL PROTECTED] [2002-11-07 11:39:37 -0500]:
[EMAIL PROTECTED] wrote:
Otherwise, I'm also subscribed on the list, so no need to CC me in every
post :-)
Then set M-F-T in your postings.
Mail-Followup-To: [EMAIL PROTECTED]
It is a function of the mail client Reply-All event to
Wow, that saves me dual implementation of 'debug' and 'release' make
targets. cool :-)
Yet 2 more newbie questions:
Q1. Why do I get:
-I. -I. -I.
when make runs gcc?
peekeing in the Makefile.in reveals:
DEFAULT_INCLUDES = -I. -I$(srcdir) -I.
This raises 2 questions in itself:
a.
[EMAIL PROTECTED] writes:
Wow, that saves me dual implementation of 'debug' and 'release' make
targets. cool :-)
Yet 2 more newbie questions:
Q1. Why do I get:
-I. -I. -I.
when make runs gcc?
peekeing in the Makefile.in reveals:
DEFAULT_INCLUDES = -I. -I$(srcdir) -I.
This
On Wed, 2002-11-06 at 11:11, [EMAIL PROTECTED] wrote:
DEFAULT_INCLUDES = -I. -I$(srcdir) -I.
This raises 2 questions in itself:
a. what's wrong with DEFAULT_INCLUDES = -I. -I$(srcdir)
Don't know that,
or, since
my project's sources all lie in the root (as much as I'd have liked
Bob == Bob Proulx [EMAIL PROTECTED] writes:
Bob If you want to change this you can set CXXFLAGS at configure
Bob time.
Bob CFLAGS=-O CXXFLAGS=-O ./configure
./configure CFLAGS=-O CXXFLAGS=-O
is better.
Akim Demaille wrote:
Bob == Bob Proulx [EMAIL PROTECTED] writes:
Bob If you want to change this you can set CXXFLAGS at configure
Bob time.
Bob CFLAGS=-O CXXFLAGS=-O ./configure
./configure CFLAGS=-O CXXFLAGS=-O
is better.
because it then becomes a part of config.status while
On Tue, Nov 05, 2002 at 07:35:11AM -0500, Earnie Boyd wrote:
Akim Demaille wrote:
Bob == Bob Proulx [EMAIL PROTECTED] writes:
Bob CFLAGS=-O CXXFLAGS=-O ./configure
./configure CFLAGS=-O CXXFLAGS=-O
is better.
because it then becomes a part of config.status while the
Small question:
Why do my autoconf-generated configure scripts automatically fit in
debugging info -g -O2 (or -g if I ask nicely?)
When I compile release versions of my code, how do I (elegantly) ask
automake, or rather autoconf (through autoconf.in) to omit this from
CXXFLAGS?
Thanks!
--
Miki
13 matches
Mail list logo
