In the OCF folder there is code that references OWL620 DLL's
It's in ocreg.cpp
//Jogy - this is not correct!!
#if !defined(OWL_DLLNAME)
# if defined (_UNICODE)
# if defined(__TRACE) || defined(__WARN)
# define OWL_DLLNAME "owl620vud.dll"
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi David, thanks for the feedback. I have registered a ticket for this issue [bugs:#273].
I do not use OCF, but after having a brief look at the code I note the following:
The code in question is a workaround for the Microsoft compiler (BI_COMP_MSC). Is this workaround still needed with the current set of supported compiler versions?
The code is within a DLL entry point implementation, but is not conditional on whether or not OWLNext is built for static linking. For static linking, DLL entry points and OWL DLL loading should not be relevant.
Hopefully someone with OCF usage and insight will pick this up.
In the OCF folder there is code that references OWL620 DLL's
It's in ocreg.cpp
Hi David, thanks for the feedback. I have registered a ticket for this issue [bugs:#273].
I do not use OCF, but after having a brief look at the code I note the following:
The code in question is a workaround for the Microsoft compiler (BI_COMP_MSC). Is this workaround still needed with the current set of supported compiler versions?
The code is within a DLL entry point implementation, but is not conditional on whether or not OWLNext is built for static linking. For static linking, DLL entry points and OWL DLL loading should not be relevant.
Hopefully someone with OCF usage and insight will pick this up.
Related
Bugs: #273