How do I specify a custom external compiler to run from the CVI Editor?

[Bob Balch]

We have a High level development language, that we would like to edit in the CVI editor. We would like to specify a compiler or preprocessor to run from the editor. I see references to an external compiler in the Build menu.

Our compiler would output warnings and errors to the error or build window. Under the hood, CVI C object code would be generated. When run, we'd like to specify breakpoints and stepping behavoir in the CVI window pointing to the High level development language code.

[Scott Y]

Only Microsoft Visual C/C++ and Borland C/C++ are supported as external compliers. This is described in the "Compatibility with External Compilers" section of the LabWindows/CVI help. I have included the text of this section below.

Scott Y
NI

Compatibility with External Compilers
LabWindows/CVI can be compatible at the object code level with both of the compatible external compilers, Microsoft Visual C/C++ and Borland C/C++. Because these compilers are not compatible with each other at the object code level, LabWindows/CVI can be compatible with only one external compiler at a time. This help refers to the compiler with which your copy of LabWindows/CVI is currently compatible as the current compatible compiler.

If you want to change the compatible compiler, select Options»Build Options and choose Visual C/C++ or Borland C/C++ from Compatibility with in the Build Options dialog box.

[LuisG]

Bob,

What you are requesting sounds similar to something which we are considering implementing in a future version of CVI. In order to know for sure, however, I would like to clarify what you mean by "CVI C object code would be generated." Does your High-Level language compiler output C source code, or does it output a standard object file format (like COFF or OMF)? If it outputs source code, do you know if it includes #line directives in the code?

Luis
NI

[Bob Balch]

Luis,

We develop test equipment. We'd like to provide an interface to customers using legacy test languages.
One of these is called Mediator. It's been suggested that we also support Atlas. Currently, we have a Mediator to CVI C translator, the output of which we compile to a dll and run using TestStand. Optimally, we'd like to be able to provide trace back to a given Mediator source line and set breakpoints in the Mediator Source. Initially, we'd like to compile the Mediator source to dll, reducing multiple steps and programs. If the addition of # line directives or other # directives or other macros would facilitate these goals, we could incorporate them.