This repository has been archived by the owner on Apr 19, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 94
Building with VS2015 Community
Chris West edited this page Dec 13, 2015
·
2 revisions
- Install a git client (e.g. Github for Windows) and obtain a copy of the PuTTYTray code.
- Install Visual Studio 2015 Community. There's no reason the build shouldn't work with non-Community versions, but it's not been tested.
- You will need the "C++"-related features and the tools for building "Desktop applications for Windows 8.1".
- Install a perl interpreter, such as Strawberry Perl.
- 5.18 tested, but newer versions should work.
- The one shipped with msysGit does not have the necessary modules.
- The cygwin one has had issues in the past, so you might want to avoid it.
- Start a command prompt in the PuTTYTray directory, and run
perl mkfiles.pl
. This should print nothing, and create a load of files. - You can open PuTTYTray\windows\VS2012\putty.sln in VS2015.
- It will ask you to "Upgrade VC++ Compiler and Libraries", which you want to do.
- Right-click "putty" (not "plink") in the Solution Explorer, and choose "Set as startup project".
- Press "▶ Local Windows Debugger" (
F5
). - PuTTY should start, although it will lack proper themes.
- You might have to tell Visual Studio it where the 8.1 header files are (because it's rubbish), or it will complain it can't find
winsock2.h
: - Open the "putty" project properties.
- VC++ directories.
- Add
C:\Program Files (x86)\Windows Kits\8.1\Include\shared
andC:\Program Files (x86)\Windows Kits\8.1\Include\um
to the "Include Directories". - Alternatively, you can use the command-line build:
- Start the "Developer Command Prompt for VS2015", previously known as "Windows SDK X.X Command Prompt", or "Visual Studio (XXX) Command Prompt".
cd windows
build-debug
- This should eventually emit a
putty.exe
, which you can run or debug. - The release script requires a version, and will attempt to sign the build, etc. If you want to investigate further, I suggest running nmake by hand.