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: | "Marc Britten" <yugami@monochromatic.com> |
Newsgroups: | comp.compilers,comp.unix.programmer |
Date: | 6 Jul 2001 16:30:15 -0400 |
Organization: | Posted via Supernews, http://www.supernews.com |
References: | 01-07-031 |
Keywords: | tools |
Posted-Date: | 06 Jul 2001 16:30:15 EDT |
basicly the problem is one target can produce any number of actions,
those actions may or maynot product programs.
make is basicly a scripting language, it doesn't actually know what
actions are making executables and which ones are making object files and
which ones are parcing yacc scripts.
"Stan" <Stanya@aol.com> wrote:
> Is there any possible way from reading the main makefile (root directory
> of the project) and extracting this information? I'm on HP-UX, but I use
> ClearCase which, in turn, provides clearmake - their own version of the
> UNIX make(1). I figured out that by running clearmake w/ the -w -d and
> -n options, I get a dry run that gives me the names of all the
> directories and files used in the build for the project, but I still
> haven't found a way to separate this by application or executable, IF
> possible at all.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.