[Bashdb-remake] Any suggestions to get make/remake to do a -E (c pre-processor) equivalent??

[R. B. <ro...@pa...>]

These options from the GNU Make manual may be of help.

`-p'
`--print-data-base'
     Print the data base (rules and variable values) that results from
     reading the makefiles; then execute as usual or as otherwise
     specified.  This also prints the version information given by the
     `-v' switch (see below).  To print the data base without trying to
     remake any files, use `make -qp'.  To print the data base of
     predefined rules and variables, use `make -p -f /dev/null'.  The
     data base output contains filename and linenumber information for
     command and variable definitions, so it can be a useful debugging
     tool in complex environments.

`-q'
`--question'
     "Question mode".  Do not run any commands, or print anything; just
     return an exit status that is zero if the specified targets are
     already up to date, one if any remaking is required, or two if an
     error is encountered.  *Note Instead of Executing the Commands:
     Instead of Execution.

However if this doesn't doesn't do it, then the most sure way to get
what you want done is to dig in and do it ;-) 

Patches to remake are most welcome. And I bet the same is true with GNU
make.

guy...@vi... writes:
 > Hi,
 > 
 > I recently read and tried to implement makefiles based on a webcast I Googled named: "Muli-Target, Multi-Platform Make: Building Everything from one Makefile" @  http://www.cmcrossroads.com/content/view/6921/153/  
 > 
 > I liked the ideas presented, since I'm developing on multi-platforms, and I'm trying to tame an old large C application with very messy MAKEDEPENDS, recursive MAKES, and other hoops and jumps, such as
 > pre-pre-processor steps depending on targets, platforms, DB, etc.
 > 
 > The premise of having makefiles included in the main makefile (instead of recursive) works nicely, but when I'm trying to troubleshoot the makefiles, that's when it starts going sour.  It's sometimes hard to
 > figure which variables are what, especially when using variables inside variables "ie:  ($(module)_prog1)" and in what sequence they present themselves, etc.  I have special targets to print out variables, and also to print out all variables, but...
 > 
 > It would be nice if:
 > MAKE has a -E option (like the gcc -E) to dump the fully expanded source (or makefile in this case) to STDOUT (or a file), after pass 1 (after all the includes are done and the variables are computed, but before any target decisions are made (in pass 2).
 > 
 > I was looking to see if REMAKE had such an option, and even though it definitely has some new
 > interesting debugging capabilities, I still couldn't find an equivalent to -E.  
 > 
 > Any suggestions and/or any ideas how much effort would be required to add this to REMAKE??
 > 
 > Regards,Guy
 > 
 > 
 > 
 > -------------------------------------------------------------------------
 > This SF.net email is sponsored by DB2 Express
 > Download DB2 Express C - the FREE version of DB2 express and take
 > control of your XML. No limits. Just data. Click to get it now.
 > http://sourceforge.net/powerbar/db2/
 > _______________________________________________
 > Bashdb-remake mailing list
 > Bas...@li...
 > https://lists.sourceforge.net/lists/listinfo/bashdb-remake
 >