For ultimate performances, the compiler can produce machine code by using a "C" compiler. In that case the p-code is post-compiled to "C" and then compiled using a 3rd party "C" compiler. This box enables you to select the required "C" compiler and setup relevant options.

Selecting the "C" compiler

The main list propose possible "C" compilers and indicates for which Runtime Service system. Select the None choice if you do not want to enable "C" compiling.

Options

You can ask the Workbench Studio to generate both machine code and classical p-code. If this option is selected, then the application will require more space in the Runtime Service system. Some debugging features such as step by step debugging and variable locking are not available when the Runtime Service runs machine code. If this option is set, you will be available during debug to change "on the fly" from machine code execution to p-code interpretation. Turning the Runtime Service to p-code execution will then enable advanced debugging features.

If can select the Load compiled code option, then the code file (typically a DLL) will be automatically downloaded together with the application code.

The "C" compiler is run in a DOS-like prompt window. You can check the Show compiler window option if you want this window to be visible when post-compiling.

3rd party tool folder

You must specify where the 3rd party "C" compiler is installed on your computer. You can press the Check button to verify that the Workbench Studio actually recognizes the compiler in this folder.

Target code file name

Here you can enter the name of the code file to be produced by the "C" compiler. Refer to your OEM instructions if your Runtime Service system does not use the default name.

Created with the Personal Edition of HelpNDoc: From Word to ePub or Kindle eBook: A Comprehensive Guide