Daniel, I just refactored the logic around so that our apps/libs should now be compiling with the same defaults as the src/other targets (which means they should be MT or MD but not both). Would you re-test and make sure it works?
> However, I think I just figured out what is going on. We wipe out the flags > ... in CompilerFlags.cmake ... which is included in a NOT MSVC block in the > top-level CMakeLists.txt file ... which means they're not being wiped out on > Windows [0] like they needed to be. If we make them sync, I'd expect MT or > MD to work and no platform conditionals are needed anywhere. Presuming the change works, it begs the question: do we want MD or MT? >From my understanding, MT means we don't have to require/ship a particular >MSVCRT.DLL which may actually fix several issues we've encountered running on >older versions of Windows. This of course bloats the binary a little, but it >effectively matches what happens on Linux. That said, MT makes our libs potentially problematic if there are 3rd party application developers that also use MT (a different version) or MD even if we allocate in the library and free in the app (ugh). Since you're in this situation, I think you're in the position to specify either. Cheers! Sean ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
