| Age | Commit message (Collapse) | Author |
|---|
|
From VS2015 onwards, overloaded new and delete operators were no longer allowed to be declared inline. See https://docs.microsoft.com/en-us/cpp/porting/visual-cpp-what-s-new-2003-through-2015?view=vs-2019.
As a consequence of moving the definitions into source files, we cannot simply include the headers in the files they are required in without also either creating a static library or including the source files in the projects. Do the latter as the pattern fits other examples of dependencies across projects in the solution.
The overloaded operator definitions could be made neater in a future change. For now they are written as their declarations appear in the header file, with the same ifdefs as in the header file.
|
|
Fixes incompatibility between /ZI and /Gy- by not allowing ZI at all for the time-being. We can turn it on again later.
|
|
This is the \Gm compiler flag. There are warnings that this is deprecated, and the general advice is that setting the multiprocessor build flag should be used instead.
|
|
This reverts commit f935fb0960b1563d6404d2fec21963b20f498a3b.
|
|
This is the \Gm compiler flag. There are warnings that this is deprecated, and the general advice is that setting the multiprocessor build flag should be used instead.
|
|
We shouldn't hide potential issues and it seems to be compiling okay without.
|
|
In addressing the complaint here,
https://www.hard-light.net/forums/index.php?topic=80935.msg1853522#msg1853522
I have decided to include all the standard libraries for the debug build in the same way that the retail build does. I don't have enough information to know why this is different, but I could not resolve my build issues by instead adding more required libraries to the "Linked Dependencies". I could retry this solution later and roll this back.
|
|
Retarget all projects in the Starshatter.sln from v110 (VS12) to v141 (VS17)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
environment variable with the name "STARSHATTERPATH" pointing to the directory where Starshatter is installed (C:\Matrix Games\Starshatter by default), builds will automatically be copied there once compilation is finished.
|
|
builds
|
|
Do note that it is possible to compile Starshatter.exe now.
|
|
|
|
|
