I'm not sure that works, but maybe it's worth trying it:
I think it is necessary that the borland objs are linkable, means there are
no external definitions used.
1. Switch your CVI to borland mode (running the installer).
2. Take your borland modules, write some wrapper code and generate a DLL,
that exports all the functions you need.
3. Generate the DLL and import libraries for all compatibility modes
(especially for MSVC).
4. Switch your CVI back to MSVC mode.
5. Add the DLL (import library) to your project, that wants to use the
borland objects and use them as DLL-Calls.
I never tried, but at a first glance, this should work. Please let me know
what you figure out.
Regards
Torsten
"dale" schrieb im Newsbeitrag
news:506500000008000000D2660000-
1031838699000@exchange.ni.com...
> I have an obj file which was compiled using the Borland compiler
> compatibility mode. The source for this file is not available. I wish
> to use this file in a LabWindows project which is built using the
> Visual C/C++ compiler compatibility mode. Is there a way to import or
> convert Borland-formatted obj files for use within a LabWindows
> project which uses the Visual C/C++ compiler compatibility mode?