Am Donnerstag, 8. September 2011, 19:54:46 schrieb Peter Collingbourne:
> On Wed, Sep 07, 2011 at 11:04:42PM -0400, Jean-Christophe Fillion-Robin
wrote:
> > -- Forwarded message --
> > From: Peter Collingbourne
> > Date: Wed, Sep 7, 2011 at 9:17 PM
> > Subject: Proposal: restat ru
Tested cmake/ninja with Blender's cmake files, works well, and fast!
Single file rebuild is 0.97 sec, same on makefiles was 3.7sec.
btw, we do something similar to LLVM with generating source, only
updating if it changes, however only for C files not headers, ninja
handles this ok for my quick tes
On Thu, Sep 8, 2011 at 2:54 PM, Peter Collingbourne wrote:
>
> I am planning to submit the Ninja generator as a patch to CMake
> upstream once it has been put through more exhaustive testing and
> certain known issues have been resolved (my post to ninja-build being
> one of them).
>
Very cool!
Essentially what I've tried to do is:
ExternalProject_Add(aproject
...)
ExternalProject_Add_Step(aproject customstep
DEPENDEES build
COMMAND ${CMAKE_COMMAND} -E rename foo-* foo
...)
This appears to have generated the following:
cd /path/to/working/directory && /usr/bin/cmake -E
CMake generates all the Makefiles by itself and then creates a standard
Makefile-Project for Eclipse/CDT on top of them. This is different from
(native) 'Managed Build' in Eclipse/CDT where the project configuration
and dependency tree is pure XML and the underlying toolchain is
integrated by adapt
The project is adding it, and I will check on how it is doing it. Its only C
files.
-David
From: Glenn Coombs [mailto:glenn.coo...@gmail.com]
Sent: Thursday, September 08, 2011 11:41 AM
To: David Dunkle
Cc: David Cole; cmake@cmake.org
Subject: Re: [CMake] novice question: modification of FLAGS r
On Wed, Sep 07, 2011 at 11:04:42PM -0400, Jean-Christophe Fillion-Robin wrote:
> -- Forwarded message --
> From: Peter Collingbourne
> Date: Wed, Sep 7, 2011 at 9:17 PM
> Subject: Proposal: restat rules
> To: ninja-bu...@googlegroups.com
FWIW, the Ninja generator I have been worki
On Thu, Sep 8, 2011 at 11:17 AM, wrote:
> The reason I didn't check _SBCS is that I introduced that as a control
> to CMake. _MBCS and _UNICODE are defined by the compiler based on the
> CharacterSet setting.
OK, but since you're using it as a target level #define, it should be
defined in the t
Is the -m32 flag being provided as a default by cmake, or are you specifying
it yourself ? If the latter, then maybe it has been added to the
COMPILE_DEFINITIONS property instead of the CMAKE_C_FLAGS variable. I have
seen CMakeList.txt files use add_definitions(-m32) rather than adding it to
the
I inherited this cmake build that builds a complex project with a fairly large
directory tree. Part way through it switches compilers, with code similar to
what is below, and builds a few subdirectories using the new compilers. The
compiler flags for the original compilers (compiler A) bleeds th
On Thu, Sep 8, 2011 at 3:39 PM, David Cole wrote:
> On Thu, Sep 8, 2011 at 9:30 AM, Delphinus Delphinus wrote:
> > Hi all,
> >
> > I am using the Qt module QTestLib to do some tests on my application
> > (windows, MSVC 2008) that has been all set up with CMake.
> >
> > A test I have created with
The reason I didn't check _SBCS is that I introduced that as a control
to CMake. _MBCS and _UNICODE are defined by the compiler based on the
CharacterSet setting. The test is being executed inside an
IF(${CMAKE_TEST_GENERATOR} MATCHES "Visual Studio"). Is that
insufficient to guarantee it only ru
On Thu, Sep 8, 2011 at 9:30 AM, Delphinus Delphinus
wrote:
> Hi all,
>
> I am using the Qt module QTestLib to do some tests on my application
> (windows, MSVC 2008) that has been all set up with CMake.
>
> A test I have created with QTestLib is executed, all output is sent to the
> command window.
Hi all,
I am using the Qt module QTestLib to do some tests on my application
(windows, MSVC 2008) that has been all set up with CMake.
A test I have created with QTestLib is executed, all output is sent to the
command window. Since I want it to a file, I used what Qt suggest to
redirect all outpu
The set_target_properties() of COMPILE_FLAGS allows you to add the -DDEBUG
just for the mylibd target (although you should really use the
COMPILE_DEFINITIONS property for preprocessor symbols). Why do you need to
mess with the part of the compile command ? Can't you add extra
compiler command fl
> There are already these feature requests that seem to cover the exact
> same topic:
>
> http://public.kitware.com/Bug/view.php?id=11845
> http://public.kitware.com/Bug/view.php?id=4034
>
Yes, the second ticket has the same idea, but, as I can see, it was
completely rejected. I personally do not
16 matches
Mail list logo