Here's a third, along the lines of the Half.dll reference issue Thorsten pointed out;
* When running test (IlmImfTest, lets say) for a DLL build, how is the path to the DLLs supposed to be handled? As best I can tell, the IlmImf DLLs end up under IlmImf\, and the IlmBase DLLs end up in their install path. But when it comes time to run tests, I can't see that any of those paths are in $PATH, or that the DLLs and the test executable are in the same path, or any other way to resolve the DLL references. Basically, when I go to run tests, I get a bunch of 'DLL not found' issues to sort out manually. It's the same thing as having to manually sort out Half.dll when generating the b44/dwa table data in IlmImf. Karl On Mon, Jul 14, 2014 at 10:04 AM, Karl Rasche <[email protected]> wrote: > > Ed - > > In addition to the issues Thorsten has called out, I've hit the following > on windows > > * No stdint.h in VC 9 / 2008 > Just had to pull the include from IexMath/IexMathFpu.cpp. Probably an > occupational hazard > of using an older compiler > > * Undefined symbols in IlmImfTest > I think that ImfRle.h needs to include ImfExport and have the two > functions marked as IMF_EXPORT, > as well as CpuId in ImfSystemSpecific getting markrd as class > IMF_EXPORT > > > Karl >
_______________________________________________ Openexr-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/openexr-devel
