Configure tools - Revision history

Ollydbg: /* The input fields */show the two images in this page.

2009-12-04T15:18:02Z

The input fields: show the two images in this page.

Akkernight at 01:26, 3 December 2009

2009-12-03T01:26:00Z

Akkernight at 01:25, 3 December 2009

2009-12-03T01:25:22Z

Akkernight at 00:43, 3 December 2009

2009-12-03T00:43:51Z

Akkernight at 00:20, 3 December 2009

2009-12-03T00:20:44Z

Akkernight: Created page with 'Category:Miscellaneous == !WORK IN PROGRESS! == == Introduction == I'll not be making a long introduction, but I want to explain to you why I first got into this, and s…'

2009-12-02T23:53:26Z

Created page with 'Category:Miscellaneous == !WORK IN PROGRESS! == == Introduction == I'll not be making a long introduction, but I want to explain to you why I first got into this, and s…'

New page

[[Category:Miscellaneous]]

== !WORK IN PROGRESS! ==

== Introduction ==

I'll not be making a long introduction, but I want to explain to you why I first got into this, and since I found nothing on the wiki about it, I decided to make the page myself.
Have you ever worked with Code::Blocks and makefiles? If so, havn't you often had to go into the teminal and then had to type ''"cd <path to project>"'' and then ''"make"'', for every work-session? Well I'll be using this example in my explanatory.

@@ Line 11: / Line 11: @@
 == The input fields ==
-[[Media:Slice_0_0.png]] : ''Fig. 1''
+[[image:Slice_0_0.png]] : ''Fig. 1''
-[[Media:Slice_0_2.png]] : ''Fig. 2''
+[[image:Slice_0_2.png]] : ''Fig. 2''
 So, as you can see in Fig. 2, I named mine ''make'', and I did this simply by pressing ''Add'' and then Fig. 1 pops up. Now Fig. 1 is the interesting one and the one I'll try to explain in detail.

@@ Line 25: / Line 25: @@
 '''The Parameters input field'''
 This is where you put the parameters you want passed to the executed application, as explained above. This is very useful if you want to make your executed tool do more than just execute.
 '''The Working directory input field'''

@@ Line 1: / Line 1: @@
 [[Category:Miscellaneous]]
@@ Line 18: / Line 15: @@
 [[Media:Slice_0_2.png]] : ''Fig. 2''
-So, as you can see in Fig. 2, I named mine ''cd_shell'', and I did this simply by pressing ''Add'' and then Fig. 1 pops up. Now Fig. 1 is the interesting one and the one I'll try to explain in detail.
+So, as you can see in Fig. 2, I named mine ''make'', and I did this simply by pressing ''Add'' and then Fig. 1 pops up. Now Fig. 1 is the interesting one and the one I'll try to explain in detail.
 '''The Name input field'''
@@ Line 24: / Line 21: @@
 '''The Executable input field'''
-This is where you put the application you want executed by your tool. You can either enter the location to the application, by either browsing or typing it in, or you can enter a command in there, like I just add ''xterm'' which is a Shell for Linux. You can also add arguments/parameters supported by the executed application, which means you could put ''xterm -bg red'' into the Executable input field, and the background of the executed xterm would be red. This should be put in the Parameters input field though, see below.
+This is where you put the application you want executed by your tool. You can either enter the location to the desired application, by either browsing or typing it in, or you can enter a command in there, like I add ''make'' which is a Shell command for Linux, which 'makes' makefiles. You can also add arguments/parameters supported by the executed application, which means you could put ''xterm -bg red'' into the Executable input field, and the background of the executed Shell xterm, would be red. This should be put in the Parameters input field though, see below.
 '''The Parameters input field'''
-This is where you put the parameters you want passed to the executed application, as explained above. This is very useful if you want to make more advanced tools than I'll be explaining. You can use the macros in here, which will be explained later on.
+This is where you put the parameters you want passed to the executed application, as explained above. This is very useful if you want to make your executed tool do more than just execute.
 '''The Working directory input field'''
-This
+This is where the terminal will ''cd'' to, as in, ''cd <input directory>''.

@@ Line 10: / Line 10: @@
 I'll not be making a long introduction, but I want to explain to you why I first got into this, and since I found nothing on the wiki about it, I decided to make the page myself.
 Have you ever worked with Code::Blocks and makefiles? If so, havn't you often had to go into the teminal and then had to type ''cd <path to project>'' and then ''make'', for every work-session? Well I'll be using this example in my explanatory.
-== The ''User-defined tools'' window ==
+== The input fields ==
-[[Media:Slice_0_0.png]]
+[[Media:Slice_0_0.png]] : ''Fig. 1''
 [[Media:Slice_0_2.png]]

← Older revision		Revision as of 00:20, 3 December 2009
Line 9:		Line 9:

	I'll not be making a long introduction, but I want to explain to you why I first got into this, and since I found nothing on the wiki about it, I decided to make the page myself.		I'll not be making a long introduction, but I want to explain to you why I first got into this, and since I found nothing on the wiki about it, I decided to make the page myself.
−	Have you ever worked with Code::Blocks and makefiles? If so, havn't you often had to go into the teminal and then had to type ''"cd <path to project>"'' and then ''"make"'', for every work-session? Well I'll be using this example in my explanatory.	+	Have you ever worked with Code::Blocks and makefiles? If so, havn't you often had to go into the teminal and then had to type ''cd <path to project>'' and then ''make'', for every work-session? Well I'll be using this example in my explanatory.
		+
		+	== The ''User-defined tools'' window ==
		+
		+	[[Media:Slice_0_0.png]]
		+	[[Media:Slice_0_2.png]]