Reduce pain points with Visual Studio
commitda31531db7588f1d7aa6d1a318694b7153efcbb0
authorjohnstevenson <john-stevenson@blueyonder.co.uk>
Sun, 10 Nov 2013 14:19:24 +0000 (10 14:19 +0000)
committerjohnstevenson <john-stevenson@blueyonder.co.uk>
Mon, 11 Nov 2013 18:21:09 +0000 (11 18:21 +0000)
tree8f0f71dbe21220949218092d9359c872bab4e97d
parentcb2350903c783fbb00232f59831f49527983849a
Reduce pain points with Visual Studio

There are plenty of hoops to jump through before you can build
and debug using Visual Studio. Even more if you then want to
contribute any changes back.

This pain can be alleviated by providing a single project file
(suitable for Visual Studio 2010 upwards), removing the use of
make in the build process and bypassing the version info mechanism.

Maintainability over different versions is aided by the code being
in a single project file with most properties being controlled by
external property sheets.

Signed-off-by: johnstevenson <john-stevenson@blueyonder.co.uk>
explorer/cheetah.def [new file with mode: 0644]
explorer/visualstudio/.gitignore [new file with mode: 0644]
explorer/visualstudio/README.txt [new file with mode: 0644]
explorer/visualstudio/cheetah.vcxproj [new file with mode: 0644]
explorer/visualstudio/cheetah.vcxproj.filters [new file with mode: 0644]
explorer/visualstudio/props/Cheetah.Debug.Win32.props [new file with mode: 0644]
explorer/visualstudio/props/Cheetah.Debug.x64.props [new file with mode: 0644]
explorer/visualstudio/props/Cheetah.Release.Win32.props [new file with mode: 0644]
explorer/visualstudio/props/Cheetah.Release.x64.props [new file with mode: 0644]