Sha256: 0fdc0558e25fbf56d4d377ea89a195349ea606a97f5ed613bd3559325f7f9176
Contents?: true
Size: 1.74 KB
Versions: 17
Compression:
Stored size: 1.74 KB
Contents
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Documentation of the bake-tookit</title>
<style type="text/css">
#rundrum {
border-width:1px;
border-style:dashed;
border-color:blue;
padding:0.2cm;
text-align:justify; }
}
</style>
</head>
<body>
<h1>How to debug in Visual Studio</h1>
Natively you can only debug the output from the Microsoft VC compiler with Visual Studio. There are some plugins available for e.g.
debugging gcc output. Another option is to use the MSVC toolchain from bake, which is described on this help page.
<p>
Add debug flags to the MSVC toolchain:
<pre id="rundrum"><code>DefaultToolchain MSVC {
Compiler CPP {
Flags "-Zi"
}
Linker {
Flags "-Debug"
}
}</code></pre>
Start Visual Studio with e.g. a batch file shown below and choose the appropriate solution. If you don't have a solution yet, check out <a href="create.html">How to create a solution / projects in Visual Studio</a>.
<pre id="rundrum"><code>set PATH=%PATH%;C:\tools\Microsoft Visual Studio 11.0\VC\bin
call "C:\tools\Microsoft Visual Studio 11.0\VC\vcvarsall.bat"
"C:\tools\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe"</code></pre>
<p>
This adds the compiler, linker, etc. to the path. <i>vcvarsall.bat</i> setups the environment and the last line
starts Visual Studio. As a test, just execute the first two lines and check if "cl.exe" can be executed without any errors.
In Visual Studio, you have to define the executable you like to debug. Add the executable in the project properties:
<p>
<img src="echse/echse.png"/>
<p>
You can also define command line arguments here.<p>
Start debugging as usual...
</body>
</html>
Version data entries
17 entries across 17 versions & 1 rubygems