We have a nightly build for our project as reported here
http://my.cdash.org/viewBuildError.php?buildid=781789 which is producing an
error. The short of it is that CTest is using xcodebuild (which is correct) but
is trying to pass the “-j16” style that normal “MakeFiles” would use. I have
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 82c1f16f8c74f6cba2cf2cc2e98062559a0c072e (commit)
via
On 06/11/2015 02:20 PM, Stephen Kelly wrote:
So, KDE4 as a platform breaks the cmake compatibility design for its
downstreams. At least ECM, used by KDE Frameworks 5, doesn't do that.
That is unfortunate :(
I still think they should be unconditional warnings.
Yes, see below.
I also think
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 4f7a93d21a9f9be423a9977aae575b0356246506 (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 991e27ab5a6d3b245139ace9fde4a8efaae2f109 (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 9223c6cb12bbaea05d420e9eb562f861b242 (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 ab00ff8d7a748779d880dba0b0daff145d745a7b (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 940ea9ff4af0429396fc55d0f5643b848ff972af (commit)
via
On 06/16/2015 07:34 PM, Davy Durham wrote:
Would that involve different macro's anyhow? I could try
and write a macro specifically to check that, or were you thinking I
should be able to use the macros that are already there? And would you
be opposed to my writing a dedicated one?
Please
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 7d2c58c859f3f2a0ef0291a39b6496ae3655fd53 (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 e2e6cb7348dfffddb5d93f679fc8c69fffd3d1dc (commit)
via
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15623
==
Reported By:Eric Wing
Assigned To:
On 06/17/2015 11:07 AM, Ette, Anthony (CDS) wrote:
Please see the response below about uniquely identifying cf77.
In order to identify the compiler as cf77, do something akin to the following:
$ echo ' PROGRAM V' /tmp/nil.f
$ echo ' END' /tmp/nil.f
$ cf77 -v -o /dev/null -c
On 06/17/2015 04:56 PM, Robert Goulet wrote:
I saw the file(LOCK) command
That should be what you need. All the file_append.cmake scripts need
to agree on a file path to lock (like output.txt.lock).
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ
Is there a MAKEFLAGS or CTEST_BUILD_FLAGS in your environment?
Where does the -j16 come from? (CTest should not be injecting that
unless you are telling it to somehow, so it either comes from one of
your scripts, or your environment...)
grep for just \-j -- the value 16 may come from a variable
Nope. Neither one of those are on my environment. I am also running at Root for
this build and I have a clean .bashrc for both accounts. There must be
something in my chest.cmake file that makes CTest think it is running with a
makefile generator.
Should I post my various files?
Mike Jackson
Can you explain what you mean by strong and weak symbols?
Google is your friend
https://en.wikipedia.org/wiki/Weak_symbol
http://stackoverflow.com/questions/2290587/gcc-style-weak-linking-in-visual-studio
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ
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 83b997d41a65361e5bd56c601b2896146606cc96 (commit)
via
On Thu, Jun 18, 2015 at 1:57 AM, Dan Liew d...@su-root.co.uk wrote:
The reason I'm asking this question is because of how I handle unit
tests in CMake right now. Instead of just defining an executable
target for the test and then adding a link dependency on the library
containing the class or
On 06/18/2015 08:44 AM, Brad King wrote:
We may be able to extract that while compiling the compiler identification
source file. Try modifying Modules/CMakeDetermineFortranCompiler.cmake
and extending the list in CMAKE_Fortran_COMPILER_ID_TEST_FLAGS with -v.
Then run CMake on the tiny
20150618)
+set(CMake_VERSION_PATCH 20150619)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
On Thu, Jun 18, 2015 at 4:24 PM, Dan Liew d...@su-root.co.uk wrote:
Hi,
On 18 June 2015 at 12:16, Robert Dailey rcdailey.li...@gmail.com wrote:
On Thu, Jun 18, 2015 at 12:02 PM, Dan Liew d...@su-root.co.uk wrote:
Can you explain what you mean by strong and weak symbols?
Google is your
On Thu, Jun 18, 2015 at 12:02 PM, Dan Liew d...@su-root.co.uk wrote:
Can you explain what you mean by strong and weak symbols?
Google is your friend
https://en.wikipedia.org/wiki/Weak_symbol
http://stackoverflow.com/questions/2290587/gcc-style-weak-linking-in-visual-studio
Normally Google
On 06/18/2015 01:41 PM, James Johnston wrote:
3. Patch Windows-Embarcadero.cmake, as I propose here.
I think that makes sense.
+set(CMAKE_JOB_POOL_LINK BCC32LinkPool)
Hmm. What if the user sets this too? Perhaps we should allow
users/projects to take control of this setting by making the
Hi.
I try to set a custom configurations like Debug-Demo and Release-Demo.
I had used a snippet from wiki:
http://www.cmake.org/Wiki/CMake_FAQ#How_can_I_specify_my_own_configurations_.28for_generators_that_allow_it.29_.3F
with additional modifying DEBUG_CONFIGURATIONS, because the Debug-Demo
See updated attached patch. I've retested it to ensure the VTK 5.4.2 build
I've been working with still builds correctly - and it still does.
Thank you for considering it.
-James
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
+set(CMAKE_JOB_POOL_LINK
Hi,
The attached patch is in regards to issue #15620 in mantis bug tracker
(Ninja generator triggers race condition in Borland bcc32 linker causing
intermittent build failure). Thanks to Brad King's suggestion, I think
using job pools is a lot easier than trying my proposed workaround (which I
Are you using Eclipse or Kate?
Did you do a grep -E \-j on all of the files included by the script
that drives the build? (And in your source tree?)
The only -j possibilities that look likely in CMake itself are shown
in the git grep results from a CMake checkout:
$ git grep -E \-j
I will have to admit that I don't pretend to completely understand the CMake
file that I am using as I started with something from VTK and changed things to
work with our project and setup. I will attach the files to the email. Maybe
you can see something that I am missing:
BuildDREAM3D.sh
On 06/18/2015 04:01 PM, Ette, Anthony (CDS) wrote:
rts1-4:/home/bzpl46/test2 cmake -G Unix Makefiles
-- The Fortran compiler identification is CCur
-- Check for working Fortran compiler: /usr/ccs/bin/cf77
-- Check for working Fortran compiler: /usr/ccs/bin/cf77 -- works
Great! Thanks for
Found the source. the generated CTestConfig.cmake is the following:
## This file should be placed in the root directory of your project.
## Then modify the CMakeLists.txt file in the root directory of your
## project to incorporate the testing dashboard.
## # The following are required to uses
CMake does not generate it.
You may have received it as a suggestion from CDash when you set the
project up, and then you put it in your top level source tree and
forget about it usually.
But I don't think CDash would suggest using -j with if(NOT WIN32)
logic (although I could be wrong)... so
Did you read through the pointed to stack overflow question and answers?
Is the information there misleading or incorrect?, ... because it
seems to say there is a way to do it with MSVC...
On Thu, Jun 18, 2015 at 3:16 PM, Robert Dailey rcdailey.li...@gmail.com wrote:
On Thu, Jun 18, 2015
And I will follow that up quickly with .. it was buried down in our project…..
Thanks for the help.
Mike J.
On Jun 18, 2015, at 3:45 PM, Michael Jackson mike.jack...@bluequartz.net
wrote:
Found the source. the generated CTestConfig.cmake is the following:
## This file should be placed
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 85615c055a275edbab3c8dfb53f563003ea21841 (commit)
via
On 06/18/2015 03:05 PM, James Johnston wrote:
See updated attached patch.
Thanks, applied:
Embarcadero: Run at most one linker invocation at a time
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=078b60f0
I moved most of the explanation from comments to the commit message
and left a
True it works; I was wrongly setting the file lock on the file I was trying to
write into. Thanks!
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent: Thursday, June 18, 2015 9:28 AM
To: Robert Goulet
Cc: cmake-developers@cmake.org
Subject: Re: [cmake-developers]
Hi,
On 18 June 2015 at 12:16, Robert Dailey rcdailey.li...@gmail.com wrote:
On Thu, Jun 18, 2015 at 12:02 PM, Dan Liew d...@su-root.co.uk wrote:
Can you explain what you mean by strong and weak symbols?
Google is your friend
https://en.wikipedia.org/wiki/Weak_symbol
The error shown in your CDash build error output page could be coming
from something that is built within your project as an
ExternalProject.
Do you have any of those?
Have you grepped your source tree for -j yet?
On Thu, Jun 18, 2015 at 3:17 PM, Michael Jackson
mike.jack...@bluequartz.net
Please try building CMake from commit 7cd539b1 to see if it detects the
compiler id as CCur. Once that works we can look at updating the flags
used for the compiler.
Looks like this patch (which includes the commit to remove -rdynamic from GNU
fortran compilers -
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 95423594649a7df0fe254c44379b48c32e0183f6 (commit)
via
On Thu, Jun 18, 2015 at 1:43 AM, Robert Dailey rcdailey.li...@gmail.com
wrote:
On Wed, Jun 17, 2015 at 4:31 PM, Dan Liew d...@su-root.co.uk wrote:
On 17 June 2015 at 12:28, Robert Dailey rcdailey.li...@gmail.com
wrote:
Is there a way to only take (recursively) the include directiories from
This is the approach that the LLVM project uses which is very simple
and very clean (take a look at the sources). This also works very well
for installing your header files, the contents of ${CMAKE_SOURCE_DIR}
just need to be copied into /usr/include .
Oops I meant to say the contents of
The reason I'm asking this question is because of how I handle unit
tests in CMake right now. Instead of just defining an executable
target for the test and then adding a link dependency on the library
containing the class or set of classes to be tested, I am manually
pulling in the CPP and H
Is there an alternative method for setting the CMAKE_TOOLCHAIN_FILE variable
other than, for example:
cmake -D CMAKE_TOOLCHAIN_FILE=... args
Perhaps an environment variable or something similar?
You always have the option to set an environment variable and then
read it at the top of your
Hello,
Is there an alternative method for setting the CMAKE_TOOLCHAIN_FILE variable
other than, for example:
cmake -D CMAKE_TOOLCHAIN_FILE=... args
Perhaps an environment variable or something similar?
Thanks,
Justin
--
Powered by www.kitware.com
Please keep messages on-topic and check
46 matches
Mail list logo
