Hello Dave,
Am 05.09.2011 18:29, schrieb Johannes Stallkamp:
>
> http://www.cmake.org/Bug/view.php?id=12260
>
> is listed with target 2.8.6, but it's not listed in the changes (yet?).
>
> Will it be fixed for the next release or will it be pushed to 2.8.7?
>
>
>
Hello,
http://www.cmake.org/Bug/view.php?id=12260
is listed with target 2.8.6, but it's not listed in the changes (yet?).
Will it be fixed for the next release or will it be pushed to 2.8.7?
Regards
Johannes
___
Powered by www.kitware.com
Visit ot
Probably a bit late, but I was on vacaction:
http://www.cmake.org/Bug/view.php?id=12260
Johannes
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep message
Hi,
Would be great if
http://www.cmake.org/Bug/view.php?id=12260
would make it into 2.8.5.
Best
Johannes
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messa
Hi,
> Yes. And please use unified diff format. Preferred is if you could
> do a checkout of CMake git and commit your patch (locally) and then
> do "git format-patch HEAD^" and attach the resulting 0001-* file to
> the bug.
>
Just did so. Hope the patch format is correct. Please advise, if not.
ht
Hi,
Am 09.06.2011 13:20, schrieb Michael Wild:
> On 06/09/2011 01:11 PM, Rolf Eike Beer wrote:
>>> Hi,
>>>
>>> I just notied that CTest 2.8.4 incorrectly parses valgrind's memcheck
>>> output because it does not always take into account that numbers
>>> reported by valgrind can be larger than 1,00
Hi,
I just noticed that CTest 2.8.4 incorrectly parses valgrind's memcheck
output because it does not always take into account that numbers
reported by valgrind can be larger than 1,000 and then will contain a
comma as thousand-delimiter. Therefore, many errors/potential errors
are not correctly r
Hello,
on our build server, I have set up CTest 2.8.-rc1 to run dynamic
analysis with valgrind (3.6.0). Results are submitted to CDash 1.8.2.
However, I noticed that only results with at least one error/leak show
up in the dashboard. Tests that run flawlessly don't.
In the DynamicAnalysis.xml, a
Am 09.07.2010 12:56, schrieb Michael Hertling:
> As the version target is always out of date it will be build each time
> you (re)build main, but since CONFIGURE_FILE() obviously does not touch
> the output file as long as it won't change, version.h isn't timestamped,
> so it doesn't trigger the re
Hi,
Am 08.07.2010 22:31, schrieb Tyler Roscoe:
> On Wed, Jul 07, 2010 at 10:43:15PM -0400, John Drescher wrote:
>> On Wed, Jul 7, 2010 at 9:44 PM, Clark Gaebel
wrote:
>>> I would like to generate file that looks something like this:
>>>
>>>// version.h
>>>#define VERSION "v0.1-345-ga77ede
Hello Romain,
Romain CHANU schrieb:
> If I need to compile a library on both Linux and Windows, the best
> CMake practice would be to write toolchain files for Linux and
> Windows (cf. http://www.cmake.org/Wiki/CMake_Cross_Compiling)
>
> Is that correct?
Do you really want to cross-compile (i.e. b
Hello,
if I use
FIND_PACKAGE( OpenMP )
I get the variables OpenMP_C_FLAGS and OpenMP_CXX_FLAGS correctly set
to "/openmp" for VC2005.
Is it correct behaviour that these are not automatically added to the
CMAKE_CXX_FLAGS_[RELEASE|DEBUG] variables (and thus, the option is
not configured in VC's
Hello,
I am still trying to get ctest working on our directory structure.
Thanks to the bugfix in 2.8, running the test itself works fine.
However, there seems to be an issue with code coverage testing.
Assuming the following directory structure:
projects/
libFoo/
cmake
CMak
Richard,
Richard Wackerbarth schrieb:
> Johannes,
>
> Is there any compelling reason to place the cmake "control files" in a
> directory under the root?
>
> Foo/
>CMakeLists.txt
>CTestConfig.cmake
>include
> Foo.h
>src
> Foo.cpp
> FooTest.cpp
>
> is a more convent
Hello,
I am still experimenting and learning how to setup CTest/CDash support
for our projects.
We have the following directory structure for our projects:
Foo/
cmake
CMakeLists.txt
CTestConfig.cmake
include
Foo.h
src
Foo.cpp
FooTest.cpp
Running CM
Tyler Roscoe schrieb:
> On Mon, Nov 09, 2009 at 07:18:05PM +0100, Johannes Stallkamp wrote:
>
>> Are there any reasons the suggested patch in
>> http://public.kitware.com/Bug/view.php?id=9090 is not integrated into
>> current CMake version?
>>
>
> Loo
Hello,
sorry for asking this right after the release of CMake 2.8, but I only
stumpled upon the problem right now (using 2.6, however).
Are there any plans to fix
http://public.kitware.com/Bug/view.php?id=9090 (still marked as
"open")? We actually do have the same situation that we add
"subdirect
Hello,
I have another problem with CPack and NSIS package generator:
I currently create a CMake component for each sub-project/component of
my software.
The sub-project CMakeLists.txt use cpack_add_component(...) to define
display name, description and especially dependencies.
Now, appA might d
Hello,
I have a question concerning component-based install with CPack and NSIS:
Among others, I have a library libA and a component depending on that
library, appA.
Using CPACK_COMPONENT_APPA_DEPENDS I can achieve that libA is
installed if I select appA.
But: If appA is the only component depe
Hello list,
is it possible to set a relative path as CMAKE_MODULE_PATH ? I
actually had problems with that (CMake 2.6.3-RC 8)
Is it because the relative path would be resolved w.r.t current build
dir and not w.r.t. to the directory with CMakeLists.txt ?
Reason:
I want to point CMAKE_MODULE_PATH t
20 matches
Mail list logo