Von: Christophe Cavalaria <[EMAIL PROTECTED]>
> Alexander Neundorf wrote:
>
> >
> > Von: Christophe Cavalaria <[EMAIL PROTECTED]>
> >
> > ...
> >> Any idea why it is so? The project file itself correctly configures a
> >> file filter for the Headers, it's just that no header file is in the
> >
Bill Hoffman wrote:
Brandon J. Van Every wrote:
For clarity, let's say I make 2 static libraries:
- pcre_static_pic, for use with our shared libchicken et al
- pcre_static_nopic, for use with our libchicken-static et al
The latter case runs into the "static library as part of a static
library
Hi Ken,
On 1/23/07, Ken Martin <[EMAIL PROTECTED]> wrote:
> The problem with DART_TESTING_TIMEOUT and CTEST_TEST_TIMEOUT is that
> they apply to the complete test suites. What I'm trying to solve is
> some infinite loops test cases, I like the tests to fail/timeout but
> the next tests should be
On Tuesday 23 January 2007 18:10, kitts wrote:
> On Tuesday 23 January 2007 00:03 IST, kitts wrote:
> > 2) On windows, we would like to use VS as the IDE and KDevelop on linux.
> > Both are capable of crosscompiling (use non-native compilers). I think
> > this is only possible by setting CMAKE_C_CO
Yes, I can arrange it into two different modes. I was seeing if I
could get it done in just one. I'm new to CMake so I wasn't aware
about //. It seams strange that both # and // would be comments in the
cache files, but only # is a comment in the cmake files.
But that being the case. I can't thin
Alexander Neundorf wrote:
>
> Von: Christophe Cavalaria <[EMAIL PROTECTED]>
>
> ...
>> Any idea why it is so? The project file itself correctly configures a
>> file filter for the Headers, it's just that no header file is in the
>> project.
>
> Because you didn't list them as source for the tar
Am Dienstag 23 Januar 2007 02:48 schrieb Bill Hoffman:
> OK, found it...
> You need to add this:
> SET(CMAKE_INCLUDE_FLAG_ASM "-I")
> To CMakeASMInformation.cmake.
>
> I will also fix the seg fault, but this will get around the bug.
Thx, the work-around really helps.
Cheers,
--
(°=
On 1/23/07, Stuart Tett <[EMAIL PROTECTED]> wrote:
I downloaded the cmake-mode.el and noticed that it doesn't highlight
the CMakeCache.txt files. I customized it to do this.
This is great!
Since these
files have "# comments" and "// comments" (I also allowed "/* comments
*/" though I don't k
Hello,
I would like to be able to use Guard Malloc while running my dashboard
tests. (Guard Malloc is a Mac OS X feature that is similar to Purify
and Valgrind, that is, it tests for memory-related bugs).
To use Guard Malloc, one only needs to set an environment variable.
I've tried adding said
On Tuesday 23 January 2007 00:03 IST, kitts wrote:
> 2) On windows, we would like to use VS as the IDE and KDevelop on linux.
> Both are capable of crosscompiling (use non-native compilers). I think
> this is only possible by setting CMAKE_C_COMPILER to the compiler to use?
I tested this today and
I downloaded the cmake-mode.el and noticed that it doesn't highlight
the CMakeCache.txt files. I customized it to do this. Since these
files have "# comments" and "// comments" (I also allowed "/* comments
*/" though I don't know if these are actually supported. And I set it
up to highlight the "K
> The problem with DART_TESTING_TIMEOUT and CTEST_TEST_TIMEOUT is that
> they apply to the complete test suites. What I'm trying to solve is
> some infinite loops test cases, I like the tests to fail/timeout but
> the next tests should be executed as well.
Just to make sure we are on the same page
On 1/23/07, Ken Martin <[EMAIL PROTECTED]> wrote:
There are two ways to globally put a time limit on each test IIRC. One is
to set DART_TESTING_TIMEOUT (see Modules/CTest.cmake) to the number of
seconds to let a test run, the other is to set CTEST_TEST_TIMEOUT in your
ctest script IIRC. I do not
There are two ways to globally put a time limit on each test IIRC. One is
to set DART_TESTING_TIMEOUT (see Modules/CTest.cmake) to the number of
seconds to let a test run, the other is to set CTEST_TEST_TIMEOUT in your
ctest script IIRC. I do not believe there is a way to do it on a per test
basis
Alexander Neundorf wrote:
Hi,
see subject.
1) Is it possible to force a different compiler than cl.exe into a MSVC 6
project ? Setting the CMAKE_C_COMPILER variable in the cmake file doesn't have
this effect.
MSVC 6 is done with templates. To change the compiler, I would guess
you would
Hi,
see subject.
1) Is it possible to force a different compiler than cl.exe into a MSVC 6
project ? Setting the CMAKE_C_COMPILER variable in the cmake file doesn't have
this effect.
2) I have a custom command which calls sh -c "...lengthy cygwin command".
When trying to build this in MSVC6 it
Brandon J. Van Every wrote:
Bill Hoffman wrote:
Brandon J. Van Every wrote:
Bill Hoffman wrote:
There are no other differences in the PCRE library. It is straight
C code, not Chicken output, so it doesn't need any of Chicken's
usual flags. It is a properly independent sub-library. We just
17 matches
Mail list logo
