[Paraview-developers] [EXTERNAL] Re: CMake Call stack

Scott, W Alan wascott at sandia.gov
Wed Jul 11 13:13:02 EDT 2012


Unfortunately, the bug only shows on Windows.  I am successfully replicating the bug with Cygwin.  Also unfortunately, all of the trace output is going to stderr, and cmake keeps reading the redirect as a command for cmake.

I tried the following:

cmake --trace ../source/ParaView3 &>junk.txt

and it just complains about an invalid null command...

Alan

From: David Cole [mailto:david.cole at kitware.com]
Sent: Wednesday, July 11, 2012 4:49 AM
To: DeMarle, David Edward (External Contacts)
Cc: Scott, W Alan; paraview-developers at paraview.org
Subject: [EXTERNAL] Re: [Paraview-developers] CMake Call stack

Nope. "--trace" and re-direct to a log file is the best way...

On Tue, Jul 10, 2012 at 10:24 PM, David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>> wrote:
I use cmake --trace for that sort of thing. That and the message
command and grepping the log file cmake --trace produces.

There are probably better ways.

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909<tel:518-881-4909>


On Tue, Jul 10, 2012 at 9:33 PM, Scott, W Alan <wascott at sandia.gov<mailto:wascott at sandia.gov>> wrote:
> I am trying to figure out why a CMakeLists.txt is being used by CMake.  Is
> there a way to find out who is calling this CmakeLists.txt?
>
> Thanks,
>
> Alan
>
>
>
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org<mailto:Paraview-developers at paraview.org>
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
_______________________________________________
Paraview-developers mailing list
Paraview-developers at paraview.org<mailto:Paraview-developers at paraview.org>
http://public.kitware.com/mailman/listinfo/paraview-developers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20120711/9bee9880/attachment.htm>


More information about the Paraview-developers mailing list