Age | Commit message (Collapse) | Author |
|
One fix to the LuaJIT2 project generation ... binaries ended up outside the
top-level folder.
A handful of code sanity changes.
Updated SQLite3 to 3.30.1
|
|
|
|
Fixed up produce_vsprojects.cmd to heed the command line arguments
Reverted to original RGB_GET_?VALUE macros to prevent an exception in debug builds
Removing more parts referring to the CHM help file
Removing WEAK_ASSERT
Using --full to produce the checked in solutions
Fixed constant length to account for terminating zero
|
|
updates to 3rd party libs
* New SQlite amalgamation
* Updating other third-party libs
* New premake4.exe
* Fixes to the premake4.lua script and projects
* Adding language resource projects to solutions
* Some sanity checks added to treemap.cpp
* Using refs now instead of pointers in treemap.cpp (probably should be reviewed as it looks like there are more candidates in there)
* Added Windows 10 to manifest file
* Glitch in stdafx.h corrected
* Script which produces the projects now defaults to only VS2005 and VS2017
* Deterministic filter UUIDs for VS201x
* Fixed a handful of issues in code addressed
* XP platform toolset doesn't allow for code analysis, using default again
* Addressed a number of warnings from code analysis
|
|
Updated premake4.exe binary (again code-signed)
Updated setvcvars.cmd script
Adding projects missing from the VS2015 solution, migrated to VS2017 solution and projects
All VS201x projects now include UTF-8 BOM upon generation
premake4.lua now allows to generate v1??_xp projects for newer VS versions
Updated two more .cmd scripts to make use of the --xp option to the premake4.lua
|
|
|
|
|
|
Adjusted the script which creates the projects based on premake4.lua
|
|
Studio only
|
|
|
|
premake/premake-stable
|
|
|