Re: [CMake] CMake 2.8.2-rc2 ready for testing!

2010-06-16 Thread Alok Govil
> Date: Wed, 16 Jun 2010 19:32:32 -0700 > From: ir...@beluga.phys.uvic.ca > To: alokgo...@hotmail.com > CC: david.c...@kitware.com; cmake@cmake.org > Subject: Re: [CMake] CMake 2.8.2-rc2 ready for testing! > > On 2010-06-16 19:04-0700 Alok Govil wrote: > > &

Re: [CMake] CMake 2.8.2-rc2 ready for testing!

2010-06-16 Thread Alan W. Irwin
On 2010-06-16 19:04-0700 Alok Govil wrote: Hi all, I am unable to build using MinGW-W64, but chances are there would be some configuration issues. Here is how I am setup right now: 1.  Download latest "automatic" builds (W64 and W32) from here:  http://mingw-w64.sourceforge.net/ 2.  Removed p

Re: [CMake] CMake 2.8.2-rc2 ready for testing!

2010-06-16 Thread Alok Govil
d, 16 Jun 2010 22:18:34 -0400 Subject: Re: [CMake] CMake 2.8.2-rc2 ready for testing! From: david.c...@kitware.com To: alokgo...@hotmail.com CC: cmake@cmake.org On Wed, Jun 16, 2010 at 10:04 PM, Alok Govil wrote: Hi all, I am unable to build using MinGW-W64, but chances are there would be

Re: [CMake] CMake 2.8.2-rc2 ready for testing!

2010-06-16 Thread David Cole
with the Personal/Sezero builds, do you see a difference as compared to CMake 2.8.0 or 2.8.1 with the same Personal/Sezero builds? If this is a mingw-w64 issue, perhaps you could raise it on their mailing lists? Thanks, David Cole > Best regards - Alok > > ----

Re: [CMake] CMake 2.8.2-rc2 ready for testing!

2010-06-16 Thread Alok Govil
4 5. "mingw32-make" is present in both W32 and W64 builds. Best regards - Alok --- > Date: Wed, 16 Jun 2010 16:22:43 -0400 > From: david.c...@kitware.com > To: cmake@cmake.org > Subject: [CMake] CMake 2.8.2-rc2 ready for testing! > > The CMake 2.8.2 releas

[CMake] CMake 2.8.2-rc2 ready for testing!

2010-06-16 Thread David Cole
The CMake 2.8.2 release candidate stream continues! You can find the source and binaries here: http://www.cmake.org/files/v2.8/. Since we switched to git, and a new workflow, we're expecting to do more frequent releases. Because of that, our release candidate phases will be shorter than they have