Tyler Roscoe [mailto:ty...@cryptio.net]:
> On Thu, Jun 04, 2009 at 05:14:20PM -0400, david.k...@l-3com.com wrote:
> > I wonder if the concept of a PROJECT command in a subdirectory
> > of your top-level CMake directory is semantically sound. That is,
> > it might work sometimes but cause trouble
I missed this reply since it wasn't threaded correctly (something wrong
with your mail reader David?). Luckily David said something slightly
different from what I said :).
On Thu, Jun 04, 2009 at 05:14:20PM -0400, david.k...@l-3com.com wrote:
> I wonder if the concept of a PROJECT command in a sub
On Thu, Jun 04, 2009 at 12:47:48PM -0500, Randy Hancock wrote:
> external msproject to the parent. This is desirable, but lets say both
> the test/time project and the test/string project include the common
> lib. This makes common show up *twice* in the parent solution and
> causes a bunch of unwa
Randy Hancock :
> I'm getting duplicate projects included in my top-level solution
> (*.sln file). I have a cmake project() defined at the top level and in
> the test projects for convenience during development. When I use
> include_external_msproject in the subprojects it also adds the
> external
Hello all, It's my first post!
I'm having an issue with include_external_msproject. I have a
directory layout like so:
CMakeLists.txt
/src
/common/CMakeLists.txt
/string/CMakeLists.txt
/time/CMakeLists.txt
/test
/string/CMakeLists.txt
/time/CMakeLists.txt
/build
/src
/
