Difference between revisions of "Compiling SourceMod Plugins"
Stridemann (talk | contribs) |
|||
| Line 3: | Line 3: | ||
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]. | 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]. | ||
| − | 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 | + | 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]. |
In Windows, open up a command prompt (Start->Run or WindowsKey+R, then "cmd"): | In Windows, open up a command prompt (Start->Run or WindowsKey+R, then "cmd"): | ||
| Line 15: | Line 15: | ||
./compile.sh myplugin.sp | ./compile.sh myplugin.sp | ||
| − | Now simply move the .smx (not .sp) file from | + | Now simply move the .smx (not .sp) file from sourcemod/scripting/compiled/ to the sourcemod/plugins/ folder. |
| − | '''Note:''' When compiling preexisting plugins it is easiest to move the included from the plugin source folder to the include folder in your | + | '''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. |
[http://forums.alliedmods.net/showthread.php?t=52664 Reference Source] | [http://forums.alliedmods.net/showthread.php?t=52664 Reference Source] | ||
See Also: [http://forums.alliedmods.net/forumdisplay.php?f=107 Scripting Forum] | See Also: [http://forums.alliedmods.net/forumdisplay.php?f=107 Scripting Forum] | ||
Revision as of 03:30, 28 January 2013
Okay, so you've read the Introduction to SourcePawn and Introduction to SourceMod Plugins and now you want to actually compile a plugin.
The simplest way to compile a plugin that doesn't rely on any custom include files is using the web compiler.
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 SourceMod distribution.
In Windows, open up a command prompt (Start->Run or WindowsKey+R, then "cmd"):
cd <sourcemod>\scripting spcomp myplugin.sp
Alternatively, you can simply drag the .sp file on top of spcomp.exe, which will compile the plugin for you.
In Linux use:
./compile.sh myplugin.sp
Now simply move the .smx (not .sp) file from sourcemod/scripting/compiled/ to the sourcemod/plugins/ folder.
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.
See Also: Scripting Forum
