<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; ">This is what I did when someone "required" this:<DIV><BR class="khtml-block-placeholder"></DIV><DIV># ---- Change the Suffix on the Generated Dylib --------------------------------</DIV><DIV>IF (CMAKE_BUILD_TYPE STREQUAL "Debug")</DIV><DIV> SET_TARGET_PROPERTIES (About</DIV><DIV><SPAN class="Apple-tab-span" style="white-space:pre"> </SPAN>PROPERTIES SUFFIX ".plug_d"</DIV><DIV> )</DIV><DIV>ELSE (CMAKE_BUILD_TYPE STREQUAL "Debug")</DIV><DIV> SET_TARGET_PROPERTIES (About</DIV><DIV><SPAN class="Apple-tab-span" style="white-space:pre"> </SPAN>PROPERTIES SUFFIX ".plug"</DIV><DIV> )</DIV><DIV>ENDIF (CMAKE_BUILD_TYPE STREQUAL "Debug")</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><rant></DIV><DIV>This is just completely NOT needed with any modern IDE or CMake. I know for a fact that VS 2003 and 2005 both will generate a "Debug" and "Release" folder placing the contents in those folders for each of their respective build types. Xcode on OS X will do the same thing. This obviates the need for adding "special" extensions to your libraries. But you say, I am on (Linux/BSD/Emacs/VI) and all I have is Make.. Well.. This is where CMake shines. Just create 2 build directories, one for release and one for debug. Each Directory will have its own complete build of the libs and executables. This will obviate the need for using naming schemes on your extensions.</DIV><DIV></rant></DIV><DIV><BR><DIV> <SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Bitstream Vera Sans; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">-- </DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Mike Jackson Senior Research Engineer</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Innovative Management & Technology Services</DIV><BR class="Apple-interchange-newline"></SPAN> </DIV><BR><DIV><DIV>On Feb 16, 2007, at 3:23 PM, Matthieu Brucher wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite">Hi,<BR><BR>I'm trying to generate a CMakeList.txt file for a project that used a simple Visual Studio solution. As there was a lot of images and data to load at the start of the programs, everything was put in a /bin/data folder and the programs and libraries were generated in the /bin folder with a _d suffix for the debug versions. <BR>Is it possible to do something like this with CMake ? I tried to find a solution in the documentation, but no luck :(<BR><BR>Matthieu<BR><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">_______________________________________________</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">CMake mailing list</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="mailto:CMake@cmake.org">CMake@cmake.org</A></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="http://www.cmake.org/mailman/listinfo/cmake">http://www.cmake.org/mailman/listinfo/cmake</A></DIV> </BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>