On 2011-08-28 14:34-0400 Bill Hoffman wrote:
Can you try and build CMake 2.8.4, then 2.8.3 and see what happens?
Given many hours of computer time (remember the severe latency issue), yes.
I will get to this eventually, but other projects and computer issues are
currently
delaying it.
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=12439
==
Reported By:freddie
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=12440
==
Reported By:Thomas Jarosch
Assigned To:
Hi all,
I recently changed jobs and have a different public key than the one currently
registered with Cmake Git. How do I go about updating my public key so I can
push a change to Cmake from my new machine?
Thanks,
Will
___
cmake-developers mailing
Use this form again, as when you first signed up, to submit your public key:
https://www.kitware.com/Admin/SendPassword.cgi
(You can leave the password field blank, or fill it with irrelevance,
since it's key-based access...)
I'll alert the people on the other end of that form that this
The following issue has been SUBMITTED.
==
http://www.itk.org/Bug/view.php?id=12441
==
Reported By:vastevaste
Assigned To:
I was just replying to an acquaintance who was e-mailing me about CMake
configuration when I realized that CMake configuration options
which are only available depending on how other configuration
options are set could be analyzed/displayed using graph theory
(from a 5-minute study of graph
On 9/1/2011 12:27 AM, Clifford Yapp wrote:
On Wed, Aug 31, 2011 at 2:14 PM, Bill Hoffmanbill.hoff...@kitware.com wrote:
It would make a mess if you created a sub-dir per test. There would be lots
and lots of sub-dirs in some projects.
Personally I would expect that, and be OK with it, as
Hi David,
I've updated the bug with a patch which adds a test to check that defining
_SBCS does set CharacterSet to 0 (Single Byte Character Set). I checked that
it works when _SBCS is set and fails when _SBCS is not defined.
I looked for where the _UNICODE option is documented, thinking to
That was intentional. .dll Should already be in CMAKE_FIND_LIBRARY_SUFFIXES on
WIN32.
Since your commits haven't hit git/gitweb yet I'm not sure what you didn't
commit.
As far as the ACML changes go, the file globbing is way too greedy, and breaks
if more than one ACML or ACML-GPU package is
On Sep 1, 2011, at 12:00 PM, Alexey Ozeritsky wrote:
On Thu, Sep 1, 2011 at 7:47 PM, don la dieu n...@icecube.umd.edu wrote:
That was intentional. .dll Should already be in CMAKE_FIND_LIBRARY_SUFFIXES
on WIN32.
Yes, it should already be in CMAKE_FIND_LIBRARY_SUFFIXES but not in
Sounds like a great research project for somebody. Would be cool to
see CMake options visualized for some larger projects...
Not sure of its feasibility in terms of completeness, however. I'm
sure you could come up with something rudimentary that seems to work
for some cases.
There are some
On 2011-09-01 18:00-0400 David Cole wrote:
Sounds like a great research project for somebody. Would be cool to
see CMake options visualized for some larger projects...
Not sure of its feasibility in terms of completeness, however. I'm
sure you could come up with something rudimentary that
On 9/1/2011 8:48 PM, Alan W. Irwin wrote:
Yeah, it is fun to speculate about something new like this that would
be of considerable benefit to help a project's developers and users
visualize the complete set of options and their dependencies for their
project's build system. Unfortunately I
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 90ee78a5c6a8203226f0a58352a03404765b6754 (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 c496437203ca868f9e65572e4b7af9119f8d9bca (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 2145e2ac47607e0922875fb287968bb14158baf4 (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 3e6e82e9d89d1062ece2f1ea1432246ff8410660 (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 59195aaf5870e87390e590774751f0af457d9173 (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 319df3245e774d807b993ff2fff3957e219ffe7b (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 925af96eda392cff31e57c832ab5ed17e0e3805f (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 97c11381d69efacf419da9d5d67f1885dde7e4d0 (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 5c51a7bdf3335663adf882938f3901cbde21da4e (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 a9c96a725ed4adabd7bb9eade1f67ff3cc0e99a4 (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 1aa42978a50417a0105270692dd46b31861cfff2 (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 7692baad47d8a4266b14e6c4a04171c3432f9b19 (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 83ce7c4d3cbc8b4277e815f861456ea6f7ec18e3 (commit)
from
27 matches
Mail list logo
