Hi,
I'm trying to invoke the C compiler in cmake as would happen with an
add_excecutable command, but I don't want to generate an object file. Basically
I have a script which generates a c file, I want to compile that file in the
environment I've set up, while passing the -S flag. I then want
Oops! Forgot to CC to the list.
Hi Tod,
I'll try to answer some of your questions below inline (I've snipped off
parts of your mail). We're also using a BlueGeneP, but not for so many
packages/executables as you probably do.
On Wed, 2010-06-23 at 01:02 -0700, Todd Gamblin wrote:
Hi,
-- 8
On 06/24/2010 08:29 AM, Tom Birch wrote:
Hi,
I'm trying to invoke the C compiler in cmake as would happen with an
add_excecutable command, but I don't want to generate an object file.
Basically I have a script which generates a c file, I want to compile that
file in the environment I've
I'm writing a (new style) ctest script. When I run it, I want it to check out
the project's source code, as it was at the very beginning of the day (00:00).
What's the right way to do this? (BTW, I'm using Subversion.)
I would have assumed it's done by setting CTEST_NIGHTLY_START_TIME, but
Could someone explain something to me about CTest's conventions?
I'm reading throught this page:
http://www.cmake.org/Wiki/CTest:Using_CTEST_and_CDASH_without_CMAKE
It sounds like the variable CTEST_CHECKOUT_COMMAND is meant to contain the
ensure checkout command, including all arguments.
I'm reading throught this page:
http://www.cmake.org/Wiki/CTest:Using_CTEST_and_CDASH_without_CMAKE
It sounds like the variable CTEST_CHECKOUT_COMMAND is meant
to contain the ensure checkout command, including all arguments.
Wow, I'm typing miserably lately.
s/ensure/entire
smime.p7s
On Thu, Jun 24, 2010 at 12:34 AM, Michael Wild them...@gmail.com wrote:
On 24. Jun, 2010, at 3:11 , Bill Hoffman wrote:
On 6/23/2010 6:12 PM, Michael Jackson wrote:
From a clean build, it does not work:
1 wget
http://www.cmake.org/files/v2.8/cmake-2.8.1.tar.gz
On Thu, Jun 24, 2010 at 11:43 AM, j s j.s4...@gmail.com wrote:
On Thu, Jun 24, 2010 at 12:34 AM, Michael Wild them...@gmail.com wrote:
On 24. Jun, 2010, at 3:11 , Bill Hoffman wrote:
On 6/23/2010 6:12 PM, Michael Jackson wrote:
From a clean build, it does not work:
1 wget
You can specify the update options.. for instance :
CVS_UPDATE_OPTIONS:STRING=-d -A -P
similarly, there's
SVN_UPDATE_OPTIONS
--
karthik
On Thu, Jun 24, 2010 at 8:00 PM, Convey, Christian J CIV NUWC NWPT
christian.con...@navy.mil wrote:
I'm reading throught this page:
Turns out the problem was Macports. Removing /opt/local/bin from my
path allows the software to build. What external commands are used in
generating FundamentalType.h, because I bet it might be one of those
stupid gnu/darwin conflicts?
Should I file a bug that cmake can't build itself with
On Thu, Jun 24, 2010 at 10:27 AM, Convey, Christian J CIV NUWC NWPT
christian.con...@navy.mil wrote:
Could someone explain something to me about CTest's conventions?
I'm reading throught this page:
http://www.cmake.org/Wiki/CTest:Using_CTEST_and_CDASH_without_CMAKE
It sounds like the
On 6/24/2010 12:25 PM, Bill Hoffman wrote:
On 6/24/2010 12:15 PM, j s wrote:
I bootstrapped a version of cmake, and used it to build itself. This
didn't work until I removed /opt/local/bin (Macports) from my path.
I then built cmake with the Macports version of cmake, and it also
worked after
On 6/24/2010 12:15 PM, j s wrote:
I bootstrapped a version of cmake, and used it to build itself. This
didn't work until I removed /opt/local/bin (Macports) from my path.
I then built cmake with the Macports version of cmake, and it also
worked after removing /opt/local/bin.
So how is
On 6/24/2010 12:25 PM, Bill Hoffman wrote:
On 6/24/2010 12:15 PM, j s wrote:
I bootstrapped a version of cmake, and used it to build itself. This
didn't work until I removed /opt/local/bin (Macports) from my path.
I then built cmake with the Macports version of cmake, and it also
worked after
So if I remove /opt/local/bin from my path, but use /opt/local/bin/cmake
(Macports) to build, it will work.
The compiler found is /usr/bin/gcc when /opt/local/bin/ is not in my path.
In our group we typically symlink /opt/local/bin to gcc-mp-4.3, which may be
causing the conflict. I do know
Thanks. How does ctest know whether to employ CVS_UPDATE_OPTIONS vs.
SVN_UPDATE_OPTIONS ?
Also, the format you gave for CVS_UPDATE_OPTIONS looks like it has hte format
of a line in the cache file. Is there some reason I'd need to force it into
the cache, or is it okay for me to achieve the
On Thu, Jun 24, 2010 at 10:57 PM, Convey, Christian J CIV NUWC NWPT
christian.con...@navy.mil wrote:
Thanks. How does ctest know whether to employ CVS_UPDATE_OPTIONS vs.
SVN_UPDATE_OPTIONS ?
Based on what CTEST_UPDATE_TYPE (CVS/SVN etc) is set to. If it isn't set, it
tries to determine one
Suppose I want do just use ctest in a dead-simple manner: add a few lines to
my CMakeLists.txt files, then run cmake . make test.
In this scheme, what's the easiest way I can set CTEST_BUILD_NAME? Simply
setting that variable in my CMakeLists.txt file doesn't *seem* to be effective.
Thanks,
On Thu, Jun 24, 2010 at 03:07:50PM -0400, Convey, Christian J CIV NUWC NWPT
wrote:
Suppose I want do just use ctest in a dead-simple manner: add a few
lines to my CMakeLists.txt files, then run cmake . make test.
In this scheme, what's the easiest way I can set CTEST_BUILD_NAME?
Simply
cmake -DBUILDNAME=MyBuildName . make make test
test does not depend on all so that it can just run quickly... so you need
the middle make in the above command line if you actually want to build your
stuff first.
But why do you even need to set BUILDNAME for a make test -- it only
really
The CMake 2.8.2 release candidate stream continues!
You can find the source and binaries here:
http://www.cmake.org/files/v2.8/?C=M;O=D
If we do not get any reports of regressions from
previous releases of CMake, this release candidate
will become the final 2.8.2.
Since we switched to git, and a
Yeah, thanks, that makes sense.
Actually, another thing I like about specifying BUILDNAME on the command line
is because the shell script that invokes cmake is also a very opportune place
to compute the build name.
- C
-Original Message-
From: David Cole
Make that:
cmake -DBUILDNAME=MyBuildName . ctest -D Experimental
(forgot the '.' ...)
On Thu, Jun 24, 2010 at 3:21 PM, David Cole david.c...@kitware.com wrote:
cmake -DBUILDNAME=MyBuildName . make make test
test does not depend on all so that it can just run quickly... so you need
the
On 06/23/2010 04:10 PM, Alexander Neundorf wrote:
Hi,
On Wednesday 23 June 2010, Todd Gamblin wrote:
2. The FindMPI module's library search breaks because the the cross-compiler
name on BlueGene/P contains -l. Specifically, the GNU compute node compilers
on BlueGene/P are named
j s wrote:
So if I remove /opt/local/bin from my path, but use /opt/local/bin/cmake
(Macports) to build, it will work.
The compiler found is /usr/bin/gcc when /opt/local/bin/ is not in my
path. In our group we typically symlink /opt/local/bin to gcc-mp-4.3,
which may be causing the
You're correct about that one. This variable seems to work the same for both
old-style and new-style ctest scripts. As long as that variable is set,
then the ctest_update() step will revert the source code to that point in
time.
Based on the name of the variable, clearly it is meant to support a
On Thursday 24 June 2010, Marcel Loose wrote:
Oops! Forgot to CC to the list.
Hi Tod,
I'll try to answer some of your questions below inline (I've snipped off
parts of your mail). We're also using a BlueGeneP, but not for so many
packages/executables as you probably do.
On Wed,
Hi guys,
First off, I'd like to give my heartfelt thanks to everyone who's helped me
figure out how to use CTest in the past few weeks. I'm very grateful to you
and to those who develop CTest.
I'd like to offer one piece of constructive criticism about ctest. If found
learning how to use it
Brad King pushed this fix to cmake 'next' earlier today:
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=68c7d3e2ce2fb98980887357dd6308246ea3d64e
That, at least, addresses the -l issue in FindMPI...
HTH,
David
On Thu, Jun 24, 2010 at 4:52 PM, Alexander Neundorf a.neundorf-w...@gmx.net
Files attached
Thanks,
Juan
On Thu, Jun 24, 2010 at 2:56 PM, Brad King brad.k...@kitware.com wrote:
j s wrote:
So if I remove /opt/local/bin from my path, but use /opt/local/bin/cmake
(Macports) to build, it will work.
The compiler found is /usr/bin/gcc when /opt/local/bin/ is not in
j s wrote:
Brad King wrote:
From the CMakeOutput.log you sent it looks like the compiler
/opt/local/bin/gcc
is used while checking for the macros. Please run the build
with make VERBOSE=1 to see the full compiler command line
that fails at build time. Post it.
Files attached
[snip]
On Jun 24, 2010, at 1:52 PM, Alexander Neundorf wrote:
And the FindMPI module claims that it can't find the '-inux-g++'
library, or something similar. I was able to fix this by modifying
FindMPI's search to look for -l only when it's followed by a space.
This is a little worrisome because I
Hi all,
I'm using Xcode 3.2.2 and Perforce for my Source Code Control.
Whenever I rebuild the Xcode project with cmake, Xcode loses its
connection to the source code server and I have to reset it manually.
Does anyone have a solution for this?
Thanks in advance
Glenn
Dear all,
I use Cmake to install OTB http://www.orfeo-toolbox.org/otb/. During the making
process, some errors occurs but, the configuration is done. The building
process is also correct. And then when I test the helloworld code, I got the
helloworld.exe. When I run the execuateble
Dear all,
I use Cmake to install OTB http://www.orfeo-toolbox.org/otb/. During the making
process, some errors occurs but, the configuration is done. The building
process is also correct. And then when I test the helloworld code, I got the
helloworld.exe. When I run the execuateble
I don't think the CMake list is the place to ask this question, as it sounds
like a problem with OTB. At the very least I would ask for help first with
the developers of OTB.
Also, I would suggest when asking them, that you include the actual error
messages that you saw.
Ceej
aka Chris Hillery
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via ec10d005ce038281e634357697dcf223674fae77 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, release has been updated
via e010d1f688cac98f690e68f95f05c6763d806add (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 75b98c915ad702b74dec14f8df444721d9cff7de (commit)
via
39 matches
Mail list logo
