Thanks,
I'd prefer that, but unfortunately, this is not possible atm.
On Tue, Nov 2, 2010 at 7:45 PM, David Cole wrote:
> Elminate the circularity. You'll drive yourself mad.
>
> :-)
>
>
> On Tue, Nov 2, 2010 at 2:38 PM, tmp
> wrote:
> > Hi all,
> >
> > I have got some circular dependencies in
On Sun, Nov 14, 2010 at 8:44 AM, Andreas Mohr wrote:
>
> However back to the question itself:
> to force a re-configure, one could "cmake -E touch"
> the CMAKE_CURRENT_LIST_FILE, somehow during target building
> or some such.
> This is quite certainly not the most direct (nor elegant!) way
> to f
Hi,
> any ideas how to force it directly?
for our projects, I use a variable called RESET_CACHE as a standard.
Every FOOConfig.cmake, FindFoo.cmake, ... uses this variable to force
resetting a lot of cache variables. So it suffices for a project to include
this variable.
Anyway, this does not h
Hi,
On Tue, Nov 02, 2010 at 06:03:57PM -0400, cmake-requ...@cmake.org wrote:
> Message: 4
> Date: Tue, 2 Nov 2010 14:45:35 -0400
> From: David Cole
> Subject: Re: [CMake] How to force the configure step to start over
> To: tmp
> Cc: cmake@cmake.org
> Message-ID:
>
Elminate the circularity. You'll drive yourself mad.
:-)
On Tue, Nov 2, 2010 at 2:38 PM, tmp
wrote:
> Hi all,
>
> I have got some circular dependencies in my source that origin from
> internal cache variables managed in different parts of my project.
> Unfortunately there is no correct order to
Hi all,
I have got some circular dependencies in my source that origin from
internal cache variables managed in different parts of my project.
Unfortunately there is no correct order to include the subprojects:
Sometimes A B C would be correct, sometimes B C A, sometimes C A B.
At the moment I ch
