Skip to content

vaasdevteam/gmod-module-base

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

31 Commits
 
 
 
 
 
 
 
 

Repository files navigation

gmod-module-base

Technically everything you need is in include.

Example contains an example project. Running BuildProjects.bat requires premake5 (https://premake.github.io/download.html). The example folder contains a ProjectConfig.lua which is meant to make the setting up of your project much easier for some people. Most config options won't matter to you unless you know what your doing with them, the important portions are the source code folder, if its server side, client or shared and the project name.

The generated dlls should be placed in: garrysmod/lua/bin/

Module located in lib folder after building it. They should also be named approriately: gmsv_vaas_example_win32.dll <- require('vaas_example') serverside on windows gmsv_vaas_example_linux.dll <- require('vaas_example') serverside on linux gmsv_vaas_example_osx.dll <- require('vaas_example') serverside on osx

gmcl_vaas_example_win32.dll <- require('vaas_example') clientside on windows gmcl_vaas_example_osx.dll <- require('vaas_example') clientside on osx

gm_vaas_example_win32.dll <- require('vaas_example') clientside on windows, be sure to name it to either gmcl_ or gmsv_ first gm_vaas_example_linux.dll <- require('vaas_example') clientside on linux, be sure to name it to either gmcl_ or gmsv_ first

About

Updated base interface to create binary modules for Garry's Mod, supporting vs2019 and premake5 out of the box

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages

  • C++ 74.7%
  • Lua 12.8%
  • C 11.8%
  • Batchfile 0.7%