[CMake] Visual Studio project paths

[Ben Ratzlaff]

I agree that it is better to keep the builds separate, however this behavior
is only specific to the Visual Studio generators.

I set my output paths with setting the LIBRARY_OUTPUT_PATH and
EXECUTABLE_OUTPUT_PATH variables. The Makefile generator and NMake Makefile
generator do not change these output paths, and I can specify the
differences between debug and release in my cmake script. The Visual studio
generators CHANGE this path reguardless so output/win32_d becomes
output/win32_d/debug.

If there were DEBUG and RELEASE versions of LIBRARY_OUTPUT_PATH that I could
set that did not change, things would be just fine.

-Ben

On 1/16/07, Andrew Maclean <andrew.amaclean at gmail.com> wrote:
>
> I hope not. You need this in Visual Studio to set the build. It also keeps
> the builds separate.
>
> Andrew
>
>
>
>
> On 1/17/07, cmake at daishiva.com <cmake at daishiva.com> wrote:
> >
> > Is there any way to stop cmake from appending
> > Debug/Release/MinSizeRel/etc to my output paths when making a Visual
> > Studio project?
> > _______________________________________________
> > CMake mailing list
> > CMake at cmake.org
> > http://www.cmake.org/mailman/listinfo/cmake
> >
>
>
>
> --
>
> ___________________________________________
> Andrew J. P. Maclean
> Centre for Autonomous Systems
> The Rose Street Building J04
> The University of Sydney  2006  NSW
> AUSTRALIA
> Ph: +61 2 9351 3283
> Fax: +61 2 9351 7474
> URL: http://www.cas.edu.au/
> ___________________________________________
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://public.kitware.com/pipermail/cmake/attachments/20070116/13fed922/attachment.html