Re: [cmake-developers] [OSX CMake.dmg] Replace >10.6 build with 64-bit only and use bzip2 compression

2014-09-24 Thread Robert Maynard
Okay I have just merged into next a topic that switches over the official release to be built with UDBZ. Once the dashboards are happy I will update the x86_64 release to not be universal binaries. On Wed, Sep 24, 2014 at 10:15 AM, Brad King wrote: > On 09/24/2014 10:07 AM, Robert Maynard wrote:

Re: [cmake-developers] [OSX CMake.dmg] Replace >10.6 build with 64-bit only and use bzip2 compression

2014-09-24 Thread Brad King
On 09/24/2014 10:07 AM, Robert Maynard wrote: > I believe that the reason for both of these behaviors is that the > DragNDrop generator was written when a significant number of < 10.6 > machines existed in the wild. > > I don't see any reason why we shouldn't update the default for > CPACK_DMG_FOR

Re: [cmake-developers] [OSX CMake.dmg] Replace >10.6 build with 64-bit only and use bzip2 compression

2014-09-24 Thread Robert Maynard
I believe that the reason for both of these behaviors is that the DragNDrop generator was written when a significant number of < 10.6 machines existed in the wild. I don't see any reason why we shouldn't update the default for CPACK_DMG_FORMAT to be UDBZ instead of UDZO On Wed, Sep 24, 2014 at 8:

[cmake-developers] [OSX CMake.dmg] Replace >10.6 build with 64-bit only and use bzip2 compression

2014-09-24 Thread Adam Strzelecki
Not an big issue but official DMG bundles are 40 MB where my manually built one is 21 MB (half of it). So any reason for: * providing universal FAT binaries instead of 64-bit only for >=10.6 Darwin64 build, as anyway there is 32-bit build for these who have 32-bit only CPU? * using DMG zlib comp