OpenMake Meister

Setting Up the Visual Studio 2005, 2008 and 2010 Add-in

Following are the steps to setup the Visual Studio 2005, 2008 and 2010 Add-in.  This Add-in enables you to perform local builds from inside of Visual Studio IDE.  In addition, automatic Target generation can be performed.

 

Prerequisites

The following requirements must be met in order to run the Meister Visual Studio 2005, 2008 and 2010 Add-in:

 

         Visual Studio 2005, 2008 or 2010 must be installed on the build machine.

         Meister Client or Meister Remote Agent installation

 

Note:  When installing Meister, the Microsoft Add-in is automatically installed.  To validate and enable the installation, go to the “Tools”>”Add-in Manager” and verify that the “OpenMake Add-in” is in the list and enabled.  If it is not enabled, check the options to enable.  If it is not in the list, contact OpenMake Support.

 

Performing the Configuration

When setting up a Meister build in Visual Studio 2005, 2008 or 2010, you will need to tell the Add-in how to configure the build that you are running. Configuring a Meister build tells the add-in which Dependency Directories to use, along with which options to run the build.

 

Table PB-29 Configure Add-in

Step

Action

1

Go to 

Build > Meister > Configure Meister…  from the menu bar

2

Define Your Settings as defined below in Table PB-30

 

 

The following are the settings that can be modified by the user of the Meister Visual Studio 2005 or 2008 Add-in:

 

Table PB-30 Settings for the Microsoft Visual Studio 2005, 2008 or 2010 Add-in

Parameter

Description

KB Server

Address of the knowledge base server that the Add-in needs in order to connect for accessing the build metadata. The Add-in can grab the server address from one of two locations: from the OPENMAKE_SERVER environment variable or from local user settings.

Project

Selects the project that you want to reference for the Meister build through the IDE. The drop down menu lists all available Projects retrieved from the Knowledge Base server, listed alphabetically.

Dependency Directory

Selects the Dependency Directory that you want to reference. The drop down menu lists all Dependency Directories associated with the Project you selected above, listed alphabetically.

Pre-flight Workflow

Selects the Workflow that you want to execute for a Pre-flight build.  Useful for executing a local build prior to checking in code to the source repository.

bldmake options

Defines the options that you want to pass to bldmake when you run the build. The default options are –s (case sensitivity) –ov (verbose logging output) and –mo "windows" (denoting that you want bldmake to output exclusively to the windows.mak build control file.)

om options

Defines the options that you want to pass to om when you run the build. The default option is –ov, denoting verbose logging output.

Solution Build Project "build" directory

Defines the name of the directory relative to which all targets will be built. The default value for the directory name is "build." You can rename this directory to any Window-allowed directory name.

Solution Build Project "tgt file" directory

Defines the name of the directory where the Target Definition (TGT) files will be generated by the Meister Add-in. You can rename this directory to any Windows-allowed directory name.

Force Assemblies to this subdirectory

Select this option will consolidate all outputs to the same directory.  The directory must be relative to your solution file.

Build output to project output directories

Selecting this option will set the build directory to be under the <OMBuild Project>/build directory for Meister builds, in order to separate Meister builds from the regular VS IDE builds

Generate TGTs for Project Skipped in current .NET build configuration

Selecting this checkbox will cause the Add-in to generate TGTs for projects that are skipped in the .NET build configuration screen. The default for this option is "no" (i.e. box NOT checked.)

Generate TGTs before every build

Selecting this will cause TGTs to be generated before every build run through the Add-in. The default option is "yes" (i.e. box checked.)

Generate TGTs for Web Site Projects

Selecting this will cause TGTs to be generated for Web Site projects.  The default option is “no” (i.e. box NOT checked)

Force TGTs to use devenv Build Service

Selecting this will cause TGTs all to be generated with .Net Solution Executable or .Net Solution Dynamic Link Library even if MSBuild can be used.  This option should be used when there is a mix of C++ and C# or C++ and VB projects exist in the Solution.

 

The Build Services used when generating the Target are:

     .Net Solution Executable

     .Net Solution Dynamic Link Library

     MSBuild Executable

     MSBuild Dynamic Link Library

     MSBuild Website

 

The Build Service used is determined by the Add-in based upon the Visual Studio Project type and “Force TGTs to use devenv Build Service” option.