From: "Chan Kim" <ckim@etri.re.kr>
To: "'Rasmus Villemoes'" <rasmus.villemoes@prevas.dk>,
<u-boot@lists.denx.de>
Subject: RE: how to see cpp(C preprocessor) output for a file?
Date: Wed, 15 Dec 2021 00:10:43 +0900 [thread overview]
Message-ID: <054a01d7f0fc$c39bee40$4ad3cac0$@etri.re.kr> (raw)
In-Reply-To:
But when I do
make CROSS_COMPILE=aarch64-none-elf- lib/tiny-printf.1
make: *** No rule to make target 'lib/tiny-printf.1'. Stop.
It doesn't work for me..
But make x/y/z.s works.
> -----Original Message-----
> From: Chan Kim <ckim@etri.re.kr>
> Sent: Tuesday, December 14, 2021 11:56 PM
> To: 'Rasmus Villemoes' <rasmus.villemoes@prevas.dk>; 'u-
> boot@lists.denx.de' <u-boot@lists.denx.de>
> Subject: RE: how to see cpp(C preprocessor) output for a file?
>
> Wow that would be very helpful.
> Thank you!
> Chan
>
> > -----Original Message-----
> > From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
> > Sent: Tuesday, December 14, 2021 9:23 PM
> > To: ckim@etri.re.kr; u-boot@lists.denx.de
> > Subject: Re: how to see cpp(C preprocessor) output for a file?
> >
> > On 14/12/2021 09.23, ckim@etri.re.kr wrote:
> > > Hello,
> > >
> > > Is there any way I can see the cpp output of a file (for example
> > > arch/arm/lib/vsprintf.c) after the build? (in the Makefile option
> > > for
> > > example)
> >
> > make foo/bar/baz.i
> >
> > for any foo/bar/baz.c file which normally produces foo/bar/baz.o.
> >
> > If you have a arch/bla/xyz.S file, you can similarly do
> >
> > make arch/bla/xyz.s
> >
> > to run the preprocessor on the .S code. And if you want to see the
> > assembly generated from a .c file,
> >
> > make foo/bar/baz.s
> >
> > also works.
> >
> > Rasmus
next prev parent reply other threads:[~2021-12-14 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 8:23 how to see cpp(C preprocessor) output for a file? ckim
2021-12-14 12:23 ` Rasmus Villemoes
2021-12-14 14:55 ` Chan Kim
2021-12-14 15:10 ` Chan Kim [this message]
2021-12-15 7:28 ` Rasmus Villemoes
2021-12-15 7:36 ` Chan Kim
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='054a01d7f0fc$c39bee40$4ad3cac0$@etri.re.kr' \
--to=ckim@etri.re.kr \
--cc=rasmus.villemoes@prevas.dk \
--cc=u-boot@lists.denx.de \
/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