On Thu, Jul 22, 2010 at 10:32 PM, Ryan Pavlik <rpav...@iastate.edu> wrote: > Unfortunately there are as many ways to denote these differences as there > are projects. However, unless you're setting the ARCHIVE_OUTPUT_DIRECTORY, > LIBRARY_OUTPUT_DIRECTORY, or RUNTIME_OUTPUT_DIRECTORY (and if you are, I > highly suggest not doing so and instead installing as-needed to a local > prefix), the files should not collide in the build tree - in a multi-config > generator like MSVC, each target gets a directory for each build type, and > in a single-config generator you'll only have one build type per entire > build tree.
And then what? Having two DLLs with the same name is not going to work. Same for import or static libs. What about libs that don't have a naming scheme yet? Is there any recommended way to do this stuff? 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
