OpenMake Meister

Creating Microsoft Visual Studio 6.x C/C++ Targets Without the Add-in

Visual Studio 6 uses a .dsp  file to manage the Microsoft C/C++ Project information. This .dsp  file is updated whenever you create a new class or insert a new file into the Microsoft Project.  The .dsp  file can be used as a dependency to the Target. The continuous integration build script generation process will read the .dsp  file to determine the source files to use to generate a build script, called a Build Control File.  Because the .dsp is not always a complete list of all libraries used to build the application, you will need to update your Target with list of library dependencies (.lib) that are not listed in the .dsp.

 

To define a Visual C++ executable, dynamic link library or static library to be built, follow the procedures in Table PB-36 for adding a Target to your Project.  When adding Build Task Dependencies, follow the steps below:

 

Table PB-36 Defining Visual C++ Target

Step

Action

1

Add your project file and library dependencies.  The dependencies would be the .dsp file and the .lib files that are used to link your program.  For example:

hello\hello.dsp

user32.lib

 

2

When you define dependencies, make sure that you use only the relative paths to the files since the build process concatenates these relative paths with the Dependency Directories in order to find the correct file.

3

Make sure your Target Definition File (.tgt) and .dsp can be found through Directories associated with the Project for the Target file in order to display the Target in the Target Explorer and to determine what Targets to include in the generated Build Control File.

 

Note: Build Tasks belonging to Build Services that support .dsp Project File scanning must not be renamed or modified. Such changes may impact the build script generation during .dsp dependency scanning.