Excellent job. I have littlie knowledge of how syntax highlight additions can
be implemented in VS, but what was the design idea behind using so few colors?
Other than this, it is very useful and will be installed on all my machines.
Cheers,
Máté
Feladó: David Golub
Elküldve: kedd,
Anatoly Shirokov wrote:
Guys!
I have fixed bug related to delete translation (ts) file during clean
(someone meet the same problem here
http://cmake.3232098.n2.nabble.com/How-to-not-delete-generated-files-on-make-clean-td4425991.html)
I agree with the point that Hendrik Sattler makes that
The translation file is usual source file, it is not binary artifact.
The only difference is that I have to support them in up to date state
with the lupdate utility. I want to invoke lupdate automatically during
build and after that commit updated translation files to use them by
translator
Anatoly Shirokov wrote:
The translation file is usual source file, it is not binary artifact.
I didn't say it was a binary artifact. It's a buildsystem artifact created
by your buildsystem.
The only difference is that I have to support them in up to date state
with the lupdate utility.
I'm trying to see if CMake would be right for a project I'm working on. We're
in need of a configuration tool but there are a few things that I'm not sure if
CMake can do for us.
1. The first deals with the GUI for configuration. I'm wanting a fully
nestable tree for the various sections.
I generally stuck with the same syntax highlighting color conventions used by
Visual Studio itself. Are there other language constructs that you feel would
benefit from getting a color?
David Golub
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Nagy-Egri Máté Ferenc
Sent:
Please see my comments below
27.02.2014 1:08, Stephen Kelly ?:
Anatoly Shirokov wrote:
The translation file is usual source file, it is not binary artifact.
I didn't say it was a binary artifact. It's a buildsystem artifact
created
by your buildsystem.
This is source which can be
Hi Anatoly,
Within Slicer [1], we addressed the creation / updates of the translation
files by introducing a variable named Slicer_UPDATE_TRANSLATION [2]
Then, within a macro named 'SlicerMacroTranslation.cmake' [3], depending on
the value of Slicer_UPDATE_TRANSLATION, we either call
(1)
Dear Jean-Christophe Fillion-Robin!
Thank you very much for your attention. But I do not have a problem with
CREATE. I have problem with UPDATE, actually with
QTx_CREATE_TRANSLATION. QTx_CREATE_TRANSLATION uses add_custom_command
which forces to delete the original updated SOURCE ts file
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14772
==
Reported By:Lars
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14773
==
Reported By:Derek Chow
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14774
==
Reported By:philrosenberg
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14775
==
Reported By:Nikolay Orliuk
Assigned To:
On 02/25/2014 04:17 PM, Matthäus G. Chajdas wrote:
thanks for splitting the patches the review. I've just pushed the
requested changes to the add-FindOpenCL topic.
Thanks. I made some minor tweaks and merged to 'next' for testing:
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=041485bc
Recent commits broke the version argument handling, as the set variable
name is different to the used variable name. First attached patch fixes
this. The second one clears the variable again at the end of the macro,
to match the other variables.
Alex
From
On 02/26/2014 10:09 AM, Alex Merry wrote:
Recent commits broke the version argument handling, as the set variable
name is different to the used variable name. First attached patch fixes
this. The second one clears the variable again at the end of the macro,
to match the other variables.
Oops; I just got it through my thick head that this is an LLVM patch! OK,
much more helpful than I thought, thanks.
On Wed, Feb 26, 2014 at 3:12 PM, Dave Abrahams d...@boostpro.com wrote:
Yes, thanks, Brad. I hope one day we'll be able to use those features,
but I was hoping someone could
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 2c2ddadbe0fdb2779ca0ece2fc92d66f3609e22a (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 f8eccc4f354cae5fc95f8575490f6efb269febf6 (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 4d137ee1fae3288f3a87baa19332fdaf7abcc56a (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 4f8deba4cfdb6055a60d124f1658a8a830d856e7 (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 ae4182b32b08f077b6b5ffc8c624c2c92c5d8e88 (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 f3ae507070694b61b9dd732110f3a93da51b5cfe (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 0736dad395f775be37055e61f2cb1fa3f8ec31cc (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 6223621e9a4bfc7bbf91037183c725c4300db397 (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 5cad466daefa64578d4e4ca0394db983ab40bba4 (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 041ba1eefde146a6eb239a9f837dd5e0ef7b3d84 (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 75428cdfb9685c7e58270cae1f487b51fa0cc351 (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 037124a532bea03d22ac519eb67a70da7cfc278b (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 14170273fe9df493fa3d0867d980889d6d08e089 (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 3a00cac030b7ffb93e1b89d81e4952f94a1b4830 (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 336cca152b3ffe685f4962a5efd8c8d4691848d6 (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 184447b6e04996a63abe9d71eb75908c14fdb137 (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 072d6061135cdacec16690d0a19cb42988354c04 (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 6391b32a32c27e136eb629f633893f9a69e98182 (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 948d5d18fd6deed24ede54cb0e3b017511f99559 (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 6e6fbb0e436889c93bb64930fda51a1ef32326ae (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 8d71c7efd29d606ad11078df7e7d74de4558955e (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 d0bf34f9b275f621f0b7db537aebeebce00b9494 (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 5745be7e2b813a81f0c4c36b2d6865dba26c8a56 (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 87aad47f293ccb7358e5e9e8cd854e9bd710d26f (commit)
via
20140226)
+set(CMake_VERSION_PATCH 20140227)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
42 matches
Mail list logo
