RADE

• tck_init.bat
• tck_profile CXR17

With Unix platform:
Execute following commands to access mkmk:

• . tck_init.bat
• tck_profile CXR17

1. mkCopyPreq: static access
2. mkGetPreq: dynamic access

In the window displayed in the right side, the "Copy prereq ..." radio button corresponds to the mkCopyPreq command and the "Use Prereq ..." radio button corresponds to the mkGetPreq command. In this example, the corresponding command is:

mkGetPreq -p
  H:\BSF;E:\Program Files\Dassault Systemes\B17D04

Note that the first directory you set in the list will be the first browsed when searching for prerequisites afterwards. You can change directory order by selecting a directory in the list and click on the arrow Up and Down buttons.

You can specify additional options by clicking the Specify other options button, which is especially useful for the mkCopyFw command.

The first mode gives you dynamic access (mkGetPreq), the second static (mkCopyPreq) and the third combines both modes by copying your prerequisites in a directory different from your own (mkCopyPreq to an other directory, followed by mkGetPreq referencing this directory).

mkCopyFw -update VisualStudio -d

Using the dialog box, you enter the path to the origin workspace(s) in the top list, then type the name of the framework(s) you want to copy (use <space> between two framework names), you can filter the modules to copy by clicking on the "Add..." button associated with the middle list (at least one framework name must have been typed in before).

The check boxes in the "Copy Options" area correspond- from top to bottom - to the following options: -nm, -no, -d, -f, -update and -remove.

$ mkmk -ug EnoviaDMC

$ cd VisualStudio
$ mkmk -ug CATVBTDevBase.m

Advanced users can take benefit from the mkGMake tool to compile just one file or to link a library. This is faster than running mkmk. This feature is available in Visual Studio.NET through the usual keyboard shortcuts which have been changed to run the CAAV5 builders: Ctrl-F7 and F7.

• Ctrl-F7 starts the compilation of all source files in the current active project.
• F7 starts the link of the project (module) corresponding to the source file currently active.

The items of the Dialog boxes correspond respectively to -c, -d, and -k options of the command.

The mkrun command is in charge of setting the runtime environment and then to run V5. Using Visual Studio.NET the runtime environment is already set and you can run V5 directly.

Like -keep option of mkrun is used to get a shell setting a proper environment, we can open from Visual Studio.NET a DOS window in which the runtime environment has been set, this is a convenient way for checking it's correct. To do this open menu "Window" and select "Open Runtime Window".

if you're not building an executable, you'll be prompted to enter the name of the executable to run, then type CNEXT, or select the CNEXT.exe module with the browse button from your Runtime View.

1. mkman for C++ interfaces
2. mkdcidl for IDL objects.

There is nothing more to do, a log window is displayed while the documentation is being generated.

The test objects which are selected in the right side of the dialog box are specified using -s option on the command line.

The following window appears displaying the test objects found in test frameworks of your workspace. Select which ones you want to run and click on "OK".

You can also define additional variables, to take them into account only during the replay.

Select all files in the workspace, all files from a specified framework, all files for a specified module or a single source file. You can enable or disable warning messages and specify an optional file containing an alternate list of methods returning a pointer and needing a Release().
Click OK to start, a HTML viewer will be opened at command completion to display the generated report.