Creating a Project with Multiple Directories

ID: Q83229

The information in this article applies to:
  • The Visual Workbench
    • Microsoft Visual C++ for Windows, 16-bit edition, versions 1.0, 1.5
    • Microsoft Visual C++, 32-bit Editions, version 1.0

SUMMARY

To help manage a large software project, it is often desirable to store source code and object modules in different directories. By default, Visual Workbench and QuickC for Windows stores the source code and object modules in the same directory. However, you can segregate the source code and object modules by creating the project file in the directory that will contain the object modules.


MORE INFORMATION

To maintain a project with multiple directories, first build the desired directory structure. For example, consider the following directory structure: 


   Main project directory: \TEST
   Source code:            \TEST\SOURCE
   Object files:           \TEST\OBJ
If desired, you can create additional directories (to store header files, and so on). The results of the compilation (.OBJ, .DLL, .EXE, and other files) are placed into the project directory. You cannot place the .OBJ and .EXE files into different directories. In this example, all source files are placed into the source code directory.

Perform the following steps to use the directory structure above:

  1. Create the source files in the source code directory.


  2. From the Project menu, choose Open.


  3. Type the name of your project file (for example, TEST.MAK) in the File Name edit control.


  4. In the Directories list box, choose the object files directory.


  5. Choose OK to create a new project. This creates the project file in the object files directory. When you build the project, the tools store all build results in this directory.


  6. In the Edit Project dialog box, choose the project files from the source directory to add them to the project list. Include all .C, .H, .DEF, .RC, .CUR, .DLG, and other files required to build your project.


  7. Build the project.


NOTE: This kind of technique is not recommended for AppWizard generated projects because Class Wizard (.CLW) files will be required in the OBJ and SOURCE directories.

Additional query words: kbinf 1.00 1.10 1.50 1.51 1.52 build obj

Keywords : kbide kbVC
Version : 1.00 1.50 1.51 1.52 | 1.00
Platform : NT WINDOWS
Issue type :


Last Reviewed: July 26, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.