I understand your point, but the Visual Studio itself doesn't really support more than one project in one directory. Ok, you can force it via tricks like this, but that's not the beaten path for most VC developers. For example, the wizard always makes a new directory.
Rather, they are used to the current directory structure that VC generates. True, that directory structure has a bug that this fix addresses, but from my POV I'd rather have a switch - call it "USE_BROKEN_VC7_DIRECTORY_STRUCTURE" if you want - that causes Cmake to extrude the traditional directory layout. -----Original Message----- From: Bill Hoffman [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 09, 2007 1:57 PM To: Rob Mathews Cc: Brad King; [email protected]; Bill Hoffman Subject: Re: [CMake] RE: CMake 2.4.1/VC71 Why the wierd <project>.dir subdirs? Rob Mathews wrote: > Ah, ok, now that makes sense. > > But if you *aren't* doing that.. then you don't need this. > A very simple cmake project would need that: add_library(foo foo.c) add_executable(bar bar.c) target_link_libraries(bar foo) This would create foo.vcproj and bar.vcproj in the same directory. -Bill _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
