Hi Brad,
adding set(CMAKE_INCLUDE_FLAG_C -I ) (and, just to be sure, its C++
cousin) did the trick all right. I can now build PLplot's Fortran
bindings and examples using the Compaq Visual Fortran compiler.
The only thing that worries me is that this may have an impact on
the C compiler too, as
Hi all!
I'm porting cmake to interix for use in my company. It seems to work
quite well on single core machines. however, when it comes to multicore,
interix has several severe bugs. fixing those may (better: _will_) take
a lot of time. in the meantime i'm trying to hack around things.
i'm
Hi Alexander, I'm not very skilled in Symbian developing, but I created
a simple program for Symbian with Qt libraries. I will be happy to test
your CMake patches for Symbian support, but I cannot understand how to
apply them:
- in which order should I use them?
- where ParseArgs.cmake and
I've modified my local FindDoxygen.cmake to be compatible with the
latest versions of Graphviz, which were not be picked up by the module
in CMake 2.8.0 on Windows, as follows:
--- FindDoxygen.cmake.old 2010-02-17 11:59:27.71875 +
+++ FindDoxygen.cmake 2010-02-17
CMake 2.8.1 RC 3 is ready to try:
http://www.cmake.org/files/v2.8/?C=M;O=D
Please try your projects with it. If you find any issues, let me know.
I think we are getting very close to the actual release. Pretty much
regressions only at this point, so PLEASE test your software with this
Markus Duft wrote:
Hi all!
[snip]
i thought of introducing some lame timeout when select()ing the signal
pipe, then checking whether the process is still alive (wait()), and
again selecting if it is. what do you think?
answering my own mail, i came up with a patch in the meantime, which
Markus Duft wrote:
cmakes implementation of how child processes are handled doesn't work
reliably on multicore interix. it seems that every other SIGCHLD is lost
Is this a known problem on that platform, independent of CMake?
The ProcessUNIX.c implementation is for POSIX platforms, which
I did not want to get into the technical thread on this issue, so I
created a new message. Markus, will you be able to run a dashboard for
this platform? It is sort of a requirement for accepting patches like
this into CMake. Otherwise, we are sure to break things in the future
and not
Bill Hoffman wrote:
I did not want to get into the technical thread on this issue, so I
created a new message. Markus, will you be able to run a dashboard for
this platform? It is sort of a requirement for accepting patches like
this into CMake. Otherwise, we are sure to break things in the
Brad King wrote:
Markus Duft wrote:
cmakes implementation of how child processes are handled doesn't work
reliably on multicore interix. it seems that every other SIGCHLD is lost
Is this a known problem on that platform, independent of CMake?
it is independant of cmake, yes. it is not
Markus Duft wrote:
Brad King wrote:
Can you print out the state of signal masks?
how can i do that? i'm not really into that topic that much :) but i'll
read some man pages to figure it out.
Look at sigprocmask docs.
it seems that i'm not hit by the select problem, as there is already a
Are you effectively just using the SUA component that is included with
Windows? If so, that's not too hard for someone who is already testing
Windows to start testing on.
On a semi-related note: have you considered using MSYS? I've used it to
build auto*-based Win32 applications, and while
Just stumbled upon that problem. I have files like *.darwin.cpp
And get_filename_component returns .darwin.cpp for the extension which is
wrong!
The extension is .cpp.
Let s take the example of toto.tar.gz. It s a gz file, not tar.gz file. To
see why it s wrong we can think of file
Hi all,
I was trying to use CUDA_COMPILE_PTX to make nvcc compile *.cu files
to .ptx files but with no success.
Running make just compile my regular .cpp files and does nothing to .cu
files. I want the ptx files to use them with CUDA driver API.
I checked in the trunk SVN repository of FindCUDA
On 2010-02-17 10:39-0500 Bill Hoffman wrote:
CMake 2.8.1 RC 3 is ready to try:
http://www.cmake.org/files/v2.8/?C=M;O=D
Bill, could you please include gpg signature files with each form of your
downloadable release files? If the user imports your public key from your
website or a keyserver
Hi,
Is it possible to specify the build options such as release/debug etc
when building the nmake files generated by cmake ?
Thanks,
Vikas
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
I've got a preliminary Continuous Integration system up and running
based on the scripts Bill pointed me to. Thanks Bill!
I have some questions about this setup. Let me know if you think I would
get better responses on the CDash list. I'm going to break up these
questions into separate posts to
Next question:
- CDash and miscellaneous post-build steps
Now that I've got Continuous Integration up and running with CDash, I'd
like to publish my Continuous builds to a central build archive so
developers and testers can use them.
I can write post-build rules to copy my _results directory to
Have you tried setting CTEST_UPDATE_OPTIONS to contain the extra arguments for
updating the way you want?
Clint
On Wednesday 17 February 2010 02:45:17 pm Tyler Roscoe wrote:
I've got a preliminary Continuous Integration system up and running
based on the scripts Bill pointed me to. Thanks
On Wed, Feb 17, 2010 at 03:16:13PM -0700, Clinton Stimpson wrote:
Have you tried setting CTEST_UPDATE_OPTIONS to contain the extra arguments
for
updating the way you want?
This affects the svn update command itself (which is working fine
without further adjustment) but does not appear to
Hello,
I am trying to find all release notes for CMake. I am currently using the if
(... VERSION_NEWER ...) and I know that it has not always been available and
would like to avoid downloading all past versions of CMake to figure out when
it was added to have the correct
On 02/17/2010 03:49 PM, Tyler Roscoe wrote:
On Wed, Feb 17, 2010 at 03:16:13PM -0700, Clinton Stimpson wrote:
Have you tried setting CTEST_UPDATE_OPTIONS to contain the extra arguments for
updating the way you want?
This affects the svn update command itself (which is working fine
You need to add ${ptxfiles} to your add_executable command, so that it
contains both the source and generated files.
For makefile targets you need to establish a dependency between the target
(cuda_core_test) and your ptx files. This is done by putting the generated
files into the target. For
I've been meaning to add something like that to our nightly builds just
using shell/batch scripting. You should be able to set CMAKE_PREFIX_PATH in
the initial cache and then just make install or use the vs command line app
to run the INSTALL project after calling ctest -S.
Not sure on how to
On Wed, Feb 17, 2010 at 04:16:15PM -0700, Clinton Stimpson wrote:
On 02/17/2010 03:49 PM, Tyler Roscoe wrote:
On Wed, Feb 17, 2010 at 03:16:13PM -0700, Clinton Stimpson wrote:
Have you tried setting CTEST_UPDATE_OPTIONS to contain the extra
arguments for
updating the way you want?
On Wed, Feb 17, 2010 at 06:50:19PM -0500, Philip Lowman wrote:
I've been meaning to add something like that to our nightly builds just
using shell/batch scripting. You should be able to set CMAKE_PREFIX_PATH in
the initial cache and then just make install or use the vs command line app
to run
I do this to get test results:
# find dir containing testing files
FILE(READ ${CTEST_BINARY_DIRECTORY}/Testing/TAG TAG_FILE)
STRING(REGEX MATCH [^\n]* TEST_FILE_DIR ${TAG_FILE})
SET(TEST_FILE_DIR ${CTEST_BINARY_DIRECTORY}/Testing/${TEST_FILE_DIR})
SET(test_passed 0)
CTEST_TEST(BUILD
Adding precompiled header support doesn't have to be a massive amount of
work.
Fundamentals:
1. Include the header in every source module,
2. Compile the header once for every target (so that compiler flags
match),
There are three possible build environments:
1. Full precompiled
Brad King wrote:
Markus Duft wrote:
Brad King wrote:
Can you print out the state of signal masks?
how can i do that? i'm not really into that topic that much :) but i'll
read some man pages to figure it out.
Look at sigprocmask docs.
it seems that i'm not hit by the select problem, as
Hi all.
Im using latest (2.8 CMake) under Windows, VisualStudio 2008.
When I mix x86 and x64 builds, I would like to separate the actual output
directory for the builds so that I dont get problems about mixing build
types.
Right now, the obj files etc is created in: src\foo.dir\Debug
no matter
Ryan Pavlik wrote:
Are you effectively just using the SUA component that is included with
Windows? If so, that's not too hard for someone who is already testing
Windows to start testing on.
yeah - i'm using the SUA component, and on top of that i am building
gentoo prefix [1], which i use to
31 matches
Mail list logo
