Hi Klaim,
I would try to start with just one (base-)project, try to get
everything in place and building the way you want it. If you're new to
CMake, that's really the way to go. Once you have this base-project
ready, you can think of starting a second project, using the
base-project as
Hello,
Is there a way to pass the ctest -E flag to a visual studio 10 configuration
to prevent certain tests from running in the regressions?
Thanks,
Juan
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
Hicham,
Sorry for confusing. I supposed you asked about how to handle different
versions of the Boost (1.42, 1.44 etc) on the same build server.
On 6 December 2010 00:16, Hicham Mouline hic...@mouline.org wrote:
-Original Message-
From: philiplow...@gmail.com
I would try to start with just one (base-)project, try to get
everything in place and building the way you want it. If you're new to
CMake, that's really the way to go. Once you have this base-project
ready, you can think of starting a second project, using the
base-project as
By the way, I'm using a set of test projects to play with CMake and
understand clearly how it works, so I can experiment.
On Tue, Dec 7, 2010 at 11:59, Klaim mjkl...@gmail.com wrote:
I would try to start with just one (base-)project, try to get
everything in place and building the way you
-Original Message-
From: Dmytro Ovdiienko [dmitriy.ovdie...@gmail.com]
Date: 07/12/2010 10:57 AM
To: Hicham Mouline
CC: Philip Lowman , CMake mailing list , boost-bu...@lists.boost.org
Subject: Re: [CMake] FindBoost: find both win32 and x64 static libs
Hicham,
Sorry for confusing. I
On Sunday, December 5, 2010, Hicham Mouline hic...@mouline.org wrote:
I've built both win32 and x64 versions of boost thread library with the
following 2 lines:
1. 32bit cl.exe from msvc9 directory in the %PATH%
bjam --with-thread --layout=versioned toolset=msvc address-model=64
On 11/28/2010 09:10 AM, Alan W. Irwin wrote:
On 2010-11-28 06:39+0100 Michael Hertling wrote:
On 11/27/2010 06:45 PM, Alan W. Irwin wrote:
I just discovered that many Linux distros these days use the
--as-needed Linux linker option by default. At first glance that
option makes a lot of
Folks -
I've opened a ticket
http://public.kitware.com/Bug/view.php?id=11575 to include my WiX
patch I made a while back, and updated to target 2.8.3 src. Please
update said ticket with your questions/comments/complaints as I'm
determined to get this in your next point release.
--
Cheers,
See my comments in the bug report.
Thanks,
David
On Tue, Dec 7, 2010 at 9:00 AM, Tim St. Clair timoth...@gmail.com wrote:
Folks -
I've opened a ticket
http://public.kitware.com/Bug/view.php?id=11575 to include my WiX
patch I made a while back, and updated to target 2.8.3 src. Please
On Tue, Dec 07, 2010 at 02:39:18AM -0600, j s wrote:
Is there a way to pass the ctest -E flag to a visual studio 10 configuration
to prevent certain tests from running in the regressions?
I don't know of a good way (and I'm not 100% sure what you mean by
prevent certain tests from running in
Any suggest for the most-proper way, in a CMakeLists.txt file, to determine
whether the Intel vs. GNU fortran compiler will be used?
I need to use different sets of source files, and different compiler flags,
depending on that detail.
Christian Convey
Scientist, NUWC Division Newport
1176
On 12/07/2010 05:15 PM, Convey, Christian J CIV NUWC NWPT, B-171 wrote:
Any suggest for the most-proper way, in a CMakeLists.txt file, to determine
whether the Intel vs. GNU fortran compiler will be used?
I need to use different sets of source files, and different compiler flags,
depending
Yes it's true I didn't think of this one. It work nicely, here what I
have done:
wget http://googletest.googlecode.com/files/gtest-1.5.0.tar.bz2
tar xjvf gtest-1.5.0.tar.bz2
cd gtest-1.5.0
mkdir my-test
vim CMakeLists.txt # Add ADD_SUBDIRECTORY(my-test)
cd my-test
# SIMPLE HEADER FILE
vim
Thx for replying,
But it didn't change by switching it.
Regards,
Kevyn-Alexandre Paré
On Wed, 2010-12-01 at 22:14 +, Fraser Hutchison wrote:
Hi Kevyn-Alexandre,
I think moving the -lpthread to after ${GTEST_LIB_PATH}gtest.a
${GTEST_LIB_PATH}gtest_main.a should help.
Cheers,
Thx for replying,
It seem that my simple example and using a add_subdirectory and reusing
CMakelists.txt of the gtest source solved my problem.
Regards,
On Sat, 2010-12-04 at 05:48 -0500, Philip Lowman wrote:
On Wed, Dec 1, 2010 at 10:59 AM, Kevyn-Alexandre Paré
kap...@rogue-research.com
I've been using CMAKE for a few years now and I absolutley LOVE it.
It makes my life as a programmer so much easier to be able to generate project
files on any platform.
What hurts is doing the reverse. I can't count how many hours I've spent
converting Solutions, Projects and Makefiles
Funny timing - I just did that today, at least in a crude manner.
Long story short: On Unix/Linux/Mac, you can use the command-line tools (grep,
sed, cut, xargs, etc.) to get the list of all source file that comprise the
solutions' projects. If your needs aren't too fancy, it's pretty trivial
On Tue, Dec 7, 2010 at 2:14 PM, Paul Dean aquawic...@hotmail.com wrote:
I've been using CMAKE for a few years now and I absolutley LOVE it.
It makes my life as a programmer so much easier to be able to generate
project files on any platform.
What hurts is doing the reverse. I can't count how
Thanks. I have examples (for documentation) which run much longer than the
standard regressions.
Juan
On Tue, Dec 7, 2010 at 10:15 AM, Tyler Roscoe ty...@cryptio.net wrote:
On Tue, Dec 07, 2010 at 02:39:18AM -0600, j s wrote:
Is there a way to pass the ctest -E flag to a visual studio 10
Just want to say that since I want to test C code i need this in my
header file (for more details see
http://en.wikipedia.org/wiki/Compatibility_of_C_and_C%2B%
2B#Linking_C_and_C.2B.2B_code):
#ifdef __cplusplus /* If this is a C++ compiler, use C linkage */
extern C {
#endif
void function ();
From: philiplow...@gmail.com [mailto:philiplow...@gmail.com] On Behalf Of
Philip Lowman
Sent: 07 December 2010 13:17
To: Hicham Mouline
Cc: Philip Lowman; Dmytro Ovdiienko; CMake mailing list;
boost-bu...@lists.boost.org
Subject: Re: [CMake] FindBoost: find both win32 and x64 static libs
On
Hi,
On Tue, Dec 07, 2010 at 02:25:18PM -0500, cmake-requ...@cmake.org wrote:
Message: 4
Date: Tue, 7 Dec 2010 13:14:19 -0600
From: Paul Dean aquawic...@hotmail.com
Subject: [CMake] Creating CMakeLists files from Solutions,Projects
and Makefiles
I've been using CMAKE for a few
On 07.12.10 14:31:56, John Drescher wrote:
On Tue, Dec 7, 2010 at 2:14 PM, Paul Dean aquawic...@hotmail.com wrote:
I've been using CMAKE for a few years now and I absolutley LOVE it.
It makes my life as a programmer so much easier to be able to generate
project files on any platform.
On 07.12.10 13:14:19, Paul Dean wrote:
I've been using CMAKE for a few years now and I absolutley LOVE it.
It makes my life as a programmer so much easier to be able to generate
project files on any platform.
What hurts is doing the reverse. I can't count how many hours I've spent
And without the
goal of switching from qmake to cmake, I don't see any point in doing a
conversion in the first place - after all qmake can build the project on
all interesting platforms already (else it would've been replaced).
The reason I want this is there are a few QMake based libraries
On 07.12.10 23:52:10, Andreas Pakulat wrote:
On 07.12.10 13:14:19, Paul Dean wrote:
I've been using CMAKE for a few years now and I absolutley LOVE it.
It makes my life as a programmer so much easier to be able to generate
project files on any platform.
What hurts is doing the
On Dec 7, 2010, at 4:27 PM, Hicham Mouline wrote:
From: philiplow...@gmail.com [mailto:philiplow...@gmail.com] On Behalf Of
Philip Lowman
Sent: 07 December 2010 13:17
To: Hicham Mouline
Cc: Philip Lowman; Dmytro Ovdiienko; CMake mailing list;
boost-bu...@lists.boost.org
Subject: Re:
In the process of attempting to fix this, I learned a lot of stuff about
how COST is handled that I've never encountered in the docs. Am I
missing something?
Here are some notes I made about the behavior of COST in CTest. If
others find them useful, I'd be happy to put them in the Wiki if someone
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 65d442299fba56e0e05a3b475455cb194e2d917f (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 d2edef4c09d2a68363ccd23080df1d7c56cbeb36 (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 f8719ead3fd52e6a97bc873fc1195bf552800ed1 (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 7a51a2131a40aca492ed26b5ffa0686f99dad5ed (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 36eb4f9fcdac1060fbac68c35900dc2deb2fd6eb (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, master has been updated
via 02a8ea2d5b0b41858be8a9e28d41e06af744fd0b (commit)
from
35 matches
Mail list logo
