10 Commits

Author	SHA1	Message	Date
evoskuil	a3c3bcfe4a	Problem: visual c++ invalid ToolsVersion warnings.	2016-05-12 03:31:52 -07:00
Matt Powley	0e405a5a77	Use vs2015 MSBuild property sheets in older projects ... All the older (vs2010 -> vs2013) projects had copies of the Visual Studio 2015 MSBuild applied to them when running the 'configure.bat' batch file. Any modifications to a property sheet was not applied to the other Visual Studio versions' projects unless the batch file was re-executed. * Modified the older projects to reference the Visual Studio 2015 property sheets so changes are immediately applied * Removed the batch file copy steps (which left the repository very dirty after execution)	2016-03-31 14:51:23 +01:00
Dave Meehan	d775b4539f	Modified remote_thr project to not copy platform.hpp	2014-06-05 13:07:26 +01:00
Dave Meehan	451c94af8e	Fix for perf/platform.hpp not being cleaned up by distclean	2014-05-31 13:51:41 +01:00
evoskuil	3aa6c1eab0	Optimize VS projects and common props.	2014-05-13 03:17:48 -07:00
evoskuil	b0b6dd4043	Consolidate VS props to shared location.	2014-05-06 15:16:37 -07:00
evoskuil	d03a1b0d5b	Fix platform tools versioning on project files.	2014-04-14 19:19:30 -07:00
evoskuil	51be440a28	Update VS build configurations.	2014-04-09 03:27:27 -07:00
evoskuil	34f4851c23	Incorporate libsodium option and linkage, generalize, update packaging.	2014-04-07 19:38:59 -07:00
evoskuil	5d0701d71d	Add executable projects to VS2013 solution.	2014-04-04 01:17:25 -07:00