5.2 KiB
Raw Permalink Blame History

Building Volt

Note: This repository can be built with the default SDK but will not be outlined in this guide.
Note: x64 platform builds will also not be outlined in this guide.

All build instructions start the same. Clone a local copy of mini-source-sdk. (A minified version of Source SDK with support for Linux and added support for Visual Studio 2022 and the Windows 11 SDK)

git clone https://github.com/Joshua-Ashton/mini-source-sdk.git

Following your clone of the mini-source-sdk, navigate to the "version" you would like to build (sdk2013-mp, sdk2013-sp, asw). As an example, the multiplayer version will be used from now on.

cd mini-source-sdk/sdk2013-mp/src/

At this time you should now recursively git clone the VPhysics-Jolt repository into your "src" directory.

git clone --recursive https://github.com/Joshua-Ashton/VPhysics-Jolt.git vphysics_jolt

From this point onward, please follow the rest of the guide specific to your chosen build platform. The current working directory is also assumed to be mini-source-sdk/sdk2013-mp/src/ and should be adjusted to suit your own build if need be.


Continuing on Windows, be sure you have both Visual Studio 2022 and the Windows 11 SDK installed on your system. (even if you run Windows 10 the SDK still applies)


The next step is to run the fix registry script (as administrator). You can just Right-Click -> 'Run As Administrator' the fix_registry.bat file located in mini-source-sdk/sdk2013-mp/src/. If your command prompt or powershell instance are already running under administrator you can run the script from there:


This is the final command to run before the CLI portion of this guide ends. It will generate your Visual Studio project/solution file(s). (You may also just Double-Click the file createjoltprojects.bat)


Visual Studio

After running createjoltprojects.bat you should now have a file named jolt.sln. Open it. After opening, building should be simple. Press the shortcut Ctrl+Shift+B OR find the Solution 'jolt' bar in the Solution explorer window and Right-Click -> Build Solution.


The built vphysics_jolt.dll file should now be located in mini-source-sdk/sdk2013-mp/game/bin/.

Build errors

Common build errors you may run into building on Windows and their solutions.


If there is an error involving a symbol named size_t _msize or size_t __cdecl _msize_base, it is most likely because you haven't updated your Windows SDK to the Windows 11 SDK. Please do so. If you still get this error make sure that your Visual Studio projects also default to the latest installed version if they don't already.


Continuing on Linux, there are a few prerequisites to building regardless of distribution.

  • gcc 10+
  • g++ 10+
  • gcc-multilib
  • g++-multilib
  • make


Note: Certain versions may also require version explicit packages (gcc/g++ 10 may not be the default installed version).

Before we continue building project files, lets get our dependencies out of the way. Install the build-essential group to get common developer packages such as gcc, g++, and make, which are included.

sudo apt install build-essential

After installing the build-essential group packages, we now need to install the x86 dependencies.

sudo apt install gcc-multilib g++-multilib

The next step is to build our makefiles by running the premade script createjoltprojects.sh


Once the script has finished running you should now have a file name jolt.mak in the current directory. Verify you do and now run it with the command below. This command automatically will (and is recommended to) use all available CPU threads. If you want to specify it yourself, replace $(nproc) with a number less than or equal to your max number of threads. To be clear, this only affects compile speed.

make -j $(nproc) -f jolt.mak

Alternative example...

make -j 8 -f jolt.mak


If the console outputs LINKING and COPYING TO messages, that means your build was successful and you may retrieve your vphysics_jolt.so and vphysics_jolt_srv.so files which will be located in mini-source-sdk/sdk2013-mp/game/bin/.

Build errors (distribution independent)

Common build errors you may run into building on Linux and their solutions.

error: unrecognized command line option -std=gnu++20; did you mean -std=gnu++2a? (make: *** [jolt.mak:28: all] Error 2)

This error is caused because the compile was not started with gcc/g++ v10 or higher. Please update.