ComponentWorks work abnormally with C++ Builder 5.0

Question

I am an user of ComponentWorks(full version). I formerly used ComponentWorks
with C++ Builder 4.0 professional and they worked together ok. Recently, I¡¯
ve updated C++ Builder 4.0 to C++ Builder 5.0 enterprise suite, then
ComponentWorks worked abnormally. The details show as follows:
In C++ Builder 5.0 IDE, I installed ComponentWorks from the menu Component
and submenu Import ActiveX control, compile could not pass. Later I
installed ComponentWorks component one by one, I found the National
Instrument CWDAQ 2.0.1(Version 1.3) have 10 errors and CW DataSocket 2.0.1
have 2 errors. All of others registered successful. So I opened the project
BuilderGraph1 which I downloaded from your web NI.COM, compile th
e project
cound not pass because there were too many errors. I don¡¯t know why it¡¯s
so.
The errors when I installed the CWDataSocket 2.0.1(v1.3) :
[Linker Error] Unresolved external ¡®Cwdslib_tlb:IID_DCWData¡¯ referenced
from c:\PROGRAM FILES\BORLAND\CBUILDERS\IMPORTS\CWDSLIB_OCX.OBJ
[Linker Error] Unresolved external ¡®Cwdslib_tlb:IID_CWData¡¯ referenced
from c:\PROGRAM FILES\BORLAND\CBUILDERS\IMPORTS\CWDSLIB_OCX.OBJ
The errors when I installed the CWDAQ 2.0.1(v1.3):
[Linker Error] Unresolved external ¡®CWdaqcontrolslib_tlb:IID_CWAIChannel
¡¯ referenced from c:\PROGRAM
FILES\BORLAND\CBUILDER5\IMPORTS\CWDAQCONTROLSLIB_OCX.OBJ
[Linker Error] Unresolved external ¡®CWdaqcontrolslib_tlb:IID_CWAOChannel
¡¯ referenced from c:\PROGRAM
FILES\BORLAND\CBUILDER5\IMPORTS\CWDAQCONTROLSLIB_OCX.OBJ
I want to know the reasons and the resolve way quickly.

Answer 1

Hello
Borland enables certain types of exceptions by default which are initially disable in MSVC. You will need to refer to the documentation for Borland Builder on how to disable floating point exceptions. I believe you can do it by adding the following statement to your initialization code, but you should double check this:
_control87(MCW_EM, MCW_EM);
These exceptions get thrown because we are doing some floating point initialization underneath. This is not an indication of a bug or a problem of any sort. Apparently you have to this for alot of libraries to work correctly with Borland (OpenGL etc...)
Hope this helps
Bilal Durrani
NI
Bilal Durrani
NI