<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.codeblocks.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Akkernight</id>
	<title>Code::Blocks - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.codeblocks.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Akkernight"/>
	<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php/Special:Contributions/Akkernight"/>
	<updated>2026-05-02T15:06:03Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.35.0</generator>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Configure_tools&amp;diff=6225</id>
		<title>Configure tools</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Configure_tools&amp;diff=6225"/>
		<updated>2009-12-03T01:26:00Z</updated>

		<summary type="html">&lt;p&gt;Akkernight: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Miscellaneous]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
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 &amp;lt;path to project&amp;gt;'' and then ''make'', for every work-session? Well I'll be using this example in my explanatory.&lt;br /&gt;
I'm going to talk about the windows in ''Tools -&amp;gt; Configure tools...'', which you should find on the Code::Blocks Menu Strip.&lt;br /&gt;
&lt;br /&gt;
== The input fields ==&lt;br /&gt;
&lt;br /&gt;
[[Media:Slice_0_0.png]] : ''Fig. 1''&lt;br /&gt;
&lt;br /&gt;
[[Media:Slice_0_2.png]] : ''Fig. 2''&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
'''The Name input field'''&lt;br /&gt;
This is simply where you write the desired name for your tool. The name will show up when you press ''Tools'', on the Code::Blocks Menu Strip.&lt;br /&gt;
&lt;br /&gt;
'''The Executable input field'''&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
'''The Parameters input field'''&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
'''The Working directory input field'''&lt;br /&gt;
This is where the terminal will ''cd'' to, as in, ''cd &amp;lt;input directory&amp;gt;''.&lt;br /&gt;
&lt;br /&gt;
== Launching options ==&lt;br /&gt;
&lt;br /&gt;
As seen in Fig. 1 there are four options for ''Launching options'', I'll try to explain each option.&lt;br /&gt;
# This simply means that Code::Blocks will launch a terminal/console window which you'll see, and then when the execution is done, the terminal will wait for you to give it a keypress.&lt;br /&gt;
This is good if you want time to read the output.&lt;br /&gt;
# This option will hide the terminal for you, but redirecting standard output.&lt;br /&gt;
# ''Needs explanatory!''&lt;br /&gt;
# ''Needs explanatory!''&lt;br /&gt;
&lt;br /&gt;
== Macros ==&lt;br /&gt;
&lt;br /&gt;
These are pre-defined macros for you to use, and they are very useful. Let me explain one use of them for my example.&lt;br /&gt;
My example is about making makefiles, and fortunately Code::Blocks has a macro which defines the destination to the makefile of the project.&lt;br /&gt;
The macros have names which are pretty much self explanatory.&lt;br /&gt;
&lt;br /&gt;
== The ''make'' example explanation ==&lt;br /&gt;
So as seen in fig. 1, I call my tool ''make'', which is a fine name since the tool is for making makefiles, and making in this context means executing them.&lt;br /&gt;
Then in the Executable input field I put ''make'' again, this is because in my linux distribution (which is Arch Linux) the command to launch ''make'' is simply ''make''.&lt;br /&gt;
I put no paramters because I need none, ''make'' automaticly searches for the file named ''makefile''.&lt;br /&gt;
I use a macro for my working directory, because fortunately there's a macro that defines the destination to the project's makefile.&lt;br /&gt;
Since I want to read the output, my launch option was the first one because it gives me the time to read the output.&lt;br /&gt;
And that was pretty much it.&lt;br /&gt;
&lt;br /&gt;
== Notes ==&lt;br /&gt;
This wiki page was based on Linux (specifically Arch Linux running on Openbox), because that is what I use/run. There might be some differences with other OS' like Microsoft Windows, etc.&lt;/div&gt;</summary>
		<author><name>Akkernight</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Configure_tools&amp;diff=6224</id>
		<title>Configure tools</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Configure_tools&amp;diff=6224"/>
		<updated>2009-12-03T01:25:22Z</updated>

		<summary type="html">&lt;p&gt;Akkernight: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Miscellaneous]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
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 &amp;lt;path to project&amp;gt;'' and then ''make'', for every work-session? Well I'll be using this example in my explanatory.&lt;br /&gt;
I'm going to talk about the windows in ''Tools -&amp;gt; Configure tools...'', which you should find on the Code::Blocks Menu Strip.&lt;br /&gt;
&lt;br /&gt;
== The input fields ==&lt;br /&gt;
&lt;br /&gt;
[[Media:Slice_0_0.png]] : ''Fig. 1''&lt;br /&gt;
&lt;br /&gt;
[[Media:Slice_0_2.png]] : ''Fig. 2''&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
'''The Name input field'''&lt;br /&gt;
This is simply where you write the desired name for your tool. The name will show up when you press ''Tools'', on the Code::Blocks Menu Strip.&lt;br /&gt;
&lt;br /&gt;
'''The Executable input field'''&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
'''The Parameters input field'''&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''The Working directory input field'''&lt;br /&gt;
This is where the terminal will ''cd'' to, as in, ''cd &amp;lt;input directory&amp;gt;''.&lt;br /&gt;
&lt;br /&gt;
== Launching options ==&lt;br /&gt;
&lt;br /&gt;
As seen in Fig. 1 there are four options for ''Launching options'', I'll try to explain each option.&lt;br /&gt;
# This simply means that Code::Blocks will launch a terminal/console window which you'll see, and then when the execution is done, the terminal will wait for you to give it a keypress.&lt;br /&gt;
This is good if you want time to read the output.&lt;br /&gt;
# This option will hide the terminal for you, but redirecting standard output.&lt;br /&gt;
# ''Needs explanatory!''&lt;br /&gt;
# ''Needs explanatory!''&lt;br /&gt;
&lt;br /&gt;
== Macros ==&lt;br /&gt;
&lt;br /&gt;
These are pre-defined macros for you to use, and they are very useful. Let me explain one use of them for my example.&lt;br /&gt;
My example is about making makefiles, and fortunately Code::Blocks has a macro which defines the destination to the makefile of the project.&lt;br /&gt;
The macros have names which are pretty much self explanatory.&lt;br /&gt;
&lt;br /&gt;
== The ''make'' example explanation ==&lt;br /&gt;
So as seen in fig. 1, I call my tool ''make'', which is a fine name since the tool is for making makefiles, and making in this context means executing them.&lt;br /&gt;
Then in the Executable input field I put ''make'' again, this is because in my linux distribution (which is Arch Linux) the command to launch ''make'' is simply ''make''.&lt;br /&gt;
I put no paramters because I need none, ''make'' automaticly searches for the file named ''makefile''.&lt;br /&gt;
I use a macro for my working directory, because fortunately there's a macro that defines the destination to the project's makefile.&lt;br /&gt;
Since I want to read the output, my launch option was the first one because it gives me the time to read the output.&lt;br /&gt;
And that was pretty much it.&lt;br /&gt;
&lt;br /&gt;
== Notes ==&lt;br /&gt;
This wiki page was based on Linux (specifically Arch Linux running on Openbox), because that is what I use/run. There might be some differences with other OS' like Microsoft Windows, etc.&lt;/div&gt;</summary>
		<author><name>Akkernight</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=File:Slice_0_0.png&amp;diff=6223</id>
		<title>File:Slice 0 0.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=File:Slice_0_0.png&amp;diff=6223"/>
		<updated>2009-12-03T01:07:21Z</updated>

		<summary type="html">&lt;p&gt;Akkernight: uploaded a new version of &amp;quot;File:Slice 0 0.png&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Akkernight</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=File:Slice_0_2.png&amp;diff=6222</id>
		<title>File:Slice 0 2.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=File:Slice_0_2.png&amp;diff=6222"/>
		<updated>2009-12-03T00:46:43Z</updated>

		<summary type="html">&lt;p&gt;Akkernight: uploaded a new version of &amp;quot;File:Slice 0 2.png&amp;quot;:&amp;amp;#32;Changing the purpose of the wiki page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Akkernight</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=File:Slice_0_0.png&amp;diff=6221</id>
		<title>File:Slice 0 0.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=File:Slice_0_0.png&amp;diff=6221"/>
		<updated>2009-12-03T00:46:22Z</updated>

		<summary type="html">&lt;p&gt;Akkernight: uploaded a new version of &amp;quot;File:Slice 0 0.png&amp;quot;:&amp;amp;#32;Changing the purpose of the wiki page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Akkernight</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Configure_tools&amp;diff=6220</id>
		<title>Configure tools</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Configure_tools&amp;diff=6220"/>
		<updated>2009-12-03T00:43:51Z</updated>

		<summary type="html">&lt;p&gt;Akkernight: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Miscellaneous]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== !WORK IN PROGRESS! ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
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 &amp;lt;path to project&amp;gt;'' and then ''make'', for every work-session? Well I'll be using this example in my explanatory.&lt;br /&gt;
I'm going to talk about the windows in ''Tools -&amp;gt; Configure tools...'', which you should find on the Code::Blocks Menu Strip.&lt;br /&gt;
&lt;br /&gt;
== The input fields ==&lt;br /&gt;
&lt;br /&gt;
[[Media:Slice_0_0.png]] : ''Fig. 1''&lt;br /&gt;
&lt;br /&gt;
[[Media:Slice_0_2.png]] : ''Fig. 2''&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
'''The Name input field'''&lt;br /&gt;
This is simply where you write the desired name for your tool. The name will show up when you press ''Tools'', on the Code::Blocks Menu Strip.&lt;br /&gt;
&lt;br /&gt;
'''The Executable input field'''&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
'''The Parameters input field'''&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
'''The Working directory input field'''&lt;br /&gt;
This&lt;/div&gt;</summary>
		<author><name>Akkernight</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=File:Slice_0_0.png&amp;diff=6219</id>
		<title>File:Slice 0 0.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=File:Slice_0_0.png&amp;diff=6219"/>
		<updated>2009-12-03T00:30:31Z</updated>

		<summary type="html">&lt;p&gt;Akkernight: uploaded a new version of &amp;quot;File:Slice 0 0.png&amp;quot;:&amp;amp;#32;There's text now!&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Akkernight</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Configure_tools&amp;diff=6218</id>
		<title>Configure tools</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Configure_tools&amp;diff=6218"/>
		<updated>2009-12-03T00:20:44Z</updated>

		<summary type="html">&lt;p&gt;Akkernight: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Miscellaneous]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== !WORK IN PROGRESS! ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
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 &amp;lt;path to project&amp;gt;'' and then ''make'', for every work-session? Well I'll be using this example in my explanatory.&lt;br /&gt;
&lt;br /&gt;
== The ''User-defined tools'' window ==&lt;br /&gt;
&lt;br /&gt;
[[Media:Slice_0_0.png]]&lt;br /&gt;
[[Media:Slice_0_2.png]]&lt;/div&gt;</summary>
		<author><name>Akkernight</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=File:Slice_0_0.png&amp;diff=6217</id>
		<title>File:Slice 0 0.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=File:Slice_0_0.png&amp;diff=6217"/>
		<updated>2009-12-03T00:20:02Z</updated>

		<summary type="html">&lt;p&gt;Akkernight: uploaded a new version of &amp;quot;File:Slice 0 0.png&amp;quot;:&amp;amp;#32;borders&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Akkernight</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=File:Slice_0_2.png&amp;diff=6216</id>
		<title>File:Slice 0 2.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=File:Slice_0_2.png&amp;diff=6216"/>
		<updated>2009-12-03T00:13:03Z</updated>

		<summary type="html">&lt;p&gt;Akkernight: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Akkernight</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=File:Slice_0_0.png&amp;diff=6215</id>
		<title>File:Slice 0 0.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=File:Slice_0_0.png&amp;diff=6215"/>
		<updated>2009-12-03T00:12:39Z</updated>

		<summary type="html">&lt;p&gt;Akkernight: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Akkernight</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Configure_tools&amp;diff=6214</id>
		<title>Configure tools</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Configure_tools&amp;diff=6214"/>
		<updated>2009-12-02T23:53:26Z</updated>

		<summary type="html">&lt;p&gt;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…'&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Miscellaneous]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== !WORK IN PROGRESS! ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
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 ''&amp;quot;cd &amp;lt;path to project&amp;gt;&amp;quot;'' and then ''&amp;quot;make&amp;quot;'', for every work-session? Well I'll be using this example in my explanatory.&lt;/div&gt;</summary>
		<author><name>Akkernight</name></author>
	</entry>
</feed>