>> This will never happen with CMake. CMake will always be required to be on
>> the machine doing the build. There is just no other way to do system
>> introspection. Also, if you don't have something like CMake around it is
>> hard to write cross platform build files that are complex in anyway
On Thu, Feb 17, 2011 at 4:23 PM, Bill Hoffman wrote:
>>> I think one of their main points was to generate standalone projects
>>> that do not require CMake to build.
>>
>> Yes. As mentioned in point 5.
>>
> This will never happen with CMake. CMake will always be required to be on
> the machine d
-- Forwarded message --
From: Emmanuel Blot
Date: Fri, Feb 18, 2011 at 11:48 PM
Subject: Re: [CMake] New warnings in CMake 2.8.4-rc2
To: David Cole
> If a variable is not used, then simply do not define it on the cmake
> command line.
Thanks, but I simply can't. If I could, I w
On 18.02.2011 20:48, David Cole wrote:
There are many pros for this idea, but a very important con: People will
use it as a general purpose programming language (see what often happens
to SCons projects). Even CMake has this problem to a lesser extent (IMHO
mainly because it's a PITA to program
On Fri, Feb 18, 2011 at 2:42 PM, Troy Straszheim
wrote:
> On Fri, Feb 18, 2011 at 8:16 AM, Michael Wild wrote:
>>
>>> 2. Tcl (or other) scripting language, which has clearly defined variable
>>> scoping rules and well understood semantics.
>>
>> There are many pros for this idea, but a very impor
On Fri, Feb 18, 2011 at 8:16 AM, Michael Wild wrote:
>
>> 2. Tcl (or other) scripting language, which has clearly defined variable
>> scoping rules and well understood semantics.
>
> There are many pros for this idea, but a very important con: People will
> use it as a general purpose programming
Hello,
Responses inline to 1 and 2 below:
Thanks,
Juan
On Fri, Feb 18, 2011 at 10:16 AM, Michael Wild wrote:
> On 02/18/2011 04:48 PM, j s wrote:
> > Hello,
> >
> > There is nothing wrong with another build system. Not all build systems
> fit
> > everyone needs, much like subversion and git
On Friday 18 February 2011, James Amundson wrote:
> Hi,
>
> Are there any CMake solutions for running tests in a cross-compiling
> environment? Right now I have a lovely test suite that runs over sixty
> different executables using the standard CMake and CTest setup. It works
> exactly as I want un
Bug reported:
http://public.kitware.com/Bug/view.php?id=11877
On Fri, Feb 18, 2011 at 10:30 AM, David Cole wrote:
> Yup. ctest -N and ctest without -N differ in test ordering.
>
> Congratulations! You've reported the first regression bug in CMake
> 2.8.4! :-)
>
> I suspect the change for thi
On 02/18/2011 04:48 PM, j s wrote:
> Hello,
>
> There is nothing wrong with another build system. Not all build systems fit
> everyone needs, much like subversion and git being suitable for different
> development styles.
>
> When I have the time, I will start developing my own build system. It
On Friday 18 February 2011, Schmid Alexander wrote:
> Hi,
>
> of course, I´d like to have you think further about it, so here you go...
;-)
> This is the toolchain file I use.
> The specialty about is that I want to use the ARMCC as compiler and an
> SDK-provided linker tool for linking.
>
> # th
On 02/18/2011 04:36 PM, James Amundson wrote:
> Hi,
>
> Are there any CMake solutions for running tests in a cross-compiling
> environment? Right now I have a lovely test suite that runs over sixty
> different executables using the standard CMake and CTest setup. It works
> exactly as I want under
Hello,
There is nothing wrong with another build system. Not all build systems fit
everyone needs, much like subversion and git being suitable for different
development styles.
When I have the time, I will start developing my own build system. It will
have the following proposed features.
1. D
Hi,
Are there any CMake solutions for running tests in a cross-compiling
environment? Right now I have a lovely test suite that runs over sixty
different executables using the standard CMake and CTest setup. It works
exactly as I want under Linux, but now I need to run it on a
cross-compiling
Yup. ctest -N and ctest without -N differ in test ordering.
Congratulations! You've reported the first regression bug in CMake
2.8.4! :-)
I suspect the change for this bug [
http://public.kitware.com/Bug/view.php?id=11561 ] has introduced this
issue. I'll make a new issue that we can hopefull
Hi Brad,
On Mon, Feb 7, 2011 at 7:14 PM, Brad King wrote:
> Hi Johan,
>
> Let's move this over to the developers' list. I'm cc-ing the users' list
> just for this transition message. Thanks.
>
> On 02/05/2011 06:50 PM, Johan Björk wrote:
> > The fix is extremely simple, in cmCTestGIT.cxx:266
>
ADD_DEFINITION sets the definitions for a compiler without target
binding. This means once it is used all subsequent targets and
subdirectories have these definitions
ADD_DEFINITIONS(-DHAVE_CONFIG_H -DEXCLUDE ALL_PINGUINS)
COMPILE_DEFINITIONS is a property which is used frequently with
SET_TARGET_
Dear all,
I haven't been using CMake (and hence following) for almost 3 years and I
suppose it has a big progress since 2.4.
Now I'm looking for most kosher way to specify external dependencies for a
particular project. The most straightforward way of specifying include dirs
and libraries when po
18 matches
Mail list logo
