From:	pavenis AT lanet DOT lv
Message-ID:	<B0000107414@stargate.astr.lu.lv>
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date:	Tue, 2 Nov 1999 16:07:27 +0200
MIME-Version:	1.0
Subject:	Re: -g vs -s
References:	<B0000107412 AT stargate DOT astr DOT lu DOT lv>
In-reply-to:	<Pine.SUN.3.91.991102154604.21750A-100000@is>
X-mailer:	Pegasus Mail for Win32 (v3.12a)
Reply-To:	djgpp-workers AT delorie DOT com

On 2 Nov 99, at 15:48, Eli Zaretskii wrote:

> 
> On Tue, 2 Nov 1999 pavenis AT lanet DOT lv wrote:
> 
> > Let's assume we have too files foo.c and bar.c in project. Rhide will 
> > generate commands like (if options -g and -O2 are requested in project)
> > 	gcc -g -O2 -c foo.c -o foo.o
> > 	gcc -g -O2 -c bar.c -o bar.o
> > 	gcc foo.o bar.o -o foo.exe
> 
> This can be handled by changing the relevant RHIDE_* macros so that it 
> passes -g or -g0 to the linker.
> 
> > We'll have similar problem also with many makefiles.
> 
> Most Makefile's I saw put -g into CFLAGS, so linking is done with -g as 
> well.
> 

Yes. Usualy we can find some workaround for problems some change 
causes. But I'm afraid this would require also novices to do such 
changes (messing with RHIDE-* macros, etc). If we remeber -lstdcx 
problem in rhide... . I'm afraid this would cause at least the same 
amount of questions as -lstdcxx/-lstdcx problem. Even if we update 
current versions to use -s by default, many poeple will still use 
outdated versions (and mix new ones and outdated ones) and will run 
into a trouble.

I think that the best is to avoid such hack

Andris

- Raw text -