Age | Commit message (Collapse) | Author | |
---|---|---|---|
2019-09-14 | Specify solution zlib dependencies | Yasha Jannoo | |
Set zlib as a dependency for a number of solution projects, presumably to help decide the build order. | |||
2019-09-14 | Update zlib 3rd party code to v1.2.11 | Yasha Jannoo | |
zlib source code, version 1.2.11. https://www.zlib.net/. Include all the gynmastics involved in: - making sure we compile zlibstat and set the output files locations and filename to those expected by the starshatter setup. - turning off the ASM includes as they are invalid for the new versions of zlib (and crash when running). - matching the calling conventions of the Starshatter code by ommiting ZLIB_WINAPI from the zlib preprocessor defines. - fix debug build compile error in zlibstatic: https://stackoverflow.com/questions/31867018/unresolved-external-symbol-except-handler4-common-in-visual-studio-2015 This fixes some string warnings. | |||
2019-09-12 | Fix ill-formed and warning-causing new overloaded and delete operators | Yasha Jannoo | |
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. | |||
2019-09-10 | Turn off edit and continue. | Yasha Jannoo | |
Fixes incompatibility between /ZI and /Gy- by not allowing ZI at all for the time-being. We can turn it on again later. | |||
2019-09-10 | Turn off Minimal Rebuild across the board | Yasha Jannoo | |
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. | |||
2019-09-10 | Revert "Turn off Minimal Rebuild across the board" | Yasha Jannoo | |
This reverts commit f935fb0960b1563d6404d2fec21963b20f498a3b. | |||
2019-09-10 | Turn off Minimal Rebuild across the board | Yasha Jannoo | |
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. | |||
2019-09-10 | Remove FORCE flag from Stars project | Yasha Jannoo | |
We shouldn't hide potential issues and it seems to be compiling okay without. | |||
2019-09-09 | Naively turn off UseOfMfc | Yasha Jannoo | |
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. | |||
2019-09-09 | Address Magic DXDK build error | Yasha Jannoo | |
Following the advice on https://stackoverflow.com/questions/38174893/syntax-error-identifier-dxgi-rgba-in-file-dxgi1-2-h stating "if you want to mix the old DirectX SDK with the Windows 8.x SDK, you need to invert the traditional include path order.", choose to support the newest DirectX SDK (included in the Win10 SDK) by following it. The advice references https://docs.microsoft.com/en-us/windows/win32/directx-sdk--august-2009- which we should take into account for later changes. | |||
2019-09-05 | Retarget for new MSBuild toolsets | Yasha Jannoo | |
Retarget all projects in the Starshatter.sln from v110 (VS12) to v141 (VS17) | |||
2019-09-05 | Create .gitignore | Yasha Jannoo | |
Track gitignore. | |||
2015-03-26 | Create README.md | Kimmo Kotajärvi | |
2013-07-10 | Updating the project files so that building works again | fwoltermann@gmail.com | |
2013-07-07 | Removed unused Authorization class. | milo24x7@gmail.com | |
2013-07-07 | Updated open source license declaration and fixed some formatting issues. | milo24x7@gmail.com | |
2013-07-07 | Updated open source license declaration and fixed some formatting issues. | milo24x7@gmail.com | |
2013-07-07 | Updated open source license declaration and fixed some formatting issues. | milo24x7@gmail.com | |
2013-07-07 | Updated open source license declaration and fixed some formatting issues. | milo24x7@gmail.com | |
2013-07-07 | Updated open source license declaration and fixed some formatting issues. | milo24x7@gmail.com | |
2013-07-07 | Updated open source license declaration and fixed some formatting issues. | milo24x7@gmail.com | |
2013-07-07 | Updated open source license declaration and fixed some formatting issues. | milo24x7@gmail.com | |
2012-07-22 | PVS-Studio fix: V592 The expression was enclosed by parentheses twice: '((t ↵ | rhyskidd@gmail.com | |
- h * HOUR - m * MINUTE))'. One pair of parentheses is unnecessary or misprint is present. | |||
2012-07-22 | PVS-Studio fix: V547 Expression is always true. Probably the '&&' operator ↵ | rhyskidd@gmail.com | |
should be used here. starshiptacticalai.cpp 205 | |||
2012-07-16 | PVS Studio warning: Cast from false to int | FWoltermann@gmail.com | |
2012-07-16 | Ignore PVS Studio warning V576 | FWoltermann@gmail.com | |
2012-07-16 | PVS Studio Warning fix: Part of conditional expression is always false | FWoltermann@gmail.com | |
2012-07-16 | PVS Studio warning fix: Part of conditional expression is always true (Note ↵ | FWoltermann@gmail.com | |
to self: this code is weeeeeiiird around line 221....) | |||
2012-07-16 | PVS Studio warning fix: Part of conditional expression is always false | FWoltermann@gmail.com | |
2012-07-16 | PVS Studio warning fix: Possible Array underrun | FWoltermann@gmail.com | |
2012-07-16 | PVS Studio fix: Comparison using || is always true, using && instead | FWoltermann@gmail.com | |
2012-07-16 | PVS Studio fix: m_pos < 0 can never be true | FWoltermann@gmail.com | |
2012-07-16 | PVS Studio warning fix: Unconditional break/return | FWoltermann@gmail.com | |
2012-07-16 | PVS Studio warning fix: Null pointer dereference when accessing msg | FWoltermann@gmail.com | |
2012-07-16 | PVS-Studio fix: V624 The constant 3.1415 is being utilized. The resulting ↵ | rhyskidd@gmail.com | |
value could be inaccurate. Consider using the M_PI constant from <math.h>. mission.cpp 1203 | |||
2012-07-16 | PVS-Studio fix: V618 It’s dangerous to call the 'sprintf_s' function in ↵ | rhyskidd@gmail.com | |
such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |||
2012-07-16 | PVS-Studio fix: V625 Consider inspecting the 'for' operator. Initial and ↵ | rhyskidd@gmail.com | |
final values of the iterator are the same. layout.cpp Due to changes in revision 51. | |||
2012-06-24 | A few PVS studio things5.1.87 | FWoltermann@gmail.com | |
2012-06-17 | (Hopefully) Allows SWACS ships to do more than sit around. Needs testing. | FWoltermann@gmail.com | |
2012-06-13 | One of these days, I'ma be done with project file updates | FWoltermann@gmail.com | |
2012-06-13 | Add a quick return here before we deref a null pointer | FWoltermann@gmail.com | |
2012-06-13 | Remove dependency on content.dat (The file is still required, since it was ↵ | FWoltermann@gmail.com | |
part of the last patch, but the exe will no longer fail if it isn't present) | |||
2012-06-13 | Remove a bit of commented-out code | FWoltermann@gmail.com | |
2012-06-08 | Ooops, stupid mistake here. | FWoltermann@gmail.com | |
2012-06-06 | More project file fixes | FWoltermann@gmail.com | |
2012-06-06 | Fix a potential invalid memory access issue | FWoltermann@gmail.com | |
2012-06-06 | Aaaand more VS2012 compat stuff. | FWoltermann@gmail.com | |
2012-06-06 | (no commit message) | rhyskidd@gmail.com | |
2012-06-06 | Another piece of the VS2012 compatibility puzzle | FWoltermann@gmail.com | |
2012-06-06 | Fix was accidentally reverted in r73, re-inserting | rhyskidd@gmail.com | |