2010-10-24 19:34:46 +02:00
|
|
|
Cppcheck for 64-bit Windows
|
|
|
|
|
===========================
|
|
|
|
|
|
|
|
|
|
This is quick start to get you started with compiling Cppcheck for 64-bit
|
2010-10-25 18:40:08 +02:00
|
|
|
Windows with free VS Express editions. This is work in progress so these
|
|
|
|
|
instructions will be updated as we progress with the work...
|
2010-10-24 19:34:46 +02:00
|
|
|
|
|
|
|
|
Software needed:
|
2010-10-25 18:40:08 +02:00
|
|
|
- Visual Studio 2008 or 2010 Express edition
|
|
|
|
|
- Windows SDK 7.0 (for VS2008) or Windows SDK 7.1 (for VS2010)
|
2010-10-24 19:34:46 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
Cppcheck.exe
|
|
|
|
|
------------
|
|
|
|
|
|
2010-10-25 18:40:08 +02:00
|
|
|
Make sure you have the Windows SDK installed! VS Express doesn't have 64-bit
|
2010-10-24 19:34:46 +02:00
|
|
|
tools, libraries or headers so you cannot compile 64-bit binaries without
|
|
|
|
|
Windows SDK.
|
|
|
|
|
|
|
|
|
|
To compile 64-bit binaries you need to start VS Express to 64-bit environment.
|
|
|
|
|
(by default VS Express starts to 32-bit enviroment). To do this, open Windows
|
|
|
|
|
SDK Command Prompt and switch to 64-bit environment with command:
|
2010-10-25 18:20:23 +02:00
|
|
|
> setenv /x64 /debug
|
2010-10-24 19:34:46 +02:00
|
|
|
|
|
|
|
|
Then start VS Express:
|
2010-10-25 18:40:08 +02:00
|
|
|
> "C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\VCExpress" /useenv
|
2010-10-24 19:34:46 +02:00
|
|
|
|
2010-10-25 18:40:08 +02:00
|
|
|
VS Express starts otherwise normally but now all environment variables point to
|
|
|
|
|
64-bit folders for libraries.
|
2010-10-24 19:34:46 +02:00
|
|
|
|
2010-10-25 18:40:08 +02:00
|
|
|
Now you can open the cppcheck.sln (or cppcheck_vs2010.sln) solution file and
|
|
|
|
|
compile 64-bit targets. With VS 2008 there are configurations Debug-x64 and
|
|
|
|
|
Release-x64 for 64-bit targets. This is because VS 2008 express does not allow
|
|
|
|
|
adding new platform. For VS 2010 there is platform x64 and Debug/Release
|
|
|
|
|
configurations.
|
2010-10-24 19:34:46 +02:00
|
|
|
|
|
|
|
|
You can use e.g. Dependency Walker -program (http://www.dependencywalker.com/)
|
|
|
|
|
to check that build binaries are really 64-bit binaries.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
GUI
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
Software needed:
|
2010-10-25 23:10:14 +02:00
|
|
|
- Visual Studio 2008 or 2010 Express edition
|
|
|
|
|
- Windows SDK 7.0 (for VS2008) or Windows SDK 7.1 (for VS2010)
|
2010-10-24 19:34:46 +02:00
|
|
|
- latest Qt SDK (4.7.0 or later, earlier versions don't support VS 2010)
|
|
|
|
|
|
2010-10-25 23:10:14 +02:00
|
|
|
Turns out you just need to use Windows SDK's Command prompt and 64-bit
|
|
|
|
|
environment to configure and build Qt. No extra steps needed. But of course you
|
|
|
|
|
should build 64-bit Qt to different folder than 32-bit Qt.
|
|
|
|
|
|
2010-10-26 18:25:35 +02:00
|
|
|
Compiling 64-bit GUI works fine from Windows SDK Console. But seems there is no
|
|
|
|
|
easy way to make it work with VS 2008 Express IDE. With VS2010 Express IDE
|
|
|
|
|
everything works fine after adding new x64 platform for the project.
|
