Mail Archives: djgpp/1998/01/27/02:16:41
From: | "John M. Aldrich" <fighteer AT cs DOT com>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Re: gcc switches
|
Date: | Tue, 27 Jan 1998 02:04:53 -0500
|
Organization: | Two pounds of chaos and a pinch of salt.
|
Lines: | 36
|
Message-ID: | <34CD8715.7C5E@cs.com>
|
References: | <6ae1lc$gei$1 AT herald DOT Mines DOT EDU>
|
NNTP-Posting-Host: | ppp205.cs.com
|
Mime-Version: | 1.0
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Jean-Luc Romano wrote:
>
> Is there any list that can tell me what DJGPP's gcc switches are?
> I've tried "gcc -?", "gcc -h", and "gcc -help" but they don't seem to
> work.
gcc's command line options are far too voluminous to include in a help
listing. You'd be much better off reading the actual documentation.
First, download and install 'v2gnu/txi390b.zip', which is the GNU Info
reader. Then type "info gcc invoking" to learn more than you ever
wanted to know about gcc's switches. :-)
A quick summary of the more commonly used switches:
-o set output file
-g include full debugging information
-s strip debugging information (link stage only)
-O optimize
-O[1,2,3,...] additional levels of optimization
-Wall extra (highly valuable) warnings
-c compile to object code
-S compile to assembly code
-l<lib> link lib<lib>.a (must go at end of command line)
-L<dir> specify additional library search directory(ies)
-I<dir> specify additional include search directory(ies)
Basically, if there's something you want gcc to do, there's a switch to
tell it to do it.
--
---------------------------------------------------------------------
| John M. Aldrich | "If 'everybody knows' such-and-such, |
| aka Fighteer I | then it ain't so, by at least ten |
| mailto:fighteer AT cs DOT com | thousand to one." |
| http://www.cs.com/fighteer | - Lazarus Long |
---------------------------------------------------------------------
- Raw text -