https://wiki.alliedmods.net/api.php?action=feedcontributions&feedformat=atom&user=Stridemann 2026-06-06T10:26:09Z User contributions MediaWiki 1.31.6 https://wiki.alliedmods.net/index.php?title=Compiling_SourceMod_Plugins&diff=8421 2012-03-24T19:52:50Z

<p>Stridemann: </p> <hr /> <div>Okay, so you've read the [[Introduction to SourcePawn]] and [[Introduction to SourceMod Plugins]] and now you want to actually compile a plugin.<br /> <br /> The simplest way to compile a plugin that doesn't rely on any custom include files is using the [http://www.sourcemod.net/compiler.php web compiler].<br /> <br /> Alternatively, you can use the executable compiler distributed with SourceMod. You can use this simply if you like compiling locally rather than using the web compiler. You have to use the local compiler if your plugin relies on custom include files. The compiler is included in the .../sourcemod/scripting/ folder of the [http://www.sourcemod.net/downloads.php SourceMod distribution].<br /> <br /> In Windows, open up a command prompt (Start-&gt;Run or WindowsKey+R, then &quot;cmd&quot;):<br /> cd &lt;sourcemod&gt;\scripting<br /> spcomp myplugin.sp<br /> [http://www.computerhope.com/cdhlp.htm cd command reference]<br /> <br /> Alternatively, you can simply drag the .sp file on top of spcomp.exe, which will compile the plugin for you.<br /> <br /> In Linux use:<br /> ./compile.sh myplugin.sp<br /> <br /> Now simply move the .smx (not .sp) file from .../sourcemod/scripting/ to the .../sourcemod/plugins/ folder.<br /> <br /> '''Note:''' When compiling preexisting plugins it is easiest to move the included from the plugin source folder to the include folder in your Sourcemod\scripting\include. Please see [[Spcomp_switches]] specifically the ''-i'' parameter for specifying a different folder for includes.<br /> <br /> [http://forums.alliedmods.net/showthread.php?t=52664 Reference Source]<br /> <br /> See Also: [http://forums.alliedmods.net/forumdisplay.php?f=107 Scripting Forum]</div>

Stridemann