Debugging Makefiles - Revision history

Jsujjava: Add Category Tips and Tricks, Development Tools

2011-05-11T14:21:33Z

Add Category Tips and Tricks, Development Tools

2011-04-01T00:49:32Z

‎remake

2011-04-01T00:48:35Z

‎remake

2011-04-01T00:47:54Z

‎remake

2011-01-20T07:50:47Z

‎remake

2011-01-20T07:48:36Z

‎remake

2011-01-20T07:46:29Z

‎remake

2011-01-20T07:45:31Z

‎remake

2011-01-20T07:02:38Z

2008-06-13T20:08:55Z

add remake

← Older revision		Revision as of 14:21, 11 May 2011
Line 68:		Line 68:
	when you want to build for multiple architectures from the same source, or when you wish to avoid cluttering up		when you want to build for multiple architectures from the same source, or when you wish to avoid cluttering up
	the source tree with object files, libraries and other generated files (to make diffs easier).		the source tree with object files, libraries and other generated files (to make diffs easier).
		+
		+	[[Category:Development Tools]]
		+	[[Category:Tips and Tricks]]

@@ Line 36: / Line 36: @@
 == remake ==
-''remake'', is "A patched GNU make with a debugger,
+''remake'' is a patched GNU make with a debugger,
-better tracing and error reporting" (based on GNU make 3.82 now).
+better tracing and error reporting. The latest version is based on GNU make version 3.82 released sources.
 See: http://bashdb.sourceforge.net/remake/

@@ Line 36: / Line 36: @@
 == remake ==
-"remake", is "A patched GNU make with a debugger,
+''remake'', is "A patched GNU make with a debugger,
 better tracing and error reporting" (based on GNU make 3.82 now).

@@ Line 37: / Line 37: @@
 == remake ==
 "remake", is "A patched GNU make with a debugger,
-better tracing and error reporting" (based on GNU make 3.81 now).
+better tracing and error reporting" (based on GNU make 3.82 now).
 See: http://bashdb.sourceforge.net/remake/
-if there is valid makefile in your current directory, start debug like this:
+Use the option ''--debugger'' (short form is ''-X'') in your make invocation. For example:
   $ remake --debugger
-or there is a makefile named foo_makefile, start debug like this:
+But much of the time you may be able to get by using just the better tracing that is given.
-  $ remake --debugger -f foo_makefile
+  $ remake -x
 == Debugging a kernel build ==

@@ Line 36: / Line 36: @@
 == remake ==
-"remake", is "A patched GNU make with a debuger,
+"remake", is "A patched GNU make with a debugger,
 better tracing and error reporting" (based on GNU make 3.81 now).
 See: http://bashdb.sourceforge.net/remake/
-if there is valid makefile in your dirctory, start debug like this:
+if there is valid makefile in your current directory, start debug like this:
-  remake --debugger
+  $ remake --debugger
 or there is a makefile named foo_makefile, start debug like this:
-  remake --debugger -f foo_makefile
+  $ remake --debugger -f foo_makefile
 == Debugging a kernel build ==

← Older revision		Revision as of 07:46, 20 January 2011
Line 40:		Line 40:

	See: http://bashdb.sourceforge.net/remake/		See: http://bashdb.sourceforge.net/remake/
		+
		+	start debug like this:
		+
		+	remake --debugger

	== Debugging a kernel build ==		== Debugging a kernel build ==

@@ Line 28: / Line 28: @@
 Add the following lines to your Makefile:
-  include gdm
+  include gmd
 and

@@ Line 34: / Line 34: @@
   all:
           $(__BREAKPOINT)
 == Debugging a kernel build ==