Highlighted
Phil1 Absent Member.
Absent Member.
2916 views

BoundsChecker Instrumentation -- automated builds

Jump to solution

[Migrated content. Thread originally posted on 13 May 2011]

We used bounds checker 10 or so years ago and had a difficult time getting automated nightly builds going. We had to create specific profiles and visual studio macros to tweak the process. We have just downloaded the most recent DevPartner product and are testing it with vs 2008 (and soon to be 2010). The product looks great but we have not had success getting an automated build going with the standard /DEBUG profile. We have looked at the documentation and tried nmc, nmlink, and nmvcbuild. Are there any examples for automating this process without creating a custom profile?
Thank you
0 Likes
1 Solution

Accepted Solutions
mlevis Absent Member.
Absent Member.

RE: BoundsChecker Instrumentation -- automated builds

Jump to solution
With VS2008 there are a few different things you could try.

One is to open the soloution and create a new "configuration" like "Debug BC" and then use Devpartner / Instrumentation manager to set that projects in that configuration to instrument. This will modify the vcproj files for the projects in that soloution though. They will need to be checked out and checked back into source control.

Another option is to use the "new" nmdevenv.exe that is also in the \nmshared\cti\10.5 directory with nmcl, nmvcbuild and so on. You can use that just as you would with calling devenv to build a soloution / project. You just need to pass in the instrumentation option /nmbcon / nmtxon or both.

Hope those help you or at least get you going in the right direction. If not then maybe a little more information on the specifics could help us determine exactly what you need. Lastly you open a support ticket and we can setup a conference call to discuss the specifics there as well.

Thanks for continuing to be a DevPartner customer / user.
0 Likes
4 Replies
mlevis Absent Member.
Absent Member.

RE: BoundsChecker Instrumentation -- automated builds

Jump to solution
With VS2008 there are a few different things you could try.

One is to open the soloution and create a new "configuration" like "Debug BC" and then use Devpartner / Instrumentation manager to set that projects in that configuration to instrument. This will modify the vcproj files for the projects in that soloution though. They will need to be checked out and checked back into source control.

Another option is to use the "new" nmdevenv.exe that is also in the \nmshared\cti\10.5 directory with nmcl, nmvcbuild and so on. You can use that just as you would with calling devenv to build a soloution / project. You just need to pass in the instrumentation option /nmbcon / nmtxon or both.

Hope those help you or at least get you going in the right direction. If not then maybe a little more information on the specifics could help us determine exactly what you need. Lastly you open a support ticket and we can setup a conference call to discuss the specifics there as well.

Thanks for continuing to be a DevPartner customer / user.
0 Likes
Phil1 Absent Member.
Absent Member.

RE: BoundsChecker Instrumentation -- automated builds

Jump to solution
this looks to be exactly what we are looking for. We have our automated, instrumented builds going now and will continue to test. Thank you
0 Likes
mlevis Absent Member.
Absent Member.

RE: BoundsChecker Instrumentation -- automated builds

Jump to solution
Great news Phil. Let us know if you have any other questions.

Mark
0 Likes
mlevis Absent Member.
Absent Member.

RE: BoundsChecker Instrumentation -- automated builds

Jump to solution

One thing to keep in mind when moving to VS2010 is that MSBuild is now used for building C++ apps as well now. We utilize MSBuild for instrumenting builds as well. When selecting Instrumentation we toggle a flag in the vcxproj.user file to tell MSBuild to use NMCL and NMLink to build the projects.

MSBuild allows you to get the same build in VS as well as running MSBuild from the command line.

If you create a small sample project and turn on instrumentation you will see the small XML that you will want to add to the selected projects / configurations in the vcxproj.user files that will be used on your automated build system. (If you use MSBuild in your scripts).

The XML below turns on Boundschecker instrumentation for the Debug Win32 project and off for the release.

<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">
<DevPartner_IsInstrumented>1</DevPartner_IsInstrumented>
<DevPartner_Instrumented_Type> /NMbcOn</DevPartner_Instrumented_Type>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">
<DevPartner_IsInstrumented>0</DevPartner_IsInstrumented>
<DevPartner_Instrumented_Type> /NMbcOn</DevPartner_Instrumented_Type>
</PropertyGroup>
</Project>

DevPartner_IsInstrumented when 1 is on and 0 for off
DevPartner_Instrumented_Type passes the type of instrumentation to NMCL just as you would on the command line for VS2008 and previous.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.