On 06-Oct-14 16:54, Brad King wrote:
On 10/05/2014 04:59 PM, Ruslan Baratov via cmake-developers wrote:
So it can't be resolved without some low-level management. I'm thinking
about `file` command sub-option like LOCK_DIRECTORY:
`file(LOCK_DIRECTORY /path/to/shared-dir)`. Does it sounds doable?
Hello dear developers!
03.10.2014, 16:28, Brad King brad.k...@kitware.com:
Hi Folks,
In preparation for the first 3.1 release candidate I will feature-
freeze master as of 2014-10-09. As of now there are several open
topics in 'next' that we should try to land in master by then, but
please
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15198
==
Reported By:Helfer Thomas
Assigned To:
On 10/07/2014 02:49 AM, Ruslan Baratov wrote:
How it will looks like in terms of CMake code?
That's what I'm asking you to think through and propose ;)
Thanks,
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
On 10/07/2014 12:34 AM, clin...@elemtech.com wrote:
I don't have a 10.5 machine
Oops, I must have mixed up my browser tabs on that one.
but I've put in a commit which I hope solves the problem.
36c509b9 OSX: Only enable @rpath support on OS X 10.6 or greater.
Thanks!
-Brad
--
Powered by
On 10/07/2014 03:22 AM, Amine Khaldi wrote:
Please note that from the http://www.cmake.org/Bug/view.php?id=14972
fixes on, we can no longer compile ReactOS.
Thanks for trying the development version and reporting this regression
before it was released.
We have many DEPENDS on files that exist
On 10/7/2014 8:47 AM, Brad King wrote:
Please note that from thehttp://www.cmake.org/Bug/view.php?id=14972
fixes on, we can no longer compile ReactOS.
Also, if you really care about ReactOS, you could run a nightly cmake
dashboard. Or it is almost certain that it will get broken again. If
On 10/07/2014 04:09 PM, Bill Hoffman wrote:
On 10/7/2014 8:47 AM, Brad King wrote:
Please note that from thehttp://www.cmake.org/Bug/view.php?id=14972
fixes on, we can no longer compile ReactOS.
Also, if you really care about ReactOS, you could run a nightly cmake
dashboard. Or it is almost
Eike,
This fails on a few dashboard machines:
http://open.cdash.org/testDetails.php?test=286158250build=3519076
CMake Error at /.../Modules/FindThreads.cmake:207 (add_library):
add_library cannot create imported target CMake::Threads because another
target with the same name already
To clarify as far as I understand it this particular issue is with building
ReactOS on regular Windows rather than using CMake under ReactOS.
Which of course doesn't mean that there shouldn't be a dashboard for it
nonetheless :)
Yup, this is what I understand. It isn't a problem with
On 10/03/2014 08:27 AM, Brad King wrote:
In preparation for the first 3.1 release candidate I will feature-
freeze master as of 2014-10-09. As of now there are several open
topics in 'next' that we should try to land in master by then, but
please refrain from adding non-trivial changes in the
As a result of this, it's no longer possible to use the new CMake to compile
ReactOS, which makes us see this as a severe regression, considering that
CMake is the build system we use to compile the project.
Adam, Brad and co, can you please help ?
If I understand correctly the change
On 10/07/2014 04:56 PM, Adam Strzelecki wrote:
(1) Are these .spec, .inf or .idl generated by some custom commands?
(2) If yes, are these files specified as an output of these subcommand
commands? If no, why?
From what I remember from the IRC discussion ...
They are regular (not generated)
On 10/7/2014 10:42 AM, Adam Strzelecki wrote:
Which of course doesn't mean that there shouldn't be a dashboard for it
nonetheless:)
Yup, this is what I understand. It isn't a problem with compiling CMake on
ReactOS, but problem of compiling ReactOS with latest CMake master.
I'll follow the
Am Dienstag, 7. Oktober 2014, 10:35:24 schrieb Brad King:
Eike,
This fails on a few dashboard machines:
http://open.cdash.org/testDetails.php?test=286158250build=3519076
CMake Error at /.../Modules/FindThreads.cmake:207 (add_library):
add_library cannot create imported target
On 10/06/2014 04:04 PM, Rolf Eike Beer wrote:
Topic FPHSA_exact_version pushed to next.
Thanks. The impl looks okay to me. Please look at extending
the FindPackageTest with a case to cover this. It already has
at least one case for FPHSA. Alternatively you could add cases
to
From what I remember from the IRC discussion ...
They are regular (not generated) source files that are listed as dependencies
(but not outputs) of custom commands.
Okay now I get it. So actually 7243c951 (Ninja: Don't limit custom cmd
side-effects to build folder (#14972)) is to blame not
On 10/07/2014 02:21 PM, Adam Strzelecki wrote:
So please either provide test case, or some info
[snip]
On 10/07/2014 03:20 PM, Adam Strzelecki wrote:
I had a talk with Amine, and the problem was that due 7243c951
their build.ninja was getting numerous extra phony entries that
were leading
This will not be done before the freeze for 3.1 on Thursday.
Reverting 7243c951 will resolve the problem for ReactOS in
out-of-source builds. So, we either revert that or hope Ninja can
be fixed to deal with the large dependency lists w/out crashing.
In meantime I've pushed
Hi Bill:
In a recent thread on list you brought up the topic of contract
testing
https://github.com/Kitware/CMake/tree/master/Tests/Contracts where
apparently the idea is CMake is tested by building some git version of
CMake than building some fixed version of another project against that
I thought it would be interesting to install my own local dart server
to learn how to use CTest as a dart client. However, the dart server
software development effort seems to have a largely broken web
presence. For example, http://www.cmake.org/dart/HTML/Install.shtml
points to a Dart.pdf
Consider using CDash instead. It was Dart's drop-in replacement...
and is actively maintained today.
www.cdash.org
On Tue, Oct 7, 2014 at 6:46 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
I thought it would be interesting to install my own local dart server
to learn how to use CTest as
On 2014-10-07 19:06-0400 David Cole wrote:
Consider using CDash instead. It was Dart's drop-in replacement...
and is actively maintained today.
www.cdash.org
Thanks, Dave, for that information.
In reviewing why I wasted my time looking at the moribund dart rather
than cdash, dart clients
On Tue, Oct 7, 2014 at 9:23 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
On 2014-10-07 19:06-0400 David Cole wrote:
Consider using CDash instead. It was Dart's drop-in replacement...
and is actively maintained today.
www.cdash.org
Thanks, Dave, for that information.
In reviewing
On 10/7/2014 4:59 PM, Alan W. Irwin wrote:
Of course, once I got such a contract test to work by hand, I would
probably want to move to a formal automated procedure so your advice
on that would be appreciated as well.
The idea is to test next CMake against a version of the contract
project that
On 10/08/2014 12:46 AM, Alan W. Irwin wrote:
I thought it would be interesting to install my own local dart server
to learn how to use CTest as a dart client.
You probably want the newer Kitware maintained replacement CDash:
http://www.cdash.org/
Additional instructions for a local
26 matches
Mail list logo
