Experimental Physics and
Industrial Control System

Ø  Just be aware of and careful about the dynamic and static variants of Windows builds additionally setting other compiler flags differently. Mixing object code that has been produced with different flags may create unwanted bad side effects. I.e., you shouldn't put object code from a dynamic build into a static library and vice versa.

That is an interesting point.  It is actually how that DLL has been built for many years.  It is convenient, because Com, ca, ezca, and EzcaScan are statically built into ezcaIDL.dll.  That DLL thus stands alone, and one does not need all the other DLLs.  Depending on other DLLs can lead to a real mess with PATH.  With applications (.exe files) I believe that Windows will look first for DLLs in the same folder as the .exe.  But for a run-time loadable DLL like ezcIDL.dll that does not seem to be the case.

 

The mixed-mode has worked fine for many years.  What are the types of problems people have seen when doing that?