Hi Alexey, Usually there are 2 ways: 1) put them into separate directories (like Debug and Release), probably specifying different output directories or 2) use different file names, say adding suffixes like D, or d8.
BTW, what's the point to have different configurations in the same workspace (do you really still use VC6?) in different projects? Usually for Visual Studio configuration is coded into output directory path using macros like $(Configuration), so resulting binaries are put into different dirs. And you have to build twise to get all configurations. Why do they required to have the same name? May be you're trying to solve wrong problem? Regards, Yuri On Thu, Mar 3, 2011 at 2:50 PM, Alexey Livshits <[email protected]> wrote: > Hello CMakers, > suppose I've got a library foo with tow configurations: foo_1 and > foo_2. Both versions should have the same output name: foo. The > problem is, the output directory for both ist the same, so the second > will overwrite the first. > What's the best way to organize it? > > -- > BG, > Alexey > _______________________________________________ > 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 >
_______________________________________________ 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
