Creating a Message-Compiler Subproject

If the application's directory contains an .MC (message compiler) file such as \ACLEDIT\ACLEDIT.MC or \RULEEDIT\RULEEDIT.MC, you need to create a subproject for it. This procedure uses the ACLEDIT project for an example, in which a message-compiler subproject named AclEditMsgs is created.

    To create a message-compiler subproject
  1. Choose the Project option from the Insert menu. In the Type box of the Insert Project dialog box, click Makefile. In the Name box, type a name for the subproject, such as AclEditMsgs. Click Create. Click Yes in the warning box that reads:

    The makefile name or some other command line may be specified in the Project Settings dialog. Would you like to go there now?

    The Project Settings dialog box will be displayed.

  2. In the Settings For box of the Project Settings dialog box, choose a build type (for example, Win32 Debug or Win32 Release, or both) for the subproject AclEditMsgs. Click the General tab. Replace the entire contents of the Build command line text box with:

    MC -V -C -S -H ..\ -R ..\ -X ..\ ..\ACLEDIT.MC

    This command line includes the name of the top-level project's message compiler file—in this case ACLEDIT.MC. Click OK.

  3. In the FileView pane of the Project Workspace window, click the subproject—in this case, AclEditMsgs files. Build the subproject. This step generates header files and resource files. The generated files are placed in the main project directory, which lets you compile the top-level project without specifying subdirectories.
  4. Click the top-level project in the Project Workspace window—in this case, AclEdit files. Choose the Files into Project option from the Insert menu. Select the appropriate files (in this case, ACLEDIT.CPP and ACLEDIT.RC) from the File Name list box in the Insert Files into Project dialog box, and click OK.
  5. Return to step 4 of To build a sample application or DLL, which directs you to select libraries for the linker.