kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Andreev <andreev@swemel.ru>
To: "Frank A. Cancio Bello" <frank@generalsoftwareinc.com>,
	 kernelnewbies@kernelnewbies.org
Subject: Re: How to get the preprocessor output as part of the compilation process?
Date: Mon, 09 Dec 2019 13:10:11 +0300	[thread overview]
Message-ID: <5DEE1D83.2040704@swemel.ru> (raw)
In-Reply-To: <20191208190302.ngj5qlampi4utjgk@frank-laptop>

Hi, Frank.

The universal approach that always works in this and many similar cases is just to replace the instrumented binary by your interception shell script.

E.g. rename gcc to gcc.hide (generally, moving into another location may not work) and setup 'gcc' script that does what you want: replaces `-c' with the `-E', replaces `-o' argument, etc ..., calls gcc.hide to preprocess source then calls gcc.hide with original non-modified command line.

This is cumbersome process, you can break some things, there may be a handful try and fix iterations, but the advantage is that you have a full control on what is happening, and you do not need support from the tool, build process and product maintainers.

The interception like this is used by static code analysis tools.

Regards, Konstantin

Frank A. Cancio Bello, 08 Dec 2019 MSK:
>
> Hi, I know that with gcc -E you can get the output of the preprocessor, but what I have to do to get that output for every source code file in the Linux Lernel as part of the compilation process?

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  parent reply	other threads:[~2019-12-09 10:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-08 19:05 How to get the preprocessor output as part of the compilation process? Frank A. Cancio Bello
2019-12-08 21:53 ` Valdis Klētnieks
2019-12-09 10:10 ` Konstantin Andreev [this message]
2019-12-10  3:17   ` Valdis Klētnieks
2019-12-10 13:35     ` Konstantin Andreev
2019-12-12  3:14 ` Aruna Hewapathirane

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5DEE1D83.2040704@swemel.ru \
    --to=andreev@swemel.ru \
    --cc=frank@generalsoftwareinc.com \
    --cc=kernelnewbies@kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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 NNTP newsgroup(s).