From: <guy...@vi...> - 2007-05-17 13:44:32
|
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 |