Re: [Bashdb-devel] first GNU make with a debugger

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

Thanks for the information and link. How the "make + debugger" project
is going to be managed is open for discussion and is very much up in
the air.

Up to now I've been focused on feasibility of developing such a tool,
getting a small but useful prototype working, and gauging the overall
difficulty. Although, I haven't had any feedback from others on what
is now there, based on my own experience I think this project is a
keeper. I've certainly learned more about the complex Makefiles
produced by automake and it has been able to help me understand what's
going on.

Also Interesting, this project meshes well with the bash
debugger. Makefiles often contain fragments of scripts. With the
"remake" debugger, you can stop at a point where you are about to run
a script fragment, extract the script fragment easily with the
Makefile variables expanded courtesy of remake and then use the bash
debugger to debug that! Cool if I say so myself (and I think I have
to since bulk of bashdb-devel often very silent ;-).


Masatake YAMATO writes:
 > Different from bash, the source code of GNU make is managed by cvs(
 > http://savannah.gnu.org/cgi-bin/viewcvs/make/make/).  So I higly
 > recommend you to try arch to manage your remake source code. 
 > 
 > http://www.dwheeler.com/essays/scm.html
 > 
 > You can do (1) make synchronize your remake source code and the
 > original GNU make source in CVS repository; and (2) you can manage
 > your remake source code under version control system.
 >