<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.openmpt.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Vananasun</id>
	<title>OpenMPT Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.openmpt.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Vananasun"/>
	<link rel="alternate" type="text/html" href="https://wiki.openmpt.org/Special:Contributions/Vananasun"/>
	<updated>2026-10-15T09:42:25Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.10</generator>
	<entry>
		<id>https://wiki.openmpt.org/index.php?title=Development:_Compiling_the_code&amp;diff=3994</id>
		<title>Development: Compiling the code</title>
		<link rel="alternate" type="text/html" href="https://wiki.openmpt.org/index.php?title=Development:_Compiling_the_code&amp;diff=3994"/>
		<updated>2020-12-10T11:23:08Z</updated>

		<summary type="html">&lt;p&gt;Vananasun: Preventing people having petty issues with getting the plugin bridge to work like I had&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you want to get involved with OpenMPT development, or just want to compile your own version of the tracker, here are some hints on how to get started.&lt;br /&gt;
&lt;br /&gt;
== Prerequisites ==&lt;br /&gt;
&lt;br /&gt;
* Visual Studio 2017 or later (any edition will work).&lt;br /&gt;
* &#039;&#039;Optional&#039;&#039; [https://tortoisesvn.net/downloads.html TortoiseSVN] or any other SVN client. You will need this to get the latest code revision via the [https://en.wikipedia.org/wiki/Apache_Subversion SVN] system. The description below is written for TortoiseSVN. You can also download a code snapshot if you do not want to install a SVN client (see below).&lt;br /&gt;
&lt;br /&gt;
== Getting the code ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Using TortoiseSVN:&#039;&#039;&#039; First, you have to create a directory on your hard drive in which you want to place the source code. Right-click on the directory and choose the context menu entry “SVN Checkout...”. The “Repository URL” to fill in is &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://source.openmpt.org/svn/openmpt/trunk/OpenMPT/&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;. After clicking the OK button, all files will be downloaded.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- or -&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Tarball:&#039;&#039;&#039; If you do not want to use an SVN client, simply get the GNU tarball from the [https://source.openmpt.org/browse/openmpt/trunk/ web interface] - click the “Download” link next to the &amp;lt;code&amp;gt;OpenMPT&amp;lt;/code&amp;gt; folder to retrieve it.&lt;br /&gt;
&lt;br /&gt;
Once you have checked out, you can always right-click on the directory and choose “SVN Update...” to get the most recent revision of the code. This will of course not work with the tarball method, you will have to download a new tarball after every commit in that case.&lt;br /&gt;
&lt;br /&gt;
== Compiling the code ==&lt;br /&gt;
&lt;br /&gt;
Detailed instructions on how to obtain some of the optional dependencies and how to compile the code can be found in the [https://source.openmpt.org/svn/openmpt/trunk/OpenMPT/README.md README.md] file found at the project′s root directory.&lt;br /&gt;
&lt;br /&gt;
== Note on using the plugin bridge ==&lt;br /&gt;
&lt;br /&gt;
When building the plugin bridge in order to load non-native plugins make sure you build it for both 32- and 64-bit architectures.&lt;br /&gt;
&lt;br /&gt;
== Staying up to date ==&lt;br /&gt;
&lt;br /&gt;
If you want to be notified of new code commits, you can import the [https://source.openmpt.org/browse/openmpt/trunk/OpenMPT/?op=rss&amp;amp;isdir=1&amp;amp; RSS feed] into your favourite RSS reader or subscribe to the [https://lists.sourceforge.net/lists/listinfo/modplug-svn-commit SVN mailing list].&lt;br /&gt;
&lt;br /&gt;
[[Category:Development|Compiling the code]]&lt;br /&gt;
[[de:Ressourcen: Sourcecode]]&lt;/div&gt;</summary>
		<author><name>Vananasun</name></author>
	</entry>
</feed>