give a bit more detail regarding the
"desirable behavior".
Aaron C. Meadows
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of Eric Wing
Sent: Monday, June 07, 2010 5:25 PM
To: Tyler Roscoe
Cc: CMake Mailinglist
Subject: Re: [CMake]
> On Mon, Jun 07, 2010 at 02:14:00PM -0400, Nathan Huesken wrote:
>> > 1. Why do you need to nest one project inside the other? I think you
>> > will have less trouble if you treat each one as its own independent
>> > project.
>>
>> Because it the outer projects depends on the inner and they are
>>
I just looked at your email address and now I'm pretty sure I know why
I've had "Lonely Rolling Star" from the Katamri Damacy soundtrack stuck
in my head all morning :).
On Mon, Jun 07, 2010 at 02:14:00PM -0400, Nathan Huesken wrote:
> > 1. Why do you need to nest one project inside the other? I t
On Mon, 7 Jun 2010 10:48:30 -0700
Tyler Roscoe wrote:
> On Mon, Jun 07, 2010 at 11:54:12AM -0400, Nathan Huesken wrote:
> > I have a cmake project into which I want to nest another cmake
> > project. The nested cmake project is a complete project working on
> > its own, and the outer cmake projec
On Mon, Jun 07, 2010 at 11:54:12AM -0400, Nathan Huesken wrote:
> I have a cmake project into which I want to nest another cmake project.
> The nested cmake project is a complete project working on its own, and
> the outer cmake project depends on it.
> So when the outer cmake project is build, the
Hi,
I have a cmake project into which I want to nest another cmake project.
The nested cmake project is a complete project working on its own, and
the outer cmake project depends on it.
So when the outer cmake project is build, the inner one should be build
first.
The inner, as well as the outer c
