Visual C++ project (.vcxproj) files

[Neil Hodgson]

   There has been some demand for Visual Studio project files for Scintilla and SciTE, which I've denied in the past due to Microsoft churning project file formats. .vcxproj files can be written that work over 4 Visual Studio releases (2008, 2010, 2012 and 2013) so I'd like to include SciLexer.vcxproj (but no Scintilla.vcxproj) and SciTE.vcxproj (single EXE like Sc1) with their respective projects.

   These are (mostly) handwritten files to allow the use of wildcards so they will adapt to adding and removing lexers and also to avoid repeating definitions.

  A problem with publishing .vcxproj files is that they hard-code as PlatformToolset a specific compiler version number. If, for example, SciLexer.vcxproj includes <PlatformToolset>v110</PlatformToolset> where v110 is Visual C++ 2012, then Visual C++ 2010 will refuse to build until it is changed (through a properties sheet) to v100 or earlier. Likewise, open in Visual Studio 2013 and the earlier compiler from Visual C++ 2012 will be used if installed. Its probably best to specify the most recent generally available compiler (currently v120), although I can see this leading to support requests.

   The two project files are attached. Since the use relative paths they should be placed in the win32 directory of their projects. Configurations for 32-bit and 64-bit builds for both debug and release are included in the project files.

   Neil

[Neil Hodgson]

Neil Hodgson:

> The two project files are attached. Since the use relative paths they should be placed in the win32 directory of their projects. Configurations for 32-bit and 64-bit builds for both debug and release are included in the project files.

These files are now included in the repository.

Neil