Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| Makefile questions Stanya@aol.com (2001-07-03) |
| Re: Makefile questions lockner@chaos.cns.uni.edu (Matthew J. Lockner) (2001-07-06) |
| Re: Makefile questions yedema@natlab.research.philips.com (Wim Yedema) (2001-07-06) |
| Re: Makefile questions yugami@monochromatic.com (Marc Britten) (2001-07-06) |
| Re: Makefile questions walter@digitalmars.com (walter) (2001-07-06) |
| Re: Makefile questions lex@cc.gatech.edu (Lex Spoon) (2001-07-17) |
| From: | Wim Yedema <yedema@natlab.research.philips.com> |
| Newsgroups: | comp.compilers,comp.unix.programmer |
| Date: | 6 Jul 2001 16:27:55 -0400 |
| Organization: | Compilers Central |
| References: | 01-07-031 |
| Keywords: | tools |
| Posted-Date: | 06 Jul 2001 16:27:55 EDT |
Stanya@aol.com (Stan) writes:
> What I need to do is figure out which files in the project are used
> for which applications -
can you call make for each separate application? if so you can just type
"make target" and look at the generated object files (assuming you generate
them) If you don't want to wait that long, GNU make has a -t option that
only touches files instead running commands, might be useful.
another possibility: run "nm" on the binary, this gives you the functions
and global variables that are used, then use something like TAGS to find
them in the sources.
it's a bit sketchy, but maybe it'll help.
wim yedema
Return to the
comp.compilers page.
Search the
comp.compilers archives again.