On Fri, Jul 30, 2010 at 2:11 PM, Ryan Pavlik <[email protected]> wrote: > On 7/30/10 7:01 AM, Olaf van der Spek wrote: >> >> On Fri, Jul 30, 2010 at 1:52 PM, Ryan Pavlik<[email protected]> wrote: >>> >>> Almost nobody uses the static runtime unless someone else's lib forces >>> them >> >> Why not? >> If Windows had proper package management I wouldn't use it either, but >> until then... >> >> Olaf > > I'd only really just offer it as one option, in case a user of your library > is forced to use another library with the static runtime. It doesn't mean > that you don't have a static library without it, it just means you aren't > embedding the entire standard c/c++ runtime library into yours, bloating > memory usage, and inviting lots of symbol collisions when versions don't > quite match. Myself and my colleagues have collectively lost significant > hair on this one, and it took a while for me to figure out exactly what it > all meant since it's kind of confusing. (and the error messages more so)
That's why I'm asking for library names to be decorated! So one can choose and know whether a library is using the run-time in a static way or in a dynamic way. Olaf _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
