DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending] Link: http://www.fltk.org/str.php?L2521 Version: 1.3.0 Fix Version: 1.3-current (r8298) > post-build: Greg, I don't see a reason why we would need this. All test > files are IMHO linked statically, thus we don't need the dll's in the test > directory. Why did you add this? Did you have evidence that we need it? Yes; either the Debug build or the Release build was writing the file directly to the test directory. And I recall this used to be necessary, because several of the programs were built against the DLL's (IIRC, the test/editor demo used to fail to run because the DLL wasn't in the same dir). I'd used to see these errors myself, and we all knew to copy in the DLL. Eventually someone set it up to install the DLL in the test dir, but then perhaps backed it out after changing the test programs to all build static, but forgot to change either Debug or Release. I wasn't sure what the history was, so I just set it up to copy the dll (instead of write it direct) in both Release and Debug cases to preserve that intention, as that definitely used to be the case. If it's the case the test programs are all static, then it sounds like we don't have any tests for the DLL libs.. and maybe we should. (eg. 'test-dll' or some such?) In which case you'd need the dll's in the test dir for that test to work. Link: http://www.fltk.org/str.php?L2521 Version: 1.3.0 Fix Version: 1.3-current (r8298) _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
