OpenMake Meister

Setting Up omNet for Visual Studio 2003

Within the .NET 2003 IDE, it is necessary to configure bldmake and om to perform local unit builds.  This is accomplished by defining two External Tool configurations both of which execute omNET.  omNET is an executable located in the bin directory of the Command Line Client that performs two primary functions based on the defined parameters:

 

•     Automates converting .NET 2003 Solutions and Projects into Targets and calls bldmake which constructs a Build Control File for a specified Project and Dependency Directories.

•     Calls om which executes a build against the Build Control File found in the defined Build Directory.

 

Note: omNET requires PERL 5.8.6, 5.8.7, 5.8.8, 5.10 or 5.12.

 

The External Tools can be defined within the .NET 2003 IDE through the Tools→External Tools menu option.  After being defined, the External Tools can be executed and adjusted directly from the Tools menu.

 

 

Setting Up for Target Generation

The first .NET 2003 External Tool that needs to be configured is omNET: TGT Generation.  The following steps are required to configure omNET: TGT Generation.

 

 

Table SI-33 Adding the External Tool

Step

Action

1

Go to 

External Tools in the menu bar. Click “Add” in the External Tools screen.

2

Type the title name in the “Title” field, for example, “omNET: TGT Generation”

3

Type omNET.exe in the “Command” field for the name of the executable

4

Add the following arguments to the “Arguments” field to pass to omNET.exe.
      -omProject <Meister Project>
      -omSearchpath <Meister Dependency Directories>
      -slnDir $(SolutionDir)
      -slnFile $(SolutionFileName)
      -action CONVERT

 

Once added the “Arguments” field should look like:
-omProject <Meister Client Project Name> -omSearchpath <Meister Client Dependency Directories> -slnDir $(SolutionDir) -slnFile $(SolutionFileName) -action CONVERT

 

An optional argument “-targetDir <output location>”, may be provided to force all build output for all projects in the solution to  be created in the same location, indicated by <output location>. Example: -targetDir ..\..\BuildOutput\release\bin

5

Add the build directory path to the “Initial Directory” field.  This is where Build Control Files and logs will be generated.  All executables will also be built relative to the Build Directory. This value should be set the same for both the Conversion and Build External Tool settings.

 

Note: The “Initial Directory” for omNET should not be the solution directory. This causes the main solution files to be overwritten and a pop-up message will result.  The initial directory must exist (currently). If the directory does not exist, it will use the solution directory.

6

Check the box “Use Output window” to have omNET logging information displayed at in the console window.

 


If the -omproject and -omsearchpath arguments do not have defined parameters, the omNET process will default to the .sln file name minus the “.sln” extension for the Project value and “DEVELOPMENT” for the Dependency Directories value.  In addition to the required arguments indicated above, all of the standard bldmake options can also be added to the “Arguments” field.

Note: The variables are provided to the External Tools by the .NET 2003 IDE and can be selected by clicking on the black arrow next to the “Arguments” entry field.

 

Setting up for Build Execution

The second .NET 2003 External Tool that needs to be configured is omNET: Build.  The following steps are required to configure omNET: Build.

 

 

Table SI-34 Adding the External Tool

Step

Action

1

Go to 

External Tools in the menu bar. Click “Add” in the External Tools screen.

2

Type the title name in the “Title” field, for example, “omNET: TGT Generation”

3

Type omNET in the “Command” field for the name of the executable

4

Add the following arguments to the “Arguments” field to pass to omNET.
          -slnDir $(SolutionDir)*
      -slnFile $(SolutionFileName)*
      -projDir $(ProjectDir)*
      -projFile $(ProjectFileName)*
      -action BUILD

 

Once added the “Arguments” field should look like:
-slnDir $(SolutionDir) -slnFile $(SolutionFileName) -projDir $(ProjectDir) -projFile $(ProjectFileName) -action BUILD

All of the standard om options can also be added to the “Arguments” field.

5

Add the build directory path to the “Initial Directory” field.  This is where Build Control Files and logs will be generated.  All executables will also be built relative to the build directory. This value should be set the same for both the Conversion and Build External Tool settings.

 

Note: The “Initial Directory” for omNET should not be the solution directory. This causes the main solution files to be overwritten and a pop-up message will result.  The initial directory must exist (currently). If the directory does not exist, it will use the solution directory.

6

Check the box “Use Output window” to have omNET logging information displayed at in the console window.