| title |
|---|
| (OBSOLETE) Compilation (premake branch) |
This page is OBSOLETE. If you want to properly compile the project - go to the Compilation page
However, if you still want to use this guide, please see Pulling repository page first
Additional steps
Locating Developer Command Prompt
Open a Start menu. Start typing "developer" in search. You should see a "Developer Command Prompt for VS2022" entry. Right-click on it and choose "Run as administrator". Confirm the pop-up dialog by pressing "Yes".
Using build system
Enter cd /d <path to your src_main folder> in the Developer Command Prompt.
Type compile. This will invoke steps such as creating a project files and solution, building them and symlinking to your game directory automatically.
To be more specific, you can use switches:
/premake - create all the projects and solution files
/build - build them all
/symlink - create symbolic links from a src_main\build directory to a game directory
After all the switches, you can specify which build configuration to use: Debug or Release.
For example:
compile Release - make a Release build
compile /symlink - (re-)symlink all the binaries (useful after you create additional projects)
compile without any switches and parameters internally runs compile /premake /build /symlink Debug
Running an IDE
Open a Start menu. Start typing "visual" in search. Right-click on "Visual Studio 2022" entry and choose "Run as administrator". Confirm the pop-up dialog by pressing "Yes".
Open an everything.sln solution, which is located at src_main folder. Make sure you've ran at least compile /premake before locating a solution file.
Locating freshly compiled binaries
After the build process finish you should see a build folder in your src_main. There goes all the compiled binaries, along with static libraries in "lib" folder.