Re: [CMake] Visual Studio 2010 generator broke? Yes, but not how I thought

2010-09-28 Thread Bill Hoffman
On 9/28/2010 5:43 AM, David Cole wrote: Why do you think this is incorrect? Either $(Configuration) or $(IntDir) should be acceptable locations for obj files... This was a bug, Brad checked in the fix into next. -Bill ___ Powered by www.kitware.com

Re: [CMake] Visual Studio 2010 generator broke? Yes, but not how I thought

2010-09-28 Thread David Cole
Why do you think this is incorrect? Either $(Configuration) or $(IntDir) should be acceptable locations for obj files... On Sun, Sep 26, 2010 at 11:40 AM, J Decker wrote: > this is the sample cmakelists that causes bad output... > > -- > > cmake_minimum_required(VERSION 2.8) > > pr

Re: [CMake] Visual Studio 2010 generator broke? Yes, but not how I thought

2010-09-26 Thread J Decker
this is the sample cmakelists that causes bad output... -- cmake_minimum_required(VERSION 2.8) project( launchpad ) set(BASE_SOURCES launchpad.c launchpad.rc ) add_executable(${PROJECT_NAME} WIN32 ${BASE_SOURCES} ) - the 'Output File Name' property in visual studio is .

Re: [CMake] Visual Studio 2010 generator broke?

2010-09-25 Thread J Decker
s/CMAKE_CURRENT_SOURCE_DIR/CMAKE_PROJECT_DIR/g (my bad) > > Using the Visual Studio 2010 generator .obj files of sources which are > not in the current directory are put into > (build root)/${CMAKE_CURRENT_SOURCE_DIR}/Debug/ This is actually just 'Debug/.obj' in the project file, but since the p

[CMake] Visual Studio 2010 generator broke?

2010-09-25 Thread J Decker
I only can test 2010, might be all for all I know... I have a directory that contains a source. That source, is used by multiple targets, some static executables, some dynamic libraries, and a executable linked to a dynamic library. They all do the same job; they just don't all link the same way