Date: Tue, 2 Nov 1999 15:48:56 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: pavenis AT lanet DOT lv
cc: djgpp-workers AT delorie DOT com
Subject: Re: -g vs -s
In-Reply-To: <B0000107412@stargate.astr.lu.lv>
Message-ID: <Pine.SUN.3.91.991102154604.21750A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


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.