public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* preprocessor name
@ 2002-03-25  7:04 Wei Qin
  2002-03-26  1:45 ` Claudio Bley
  0 siblings, 1 reply; 2+ messages in thread
From: Wei Qin @ 2002-03-25  7:04 UTC (permalink / raw)
  To: gcc-help


Hi,
	I am writing a shell script to obtain information of gcc's
preprocessor. I can obtain the path by getting the dirname of
	gcc -print-libgcc-file-name
	But I have trouble figuring out the cpp name. For gcc2.95, it is
cpp, for 3.0, it is cpp0. I am not sure if it is going to change in the
future. Is there a simple way to get the command name without assuming
the 2 possibilities?

thanks in advance.

Wei

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: preprocessor name
  2002-03-25  7:04 preprocessor name Wei Qin
@ 2002-03-26  1:45 ` Claudio Bley
  0 siblings, 0 replies; 2+ messages in thread
From: Claudio Bley @ 2002-03-26  1:45 UTC (permalink / raw)
  To: gcc-help

>>>>> "Wei" == Wei Qin <wqin@EE.Princeton.EDU> writes:

    Wei> Hi, I am writing a shell script to obtain information of gcc's
    Wei> preprocessor. I can obtain the path by getting the dirname of
    Wei> gcc -print-libgcc-file-name But I have trouble figuring out
    Wei> the cpp name. For gcc2.95, it is cpp, for 3.0, it is cpp0. I
    Wei> am not sure if it is going to change in the future. Is there a
    Wei> simple way to get the command name without assuming the 2
    Wei> possibilities?

Why don't you just use 'gcc -E'? gcc itself knows the name of the
preprocessor, I guess.

Claudio

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2002-03-26  9:45 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-03-25  7:04 preprocessor name Wei Qin
2002-03-26  1:45 ` Claudio Bley

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).