Re: [cmake-developers] [ANNOUNCE] CMake 3.4.0 Released

2015-11-12 Thread Jean-Michaël Celerier
> * The "CPackDeb" module now correctly excludes symlinks during
  package checksum calculation.

> * The "CPackDeb" no longer uses fakeroot and system tar program for
  packaging.

Does this mean that the ubuntu package manager will stop complaining of
CPack DEBs ?

Thanks for the great work :)

Jean-Michaël


On Thu, Nov 12, 2015 at 9:47 PM, Konstantin Podsvirov <
konstan...@podsvirov.pro> wrote:

> 12.11.2015, 21:57, "Robert Maynard" :
> > I am proud to announce that CMake 3.4.0 is now available for download at:
> > https://cmake.org/download/
> >
> > Documentation is available at:
> > https://cmake.org/cmake/help/v3.4
> >
> > Release notes appear below and are also published at
> > https://cmake.org/cmake/help/v3.4/release/3.4.html
>
> Good job! Thank you!
>
> I could not miss this event. This is a good occasion to remind about
> the existence of CPack "IFW" generator :-)
>
> https://cmake.org/cmake/help/v3.4/module/CPackIFW.html
>
> Here is a fresh not official offline installers for CMake 3.4.0 on Windows:
>
> http://ifw.podsvirov.pro/cmake/files/v3.4/cmake-3.4.0-win32-x86.exe
>
> and
>
> http://ifw.podsvirov.pro/cmake/files/v3.4/cmake-3.4.0-win64-x64.exe
>
> But I want to assure you that they are honestly built me personally of the
> official code of branch 'release' recently :-)
>
> I'll be glad if somebody test these installers for themselves and to share
> their comments and suggestions.
>
> Good luck to everyone!
>
> --
> Regards,
> Konstantin Podsvirov
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake-developers
>
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Re: [cmake-developers] [ANNOUNCE] CMake 3.4.0 Released

2015-11-12 Thread Konstantin Podsvirov
12.11.2015, 21:57, "Robert Maynard" :
> I am proud to announce that CMake 3.4.0 is now available for download at:
> https://cmake.org/download/
>
> Documentation is available at:
> https://cmake.org/cmake/help/v3.4
>
> Release notes appear below and are also published at
> https://cmake.org/cmake/help/v3.4/release/3.4.html

Good job! Thank you!

I could not miss this event. This is a good occasion to remind about
the existence of CPack "IFW" generator :-)

https://cmake.org/cmake/help/v3.4/module/CPackIFW.html

Here is a fresh not official offline installers for CMake 3.4.0 on Windows:

http://ifw.podsvirov.pro/cmake/files/v3.4/cmake-3.4.0-win32-x86.exe

and

http://ifw.podsvirov.pro/cmake/files/v3.4/cmake-3.4.0-win64-x64.exe

But I want to assure you that they are honestly built me personally of the 
official code of branch 'release' recently :-)

I'll be glad if somebody test these installers for themselves and to share 
their comments and suggestions.

Good luck to everyone!

--
Regards,
Konstantin Podsvirov
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


Re: [cmake-developers] [PATCH] iOS Framework Bundle support

2015-11-12 Thread Bartosz Kosiorek
Hello.

With this tiny little patch, the correct directory structure for iOS Frameworks 
is created.

The changes are backward compatible (it is not touching OS X at all, only iOS 
Frameworks).
The risk of regression is very low, as the change is for iOS frameworks, and 
officially CMake 3.4 do not support iOS.

I tested it manually by using scripts from previous mail for Xcode and Makefile 
generators, under iOS 9, and it fix directory structure.
After apply this patch, iOS Frameworks created by CMake are working perfectly 
for me.

Best Regards
Bartosz


From: cmake-developers  on behalf of 
Bartosz Kosiorek 
Sent: Wednesday, November 11, 2015 2:19 AM
To: Gregor Jasny; cmake-developers@cmake.org
Subject: Re: [cmake-developers] [PATCH] iOS Framework Bundle support

Hi

Generally I created this cmake scripts to to able to test creating iOS/OSX 
Application Bundle and iOS/OSX Dynamic Framework Bundle.
By default it produces iOS application Bundle and iOS Framework Bundle.

Steps to reproduce:
1. Download and install CMake 3.4.0
2. Unpack and unpack cmake_shared_ios_framework.zip
3. cd cmake_shared_ios_framework
4. mkdir build
5. cd build
6. ../../../cmake-3.4.0-rc3-Darwin-x86_64/CMake.app/Contents/bin/cmake ..
7. make

Expected result:
- Correct iOS Application Bundle in directory: addDemoCmake.app
- Correct iOS Dynamic Framework Bundle in directory: 
shared_empty/mul/mul.framework/

Current result:
- Correct iOS Application Bundle in directory: addDemoCmake.app
- Incorrect iOS Dynamic Framework Bundle in directory: 
shared_empty/mul/mul.framework/
It looks like:

find mul.framework/
mul.framework/
mul.framework//Headers
mul.framework//Headers/mul.h
mul.framework//Modules
mul.framework//Modules/module.modulemap
mul.framework//mul
mul.framework//Resources
mul.framework//Resources/Info.plist
mul.framework//Versions
mul.framework//Versions/Current

What it wrong in with that Framework :
1. Xcode expect that iOS Framework have Info.plist in main Framework directory 
(mul.framework/Info.plist).
2. mul.framework//Versions/ and mul.framework//Resources is not needed and 
shouldn't be produced (Info.plist should be moved to root Framework directory)
3. mul.framework//Versions/Current symlink is pointing to not existing "A" 
version directory

Now I see that my patch should be simplified to few lines. I will provide fix 
later.
My previous wrong assumption was that CMake 3.4 do not change anything in 
creating iOS Bundles.

@Gregor Do you think it will be possible to fix that issue in CMake 3.4.0, to 
have full support for iOS (both from Application and Frameworks) ?

Best Regards
Bartosz

From: Gregor Jasny 
Sent: Tuesday, November 10, 2015 9:54 PM
To: Bartosz Kosiorek; cmake-developers@cmake.org
Subject: Re: [cmake-developers] [PATCH] iOS Framework Bundle support

Hello,

On 10/11/15 16:22, Bartosz Kosiorek wrote:
> My name is Bartosz Kosiorek and I'm TomTom developer and Open Source 
> enthusiast.

I'm Gregor a part time contributor to CMake. During the last months I
mostly worked on Xcode support.

> Last time in our products, we notice that cmake is not creating correct iOS 
> Frameworks Bundle.
> For iOS Frameworks, not versioned Bundle is needed, eg.:
>
>   iOSFramework.framework/
>   iOSFramework
>   Info.plist
>   Headers
>
>
>
> Unfortunately with current version of CMake (3.4.0), it produces OS X 
> Framework Bundle, with versions inside, eg.:
>
>   MyFramework.framework/
> MyFramework -> Versions/Current/MyFramework
> Resources -> Versions/Current/Resources
> Versions/
> A/
> MyFramework
> Headers
> Resources/
>  Info.plist
> Current -> A
>
>
>
> You could test it with my example project in attachment 
> (cmake_shared_ios_framework.zip).

Unfortunately I cannot reproduce the problem. Could you please write
down the exact steps you took to compile the example in the zip file?
Please also Xcode and cmake version.

That's what I see (cmake master, Xcode generator and Xcode 7.1):

$ find _build/shared_empty/mul/Debug-iphonesimulator/mul.framework
_build/shared_empty/mul/Debug-iphonesimulator/mul.framework
_build/shared_empty/mul/Debug-iphonesimulator/mul.framework/Headers
_build/shared_empty/mul/Debug-iphonesimulator/mul.framework/Headers/mul.h
_build/shared_empty/mul/Debug-iphonesimulator/mul.framework/Info.plist
_build/shared_empty/mul/Debug-iphonesimulator/mul.framework/Modules
_build/shared_empty/mul/Debug-iphonesimulator/mul.framework/Modules/module.modulemap
_build/shared_empty/mul/Debug-iphonesimulator/mul.framework/mul

> The iOS Application Bundle was already fixed in CMake 3.4.0. Unfortunately 
> still iOS Frameworks are not produced correctly (Xcode refuses to sign such 
> Frameworks if you would like to push it into iOS device).
>
> In 

Re: [cmake-developers] [ANNOUNCE] CMake 3.4.0 Released

2015-11-12 Thread Konstantin Podsvirov
Meet the fresh update online installers (CMake3.4.20151113):

http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe

and

http://ifw.podsvirov.pro/cmake/cmake-master-win64-online.exe

If you have used them previously, then just update via "CMake Maintenance Tool".

12.11.2015, 23:55, "Konstantin Podsvirov" :
> 12.11.2015, 21:57, "Robert Maynard" :
>> I am proud to announce that CMake 3.4.0 is now available for download at:
>> https://cmake.org/download/
>>
>> Documentation is available at:
>> https://cmake.org/cmake/help/v3.4
>>
>> Release notes appear below and are also published at
>> https://cmake.org/cmake/help/v3.4/release/3.4.html
>
> Good job! Thank you!
>
> I could not miss this event. This is a good occasion to remind about
> the existence of CPack "IFW" generator :-)
>
> https://cmake.org/cmake/help/v3.4/module/CPackIFW.html
>
> Here is a fresh not official offline installers for 3.4.0 CMake on Windows:
>
> http://ifw.podsvirov.pro/cmake/files/v3.4/cmake-3.4.0-win32-x86.exe
>
> and
>
> http://ifw.podsvirov.pro/cmake/files/v3.4/cmake-3.4.0-win64-x64.exe
>
> But I want to assure you that they are honestly built me personally of the 
> official code of branch 'release' recently :-)
>
> I'll be glad if somebody test these installers for themselves and to share 
> their comments and suggestions.
>
> Good luck to everyone!

--
Regards,
Konstantin Podsvirov
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


[cmake-developers] [CMake 0015845]: CMake fails to identify the Cray compilers' version numbers

2015-11-12 Thread Mantis Bug Tracker

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=15845 
== 
Reported By:Damian Rouson
Assigned To:
== 
Project:CMake
Issue ID:   15845
Category:   (No Category)
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2015-11-12 09:51 EST
Last Modified:  2015-11-12 09:51 EST
== 
Summary:CMake fails to identify the Cray compilers' version
numbers
Description: 
As demonstrated below, CMake 3.0.1 fails to identify the version of the Cray C,
Fortran, and C++ compilers.  CMake 3.3.2 and CMake 3.4.0-rc3 exhibit the same
behavior.  This bug is also archived at
https://github.com/sourceryinstitute/AdHoc/tree/master/src/cmake.

Steps to Reproduce: 
> cat CMakeLists.txt 
project(cray_compiler_version_bug LANGUAGES Fortran C CXX)
if(
   "${CMAKE_Fortran_COMPILER_VERSION}" MATCHES "" AND 
   "${CMAKE_C_COMPILER_VERSION}"   MATCHES "" AND 
   "${CMAKE_CXX_COMPILER_VERSION}" MATCHES "" 
  )
  message(FATAL_ERROR 
"CMAKE_Fortran_COMPILER_VERSION, CMAKE_C_COMPILER_VERSION,
CMAKE_CXX_COMPILER_VERSION are all empty."
  )
endif()

> mkdir build && cd build

> FC=ftn cmake ..
-- The Fortran compiler identification is Cray
-- The C compiler identification is Cray
-- The CXX compiler identification is Cray
-- Check for working Fortran compiler: /opt/cray/craype/2.4.2/bin/ftn
-- Check for working Fortran compiler: /opt/cray/craype/2.4.2/bin/ftn  -- works
-- Detecting Fortran compiler ABI info
-- Detecting Fortran compiler ABI info - done
-- Checking whether /opt/cray/craype/2.4.2/bin/ftn supports Fortran 90
-- Checking whether /opt/cray/craype/2.4.2/bin/ftn supports Fortran 90 -- yes
-- Check for working C compiler: /opt/cray/craype/2.4.2/bin/cc
-- Check for working C compiler: /opt/cray/craype/2.4.2/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /opt/cray/craype/2.4.2/bin/CC
-- Check for working CXX compiler: /opt/cray/craype/2.4.2/bin/CC -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
CMake Error at CMakeLists.txt:7 (message):
  CMAKE_Fortran_COMPILER_VERSION, CMAKE_C_COMPILER_VERSION,
  CMAKE_CXX_COMPILER_VERSION are all empty.


-- Configuring incomplete, errors occurred!
See also
"/home/users/p01923/AdHoc/src/cmake/bug-x/build/CMakeFiles/CMakeOutput.log".
p01923@swan:~/AdHoc/src/cmake/bug-x/build> cmake --version
cmake version 3.0.1

CMake suite maintained and supported by Kitware (kitware.com/cmake).
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2015-11-12 09:51 Damian Rouson  New Issue
==

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


[cmake-developers] XCode Unit Test Bundle targets support

2015-11-12 Thread Robert Goulet
Hi all,

In XCode we can add a target of type "Test", specifically for us is the "iOS 
Unit Test Bundle" that is interesting, because with it we can write iOS test 
cases that will install, launch and close the app on the iOS device.

Does CMake has started to support any of this yet? And if no, what would be the 
preferable route to follow, since this seems to be XCode specific, but in the 
end we would probably need a command similar to add_library or add_executable, 
but that adds this type of target.

Thanks!

-Robert Goulet
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

[cmake-developers] [ANNOUNCE] CMake 3.4.0 Released

2015-11-12 Thread Robert Maynard
I am proud to announce that CMake 3.4.0 is now available for download at:
  https://cmake.org/download/

Documentation is available at:
  https://cmake.org/cmake/help/v3.4

Release notes appear below and are also published at
  https://cmake.org/cmake/help/v3.4/release/3.4.html

Some of the more significant features of CMake 3.4 are:

* The "if()" command learned a new "TEST" operator that evaluates to
  true if a given test name has been defined by the "add_test()"
  command.  See policy "CMP0064".

* The "install(DIRECTORY)" command "DESTINATION" option learned to
  support "generator expressions".

* The "install(FILES)" command "DESTINATION" option learned to
  support "generator expressions".

* CMake learned to honor "*.manifest" source files with MSVC tools.
  Manifest files named as sources of ".exe" and ".dll" targets will be
  merged with linker-generated manifests and embedded in the binary.


Deprecated and Removed Features:

* The "CMakeExpandImportedTargets" module is now documented as
  deprecated.  See module documentation for an explanation.

* The "CMAKE_USE_RELATIVE_PATHS" variable no longer has any effect.
  Previously it was partially implemented and unreliable.


CMake 3.4 Release Notes
***

Changes made since CMake 3.3 include the following.


New Features



Generators
--

* The "Visual Studio 14 2015" generator learned to select a Windows
  10 SDK based on the value of the "CMAKE_SYSTEM_VERSION" variable and
  the SDKs available on the host.

* CMake learned rudimentary support for the Apple Swift language.
  When using the "Xcode" generator with Xcode 6.1 or higher, one may
  enable the "Swift" language with the "enable_language()" command or
  the "project()" command (this is an error with other generators or
  when Xcode is too old).  Then one may list ".swift" source files in
  targets for compilation.


Commands


* The "find_program()" command learned a "NAMES_PER_DIR" option to
  consider all given "NAMES" in each directory before moving on to the
  next directory.

* The "get_filename_component()" command learned a new "BASE_DIR"
  subcommand.  This is used to specify a base directory when
  calculating an absolute path from a relative path.

* The "if()" command learned a new "TEST" operator that evaluates to
  true if a given test name has been defined by the "add_test()"
  command.  See policy "CMP0064".

* The "install(DIRECTORY)" command "DESTINATION" option learned to
  support "generator expressions".

* The "install(FILES)" command "DESTINATION" option learned to
  support "generator expressions".

* The "string()" command learned a new "APPEND" subcommand.


Variables
-

* The Makefile Generators and the "Ninja" generator learned to add
  compiler launcher tools like distcc and ccache along with the
  compiler for "C" and "CXX" languages.  See the
  "CMAKE__COMPILER_LAUNCHER" variable and
  "_COMPILER_LAUNCHER" target property for details.

* New "CMAKE_LINK_SEARCH_START_STATIC" and
  "CMAKE_LINK_SEARCH_END_STATIC" variables were introduced to
  initialize the "LINK_SEARCH_START_STATIC" and
  "LINK_SEARCH_END_STATIC" target properties, respectively.


Properties
--

* Visual Studio Generators learned to support additonal target
  properties to customize projects for NVIDIA Nsight Tegra Visual
  Studio Edition:

  * "ANDROID_ANT_ADDITIONAL_OPTIONS"

  * "ANDROID_ARCH"

  * "ANDROID_ASSETS_DIRECTORIES"

  * "ANDROID_JAR_DEPENDENCIES"

  * "ANDROID_JAR_DIRECTORIES"

  * "ANDROID_JAVA_SOURCE_DIR"

  * "ANDROID_NATIVE_LIB_DEPENDENCIES"

  * "ANDROID_NATIVE_LIB_DIRECTORIES"

  * "ANDROID_PROCESS_MAX"

  * "ANDROID_PROGUARD"

  * "ANDROID_PROGUARD_CONFIG_PATH"

  * "ANDROID_SECURE_PROPS_PATH"

  * "ANDROID_SKIP_ANT_STEP"

  * "ANDROID_STL_TYPE"

* The "ARCHIVE_OUTPUT_DIRECTORY", "LIBRARY_OUTPUT_DIRECTORY", and
  "RUNTIME_OUTPUT_DIRECTORY" target properties learned to support
  "generator expressions".

* The "SOURCE_DIR" and "BINARY_DIR" target properties were
  introduced to allow project code to query where a target is defined.

* The "OUTPUT_NAME" target property and its variants learned to
  support "generator expressions".

* A "TARGET_MESSAGES" global property was added to tell the Makefile
  Generators whether to generate commands to print output after each
  target is completed.

* On Windows with MS-compatible tools, CMake learned to optionally
  generate a module definition (".def") file for "SHARED" libraries.
  See the "WINDOWS_EXPORT_ALL_SYMBOLS" target property.


Modules
---

* The "ExternalProject" module "ExternalProject_Add()" function
  "GIT_SUBMODULES" option now also limits the set of submodules that
  are initialized in addition to the prior behavior of limiting the
  set of submodules that are updated.

* The "ExternalProject" module learned new "USES_TERMINAL" arguments
  for giving steps exclusive terminal access.  This is useful with the
  "Ninja" generator to monitor CMake