Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Not 100% sure for a cmake file but this is from an old VS 6 makefile modified for Devpartner. Perhaps you can post a relevant section of the makefile for me to look at. </p> <p>/nmbcon is a compile flag that says use BC instrumentation /nmtxon would be used for coverage analysis</p> <p>CPP=cl.exe</p> <p>CPP_PROJ=/nologo /MD /W3 /Gm /GX /Zi /Od /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_WINDLL" /D "_AFXDLL" /D "_MBCS" /D "_AFXEXT" /Fp"$(INTDIR)\main.pch" /Yu"stdafx.h" /Fo"$(INTDIR)\" /Fd"..\bin\Debug\MAIN.pdb" /FD /GZ /c</p> <p>Would become</p> <p>CPP=nmcl.exe</p> <p>CPP_PROJ= /nmbcon /nologo /MD /W3 /Gm /GX /Zi /Od /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_WINDLL" /D "_AFXDLL" /D "_MBCS" /D "_AFXEXT" /Fp"$(INTDIR)\main.pch" /Yu"stdafx.h" /Fo"$(INTDIR)\" /Fd"..\bin\Debug\MAIN.pdb" /FD /GZ /c </p> <p>Oh and the other poster is correct things have greatly changed by version of Visual Studio. VS2010 changed the build process to use MSBuild this caused us to completely modify the way we intercept and instterument for VS2010 and 2012.</p> <p>*<strong><em>EDIT</em></strong></p> <p>Well I did download and go through the <em>pain</em> of Cmake internship this morning. For VS2010 this seems to be a pretty simple modification just like would be needed for one of our users using MSBuild from the command line.</p> <p>In the out dir "Where to build the binaries" after the first build there will be .vcxproj.user files. This is where you need to add the flags for instrumentation</p> <pre><code>&lt;?xml version="1.0" encoding="utf-8"?&gt; &lt;Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"&gt; &lt;PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'"&gt; &lt;DevPartner_IsInstrumented&gt;1&lt;/DevPartner_IsInstrumented&gt; &lt;DevPartner_Instrumented_Type&gt; /NMbcOn&lt;/DevPartner_Instrumented_Type&gt; &lt;/PropertyGroup&gt; &lt;/Project&gt; </code></pre> <p>This can be a repeating section for each that you wish to build.</p> <p>The next key DevPartner_IsInstrumented tells us to instrument (1) or not (0). The last key DevPartner_Instrumented_Type> is what type to instrumetnt /nmbcon (Boundschecker) /nmtxon (Performance or Coverage) or both keys passed.</p> <p>So it could look like</p> <pre><code>&lt;Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"&gt; &lt;PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'"&gt; &lt;DevPartner_IsInstrumented&gt;1&lt;/DevPartner_IsInstrumented&gt; &lt;DevPartner_Instrumented_Type&gt; /NMbcOn&lt;/DevPartner_Instrumented_Type&gt; &lt;/PropertyGroup&gt; &lt;PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'"&gt; &lt;DevPartner_IsInstrumented&gt;0&lt;/DevPartner_IsInstrumented&gt; &lt;DevPartner_Instrumented_Type&gt; /NMbcOn&lt;/DevPartner_Instrumented_Type&gt; &lt;/PropertyGroup&gt; &lt;PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'"&gt; &lt;DevPartner_IsInstrumented&gt;0&lt;/DevPartner_IsInstrumented&gt; &lt;DevPartner_Instrumented_Type&gt; /NMbcOn&lt;/DevPartner_Instrumented_Type&gt; &lt;/PropertyGroup&gt; &lt;PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'"&gt; &lt;DevPartner_IsInstrumented&gt;1&lt;/DevPartner_IsInstrumented&gt; &lt;DevPartner_Instrumented_Type&gt; /NtxcOn&lt;/DevPartner_Instrumented_Type&gt; &lt;/PropertyGroup&gt; &lt;/Project&gt; </code></pre> <p>which would be Boundschecker for Debug win32, nothing for Release win32, nothing for debug x64 and Performance / Coverage for release x64</p> <p>If IsInstrumented 0 whatever is in the type will not matter as it will not be passed.</p> <p>FYI if you open the solution in VS2010 and turn instrumentation on this will be added to the vcxproj.user files for you. And the instrumentation settings are by project / config as well.</p> <p>If not using VS2010 my note below might be correct for those versions. </p> <p>For full disclosure I am the lead developer on the instrumentation engine for DevPartner. </p>
    singulars
    1. This table or related slice is empty.
    1. POHow do I change the compiler and CXX_FLAGS for CMAKE of a C++ project?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMark Levis
    1. USMark Levis
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COOK. So selecting the project to be instrumented from DevPartner->Instrumentation Manager has no effect on the vcxproj.user file. In fact, if I select the project to be instrumented from the "Check projects to be instrumented" section in the dialog, click OK and then reopen the Instrumentation Manager Dialog, those checked boxes were not persisted.
      singulars
      1. PO
      1. USJohnB
    2. COI will attempt to make the changes by hand directly to the project to the vxproj.user file. I'm not clear on how this going to cause the nmcl compiler and associated flags to be set.
      singulars
      1. PO
      1. USJohnB
    3. COWell that is a some of the beauty of MSBuild. in C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\Win32\ImportBefore you will see a few files in the targets file it shows that it will change the "CLCompileTool" if the one flag is set to "1". It will append the other flag as a compile switch. There is another set of these files in the X64 directory as well. As these are import before they are pulled into the build process before compile time by the targets in the directory above this. Believe me this was very fun to figure out how to integrate into MSBuild in the first place.
      singulars
      1. PO
      1. USMark Levis
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload