I think its obvious cvi won't accept an object file made by a c++ native
compiler since cvi can not handle with c++ code, the only thing you can do
is to 'hide' the c++ extentions in your borland code , define pure C functions
that will access the classes in the code and mark these functions as _dllexport
then make a dll of that code, then in the cvi program you won't access the
classes in the dll directly , instead you have to call the dll exported functions
