01-27-2009 06:52 AM
01-28-2009 09:37 AM
Hi qwertz,
do you still have the source files? Can you rebuild them in a newer CVI version?
Or do you have an old dll or exe? Then it is not possible to convert it.
01-29-2009 02:25 AM
Hey DianaS,
All the source files are there. It is possible to build the project using CVI 5.5 (which is still there on an the same pc the original project was written on but we want to upgrade to a newer version anyway) and Watcom compatibility mode and it works fine. Other compatibility modes gives a few hundred errors about undefined or redefined functions (tried several modes with CVI 4). I can't build with CVI 7, trying produces a similar number of errors. I assume that's because Watcom compatibility mode isn't available in the newer versions. I will check the error list again and post them.
Thanks, qwertz
01-30-2009 08:36 AM
I tried building again and got the following results:
CVI 5.5, Watcom mode:
Produces an working exe-file.
CVI 7.0, Borland mode:
Two error types when I try to build the project:
Symbol '...' defined in modules '...' and '...'. In Borland mode, multiple modules must not contain uninitialized definitions of the same global variable. Borland creates a separate variable for each definition. LabWindows/CVI and other linkers resolve all definitions to the same variable. If you want separate variables, use different names or the "static" keyword. If you want one variable, change all definitions except one to "extern" declarations.
Undefined symbol '...' referenced in "...".
There's about 200 total, do I have to fix all these or is there a better way around?
CVI 7.0, Visual C/C++:
Gives a series of error popups at startup:
"Aborted load of library "..." The file format of "..." does not match that used by the current compatibility mode.
"Library '...' not loaded."
It complains about two libraries, building the project gives the same error messages.
Does this help?
02-03-2009 06:26 AM
Hi qwertz,
if you have the .c .h and .uir files you can open them in any cvi version with any compiler.
If you have a library with watcom compiler createt you have no chance including it with other compiler mode.
Then you have to rebuild it for for example Visual C/C++ compiler mode.