2010/10/27 Alexander Neundorf neund...@kde.org:
On Wednesday 27 October 2010, David Cole wrote:
Yes, the rc3 was announced last week.
Are you sure ?
I can't find it in my emails, also neither here:
http://public.kitware.com/pipermail/cmake-developers/2010-October/date.html
nor here:
Re-sending as plain text; the first time around, it got redirected to
the universe's bit bucket...
On Wed, Oct 20, 2010 at 6:04 PM, David Cole david.c...@kitware.com wrote:
The CMake 2.8.3 release candidate stream continues!
You can find the source and binaries here:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Message-ID:
b870629719727b4ba82a6c06a31c29123119bf1...@hqmailsvr01.voltage.com
Hi Phil.
Sono ideas nowhere nohow?
Well, I did have one idea. A wild stab in the dark, probably nothing
whatsoever to do with your issue. Apologies in advance for
Hi all,
What is the best way to work around a broken Find module?
A technique I've used up till now is to wrap the broken module in a
module with the same name that I store in my own module directory. This
way, my wrapper module will be picked up first. Problem with this
approach is, of course,
Re-sending as plain text; the first time around, it got redirected to
the universe's bit bucket...
On Wed, Oct 20, 2010 at 6:04 PM, David Cole david.c...@kitware.com wrote:
The CMake 2.8.3 release candidate stream continues!
You can find the source and binaries here:
If you look at my repository, I have a system set up that I call
UseBackportedModules - basically it checks the CMake version and
extends the CMAKE_MODULE_PATH to include only those directories
mentioning newer version than the current user's cmake version. It
works pretty well for me.
cmake -DCMAKE_TOOLCHAIN_FILE:string=%~dp0\zosport.cmake -GUnix
Makefiles .\
You are building on Windows, yes? Whenever I try to use .\ in a
command prompt, batch file or command file on Windows, it does horrible
things. I have to substitute a full or partial path. Could this be the
issue?
On Wed, 2010-10-27 at 10:54 -0500, Ryan Pavlik wrote:
On Wed, Oct 27, 2010 at 9:04 AM, Rolf Eike Beer e...@sf-mail.de wrote:
Thanks. The way I understand this is that now instead of
include_directories(${GTKMM_INCLUDE_DIRS})
i would write something like
--- Mer 27/10/10, Alan W. Irwin ha scritto:
On 2010-10-26 17:53-0400 Bill Hoffman
wrote:
The policy mechanism might not be ideal but in a year
or so, all of this would go away, and the meantime the
patches you have to maintain for cygwin ports would become
trivial. The patch would
On Thu, Oct 28, 2010 at 8:23 AM, Dominik Gabi dkgis...@gmail.com wrote:
On Wed, 2010-10-27 at 10:54 -0500, Ryan Pavlik wrote:
On Wed, Oct 27, 2010 at 9:04 AM, Rolf Eike Beer e...@sf-mail.de wrote:
Thanks. The way I understand this is that now instead of
On Thu, Oct 28, 2010 at 8:29 AM, John Drescher dresche...@gmail.com wrote:
On Thu, Oct 28, 2010 at 8:23 AM, Dominik Gabi dkgis...@gmail.com wrote:
On Wed, 2010-10-27 at 10:54 -0500, Ryan Pavlik wrote:
On Wed, Oct 27, 2010 at 9:04 AM, Rolf Eike Beer e...@sf-mail.de wrote:
Thanks. The way I
--- Mer 27/10/10, Marcus D. Hanwell ha scritto:
On Wed, Oct 27, 2010 at 2:38 PM, Alan
W. Irwin
wrote:
On 2010-10-26 17:53-0400 Bill Hoffman wrote:
The policy mechanism might not be ideal but in a
year or so, all of this
would go away, and the meantime the patches you
have to
On Thu, Oct 28, 2010 at 8:45 AM, Marco Atzeri marco_atz...@yahoo.it wrote:
--- Mer 27/10/10, Marcus D. Hanwell ha scritto:
On Wed, Oct 27, 2010 at 2:38 PM, Alan
W. Irwin
wrote:
On 2010-10-26 17:53-0400 Bill Hoffman wrote:
The policy mechanism might not be ideal but in a
year or so,
--- Gio 28/10/10, Marcus D. Hanwell ha scritto:
It seems that the policy based approach would have allowed
you a one
line patch to most packages (changing the policy to NEW).
I guess so. I can work with a one single line patch.
Marcus
Marco
I've seen this a few times in the past, and I've seen a few people try to
get it to work. My advise is to not try. The problem comes from thinking
that a template class is a class, but that is not true. Your template
class is just a recipe for the compiler to use when it wants to make a
class
Please tell me someone else encountered this and it's fixed. I'm going
to have to make a patched version of ExternalProject.cmake a part of
my project until it is.
In CMake 2.8.2 ExternalProject.cmake, there is no consistency on the
capitalization of the Git_EXECUTABLE variable -- which is what
Hi Kent,
The version of FindGit.cmake and ExternalProject.cmake provided with cmake
2.8.2 uses GIT_EXECUTABLE.
Within ExternalProject.cmake:
- The lower case version of the variable is used as a parameter to
function. For example, function _ep_write_gitclone_script line 212.
- The upper
On 10/28/2010 03:47 AM, David Cole wrote:
Sorry about this folks. Apparently, the email I sent had too much
information for the CMake mailing list, exceeding the 40k limit for a single
message.
CMake 2.8.3-rc3 has been available since last week, and we are nearly ready to
cut the final release
On Thu, 2010-10-28 at 09:39 -0400, Marcus D. Hanwell wrote:
It seems that the policy based approach would have allowed you a one
line patch to most packages (changing the policy to NEW).
Look at this from the POV of a packager: even a one-line patch adds up
quickly when you talk about hundreds
On Thu, Oct 28, 2010 at 12:49:16PM -0500, Yaakov (Cygwin/X) wrote:
We see the defining of WIN32 on Cygwin as a *bug*, not a feature, and it
needs to be fixed outright.
I think the crux of the dilemma is this: what do you say to the people
who rely on this buggy behavior for their packages to
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 b57c4889b4561784f10a24065995614cb2f2c164 (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 424ba550e5b06c68df753ef7a190c0308b31b1b7 (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 5b43d8f8b1cfd3e3acf1576b5bf2f910fb3c50db (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 ec93cd2ead86ea068577105a1903f92d604b6912 (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 a3edde36ad870d669c054701bccf6c1d14d2d72c (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 e561a46c1a852516dcbb1d435a4b8c6f95f636c3 (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 9bf662a92a8d0b6a215bc81cdbf61284f2d67694 (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 b32b3181173681ff0ce041b527638e9d08cbeda6 (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 63529b1c6d7eb82b662a8fe672585c7339d12930 (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 57eea54720a378712735b5ec6386cef745855325 (commit)
from
30 matches
Mail list logo
