[Cmake-commits] CMake branch, master, updated. v3.5.1-329-g60de9b8

2016-03-28 Thread Kitware Robot 
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  60de9b8a4fe6ceb99682ef7e63e73a592506d158 (commit)
  from  d29004756fa314119a91821a14eef81a2ffcf40a (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=60de9b8a4fe6ceb99682ef7e63e73a592506d158
commit 60de9b8a4fe6ceb99682ef7e63e73a592506d158
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Tue Mar 29 00:01:05 2016 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Tue Mar 29 00:01:05 2016 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index ea1b7ac..6235b66 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,5 +1,5 @@
 # CMake version number components.
 set(CMake_VERSION_MAJOR 3)
 set(CMake_VERSION_MINOR 5)
-set(CMake_VERSION_PATCH 20160328)
+set(CMake_VERSION_PATCH 20160329)
 #set(CMake_VERSION_RC 1)

---

Summary of changes:
 Source/CMakeVersion.cmake |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-03-28 Thread Nikolaus Demmel 
Hi Stephen,

> On 03/25/2016 09:25 AM, Tobias Hunger wrote:
>> I am personally rather unsure about how to proceed. I can help make
>> this branch production/merge ready, but I do not want to maintain it
>> indefinitely after it is merged. It touches to many CMake internals
>> for me to be comfortable hacking on that code. 
> 
> Yes, this lack of interest in general in maintaining it upstream is
> currently a demotivator. I think we need a group of people interested in
> doing that.
> 
> Brad/Ben, no response since I posted the blog or the code. Any word of
> interest in any of it?

I just wanted to let you know that I think these additions have huge potential. 
Too much time is spent debugging cmake with `message(…)`. 

Unfortunately I currently do not have any capacity to join the effort, sorry. 
So all I can say is, keep it up! If you can get this to a useable state 
(hopefully with the help of others), it will be very useful indeed.

Cheers,
Nikolaus
-- 

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-commits] CMake branch, next, updated. v3.5.1-673-gae8dbb9

2016-03-28 Thread Domen Vrankar 
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  ae8dbb9d619d83104c5afa9029b084064ae8c566 (commit)
   via  1fe004eac3c5b905cb620580c3258ca3bd455c18 (commit)
  from  2d932b45dc63e8fb0f43fdcb9f69a6d020e553da (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ae8dbb9d619d83104c5afa9029b084064ae8c566
commit ae8dbb9d619d83104c5afa9029b084064ae8c566
Merge: 2d932b4 1fe004e
Author: Domen Vrankar 
AuthorDate: Mon Mar 28 18:52:25 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Mar 28 18:52:25 2016 -0400

Merge topic 'cpack-rpm-default-user-and-group' into next

1fe004ea cpack rpm setting of defattr


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1fe004eac3c5b905cb620580c3258ca3bd455c18
commit 1fe004eac3c5b905cb620580c3258ca3bd455c18
Author: Domen Vrankar 
AuthorDate: Tue Mar 29 00:51:18 2016 +0200
Commit: Domen Vrankar 
CommitDate: Tue Mar 29 00:51:18 2016 +0200

cpack rpm setting of defattr

RPM supports setting of default user, group,
file and directory permissions that will be
applied for files in package unless specified
per file/dir with attr setting
This is related to bug report 14714

diff --git a/Help/release/dev/cpack-rpm-default-user-and-group.rst 
b/Help/release/dev/cpack-rpm-default-user-and-group.rst
new file mode 100644
index 000..7667c7f
--- /dev/null
+++ b/Help/release/dev/cpack-rpm-default-user-and-group.rst
@@ -0,0 +1,9 @@
+cpack-rpm-default-user-and-group
+
+
+* The "CPackRPM" module learned how to set default values for owning user/group
+  and file/directory permissions of package content.
+  See :variable:`CPACK_RPM_DEFAULT_USER`, :variable:`CPACK_RPM_DEFAULT_GROUP`,
+  :variable:`CPACK_RPM_DEFAULT_FILE_PERMISSIONS`,
+  :variable:`CPACK_RPM_DEFAULT_DIR_PERMISSIONS` and their per component
+  counterparts.
diff --git a/Modules/CPackRPM.cmake b/Modules/CPackRPM.cmake
index 7ffec13..ae51dc1 100644
--- a/Modules/CPackRPM.cmake
+++ b/Modules/CPackRPM.cmake
@@ -531,6 +531,54 @@
 #  - /usr/share/doc/.*/man/man.*
 #  - /usr/lib/.*/man/man.*
 #
+# .. variable:: CPACK_RPM_DEFAULT_USER
+#   CPACK_RPM__DEFAULT_USER
+#
+#  default user ownership of RPM content
+#
+#  * Mandatory : NO
+#  * Default   : root
+#
+#  Value should be user name and not UID.
+#  Note that  must be in upper-case.
+#
+# .. variable:: CPACK_RPM_DEFAULT_GROUP
+#   CPACK_RPM__DEFAULT_GROUP
+#
+#  default group ownership of RPM content
+#
+#  * Mandatory : NO
+#  * Default   : root
+#
+#  Value should be group name and not GID.
+#  Note that  must be in upper-case.
+#
+# .. variable:: CPACK_RPM_DEFAULT_FILE_PERMISSIONS
+#   CPACK_RPM__DEFAULT_FILE_PERMISSIONS
+#
+#  default permissions used for packaged files
+#
+#  * Mandatory : NO
+#  * Default   : - (system default)
+#
+#  Accepted values are lists with PERMISSIONS. Valid permissions
+#  are OWNER_READ, OWNER_WRITE, OWNER_EXECUTE, GROUP_READ,
+#  GROUP_WRITE, GROUP_EXECUTE, WORLD_READ, WORLD_WRITE and WORLD_EXECUTE.
+#  Note that  must be in upper-case.
+#
+# .. variable:: CPACK_RPM_DEFAULT_DIR_PERMISSIONS
+#   CPACK_RPM__DEFAULT_DIR_PERMISSIONS
+#
+#  default permissions used for packaged directories
+#
+#  * Mandatory : NO
+#  * Default   : - (system default)
+#
+#  Accepted values are lists with PERMISSIONS. Valid permissions
+#  are OWNER_READ, OWNER_WRITE, OWNER_EXECUTE, GROUP_READ,
+#  GROUP_WRITE, GROUP_EXECUTE, WORLD_READ, WORLD_WRITE and WORLD_EXECUTE.
+#  Note that  must be in upper-case.
+#
 # Packaging of Symbolic Links
 # ^^^
 #
@@ -581,6 +629,35 @@
 
 # Author: Eric Noulard with the help of Alexander Neundorf.
 
+function(get_unix_permissions_octal_notation PERMISSIONS_VAR RETURN_VAR)
+  set(PERMISSIONS ${${PERMISSIONS_VAR}})
+  list(LENGTH PERMISSIONS PERM_LEN_PRE)
+  list(REMOVE_DUPLICATES PERMISSIONS)
+  list(LENGTH PERMISSIONS PERM_LEN_POST)
+
+  if(NOT ${PERM_LEN_PRE} EQUAL ${PERM_LEN_POST})
+message(FATAL_ERROR "${PERMISSIONS_VAR} contains duplicate values.")
+  endif()
+
+  foreach(PERMISSION_TYPE "OWNER" "GROUP" "WORLD")
+set(${PERMISSION_TYPE}_PERMISSIONS 0)
+
+foreach(PERMISSION ${PERMISSIONS})
+  if("${PERMISSION}" STREQUAL "${PERMISSION_TYPE}_READ")
+math(EXPR ${PERMISSION_TYPE}_PERMISSIONS 
"${${PERMISSION_TYPE}_PERMISSIONS} + 4")
+  elseif("${PERMISSION}" STREQUAL "${PERMISSION_TYPE}_WRITE")
+math(EXPR ${PERMISSION_TYPE}_PERMISSIONS

[Cmake-commits] CMake branch, next, updated. v3.5.1-671-g2d932b4

2016-03-28 Thread Gregor Jasny via Cmake-commits 
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  2d932b45dc63e8fb0f43fdcb9f69a6d020e553da (commit)
   via  ed8979540f1f0549bb7ab5432a1a35e46790ba76 (commit)
  from  0f364a2b1b134ce79fe62093f959d0d79657a96c (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2d932b45dc63e8fb0f43fdcb9f69a6d020e553da
commit 2d932b45dc63e8fb0f43fdcb9f69a6d020e553da
Merge: 0f364a2 ed89795
Author: Gregor Jasny 
AuthorDate: Mon Mar 28 16:35:33 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Mar 28 16:35:33 2016 -0400

Merge topic 'asm-includes' into next

ed897954 Add missing  placeholder for ASM languages


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ed8979540f1f0549bb7ab5432a1a35e46790ba76
commit ed8979540f1f0549bb7ab5432a1a35e46790ba76
Author: Gregor Jasny 
AuthorDate: Fri Mar 25 23:18:07 2016 +0100
Commit: Gregor Jasny 
CommitDate: Fri Mar 25 23:18:07 2016 +0100

Add missing  placeholder for ASM languages

Signed-off-by: Gregor Jasny 

diff --git a/Modules/CMakeASM-ATTInformation.cmake 
b/Modules/CMakeASM-ATTInformation.cmake
index 675c13b..07a2d38 100644
--- a/Modules/CMakeASM-ATTInformation.cmake
+++ b/Modules/CMakeASM-ATTInformation.cmake
@@ -19,7 +19,7 @@ set(ASM_DIALECT "-ATT")
 # assembler but should be processed by gcc
 set(CMAKE_ASM${ASM_DIALECT}_SOURCE_FILE_EXTENSIONS s;asm)
 
-set(CMAKE_ASM${ASM_DIALECT}_COMPILE_OBJECT " 
 -o  ")
+set(CMAKE_ASM${ASM_DIALECT}_COMPILE_OBJECT " 
  -o  ")
 
 include(CMakeASMInformation)
 set(ASM_DIALECT)
diff --git a/Modules/CMakeASM_NASMInformation.cmake 
b/Modules/CMakeASM_NASMInformation.cmake
index 7058fc7..146f412 100644
--- a/Modules/CMakeASM_NASMInformation.cmake
+++ b/Modules/CMakeASM_NASMInformation.cmake
@@ -38,7 +38,7 @@ if(NOT CMAKE_ASM_NASM_OBJECT_FORMAT)
   endif()
 endif()
 
-set(CMAKE_ASM_NASM_COMPILE_OBJECT "  -f 
${CMAKE_ASM_NASM_OBJECT_FORMAT} -o  ")
+set(CMAKE_ASM_NASM_COMPILE_OBJECT "  
 -f ${CMAKE_ASM_NASM_OBJECT_FORMAT} -o  ")
 
 # Load the generic ASMInformation file:
 set(ASM_DIALECT "_NASM")
diff --git a/Modules/Compiler/ARMCC-ASM.cmake b/Modules/Compiler/ARMCC-ASM.cmake
index 8e3cfc5..539d525 100644
--- a/Modules/Compiler/ARMCC-ASM.cmake
+++ b/Modules/Compiler/ARMCC-ASM.cmake
@@ -3,5 +3,5 @@ include(Compiler/ARMCC)
 set(CMAKE_ASM_OUTPUT_EXTENSION ".o")
 set(CMAKE_ASM_OUTPUT_EXTENSION_REPLACE 1)
 
-set(CMAKE_ASM_COMPILE_OBJECT   "  -o  
")
+set(CMAKE_ASM_COMPILE_OBJECT   "   -o 
 ")
 set(CMAKE_ASM_SOURCE_FILE_EXTENSIONS s;asm;msa)
diff --git a/Modules/Platform/Generic-ADSP-ASM.cmake 
b/Modules/Platform/Generic-ADSP-ASM.cmake
index 63a1388..e718bec 100644
--- a/Modules/Platform/Generic-ADSP-ASM.cmake
+++ b/Modules/Platform/Generic-ADSP-ASM.cmake
@@ -3,5 +3,5 @@ include(Platform/Generic-ADSP-Common)
 set(CMAKE_ASM_SOURCE_FILE_EXTENSIONS asm)
 set(CMAKE_ASM_OUTPUT_EXTENSION ".doj" )
 set(CMAKE_ASM_COMPILE_OBJECT
-"  -proc ${ADSP_PROCESSOR} -si-revision 
${ADSP_PROCESSOR_SILICIUM_REVISION} -o  ")
+"   -proc ${ADSP_PROCESSOR} 
-si-revision ${ADSP_PROCESSOR_SILICIUM_REVISION} -o  ")
 
diff --git a/Modules/Platform/gas.cmake b/Modules/Platform/gas.cmake
index 7d2bc84..7c659f2 100644
--- a/Modules/Platform/gas.cmake
+++ b/Modules/Platform/gas.cmake
@@ -4,7 +4,7 @@ else()
   set(CMAKE_ASM${ASM_DIALECT}_OUTPUT_EXTENSION .obj)
 endif()
 
-set(CMAKE_ASM${ASM_DIALECT}_COMPILE_OBJECT " 
 -o  ")
+set(CMAKE_ASM${ASM_DIALECT}_COMPILE_OBJECT " 
  -o  ")
 
 set(CMAKE_ASM${ASM_DIALECT}_CREATE_STATIC_LIBRARY
   " cr"

---

Summary of changes:
 Modules/CMakeASM-ATTInformation.cmake   |2 +-
 Modules/CMakeASM_NASMInformation.cmake  |2 +-
 Modules/Compiler/ARMCC-ASM.cmake|2 +-
 Modules/Platform/Generic-ADSP-ASM.cmake |2 +-
 Modules/Platform/gas.cmake  |2 +-
 5 files changed, 5 insertions(+), 5 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

Re: [cmake-developers] Patch for 0016029: GHS Generator does not support LINK_FLAGS property

2016-03-28 Thread Brad King 
On 03/28/2016 11:33 AM, Geoffrey Viola wrote:
> Here is a patch for issue 16029: https://cmake.org/Bug/view.php?id=16029.

Thanks, applied:

 GHS: Factor out compiler information shared among languages
 https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=230d50ed

 GHS: Implement link flags and dirs for non-target groups (#16029)
 https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=36ad8dd4

-Brad

-- 

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-commits] CMake branch, next, updated. v3.5.1-669-g0f364a2

2016-03-28 Thread Brad King 
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  0f364a2b1b134ce79fe62093f959d0d79657a96c (commit)
   via  36ad8dd440069b126ca28dccf57e8c65188c693b (commit)
   via  230d50ed1a1bbeac3b840ecc2d45c1b8710c8be4 (commit)
  from  3884580aabce46aaff070ebbae61fac320552410 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0f364a2b1b134ce79fe62093f959d0d79657a96c
commit 0f364a2b1b134ce79fe62093f959d0d79657a96c
Merge: 3884580 36ad8dd
Author: Brad King 
AuthorDate: Mon Mar 28 13:26:09 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Mar 28 13:26:09 2016 -0400

Merge topic 'ghs-link-flags' into next

36ad8dd4 GHS: Implement link flags and dirs for non-target groups (#16029)
230d50ed GHS: Factor out compiler information shared among languages


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=36ad8dd440069b126ca28dccf57e8c65188c693b
commit 36ad8dd440069b126ca28dccf57e8c65188c693b
Author: Geoff Viola 
AuthorDate: Sat Mar 26 21:28:31 2016 -0600
Commit: Brad King 
CommitDate: Mon Mar 28 11:46:46 2016 -0400

GHS: Implement link flags and dirs for non-target groups (#16029)

diff --git a/Modules/Compiler/GHS.cmake b/Modules/Compiler/GHS.cmake
index cfc29c2..e6a867d 100644
--- a/Modules/Compiler/GHS.cmake
+++ b/Modules/Compiler/GHS.cmake
@@ -4,3 +4,5 @@ endif()
 set(__COMPILER_GHS 1)
 
 set(CMAKE_EXECUTABLE_SUFFIX ".as")
+set(CMAKE_LIBRARY_PATH_TERMINATOR "\n")
+set(CMAKE_LIBRARY_PATH_FLAG "  -L")
diff --git a/Source/cmGhsMultiTargetGenerator.cxx 
b/Source/cmGhsMultiTargetGenerator.cxx
index c5813ba..1f17f8f 100644
--- a/Source/cmGhsMultiTargetGenerator.cxx
+++ b/Source/cmGhsMultiTargetGenerator.cxx
@@ -149,7 +149,7 @@ void cmGhsMultiTargetGenerator::Generate()
 this->WriteIncludes(config, language);
 if (this->GeneratorTarget->GetType() == cmState::EXECUTABLE)
   {
-  this->WriteTargetLinkLibraries();
+  this->WriteTargetLinkLibraries(config, language);
   }
 this->WriteCustomCommands();
 
@@ -365,7 +365,8 @@ void cmGhsMultiTargetGenerator::WriteIncludes(const 
std::string ,
 }
 }
 
-void cmGhsMultiTargetGenerator::WriteTargetLinkLibraries()
+void cmGhsMultiTargetGenerator::WriteTargetLinkLibraries(
+  std::string const& config, std::string const& language)
 {
   // library directories
   cmTargetDependSet tds =
@@ -393,6 +394,35 @@ void cmGhsMultiTargetGenerator::WriteTargetLinkLibraries()
 *this->GetFolderBuildStreams() << "-l\"" << libName << "\""
<< std::endl;
 }
+
+  if (!this->TargetGroup)
+{
+std::string linkLibraries;
+std::string flags;
+std::string linkFlags;
+std::string frameworkPath;
+std::string linkPath;
+std::string createRule =
+this->GeneratorTarget->GetCreateRuleVariable(language, config);
+bool useWatcomQuote =
+this->Makefile->IsOn(createRule + "_USE_WATCOM_QUOTE");
+this->LocalGenerator->GetTargetFlags(
+  linkLibraries, flags, linkFlags,
+  frameworkPath, linkPath,
+  this->GeneratorTarget, useWatcomQuote);
+linkFlags = cmSystemTools::TrimWhitespace(linkFlags);
+
+if (!linkPath.empty())
+  {
+  linkPath = " " + linkPath.substr(0U, linkPath.size() - 1U);
+  *this->GetFolderBuildStreams() << linkPath;
+  }
+
+if (!linkFlags.empty())
+  {
+  *this->GetFolderBuildStreams() << "" << linkFlags << std::endl;
+  }
+}
 }
 
 void cmGhsMultiTargetGenerator::WriteCustomCommands()
diff --git a/Source/cmGhsMultiTargetGenerator.h 
b/Source/cmGhsMultiTargetGenerator.h
index 327fdef..e85e412 100644
--- a/Source/cmGhsMultiTargetGenerator.h
+++ b/Source/cmGhsMultiTargetGenerator.h
@@ -81,7 +81,8 @@ private:
  std::string const );
 
   void WriteIncludes(const std::string , const std::string );
-  void WriteTargetLinkLibraries();
+  void WriteTargetLinkLibraries(std::string const& config,
+std::string const& language);
   void WriteCustomCommands();
   void
   WriteCustomCommandsHelper(std::vector const ,

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=230d50ed1a1bbeac3b840ecc2d45c1b8710c8be4
commit 230d50ed1a1bbeac3b840ecc2d45c1b8710c8be4
Author: Geoff Viola 
AuthorDate: Sat Mar 26 21:28:31 2016 -0600
Commit: Brad King 
CommitDate: Mon Mar 28 11:44:58 2016 -0400

GHS: Factor out compiler information shared among languages

Move common information in

Re: [CMake] 'CPACK_RPM_PACKAGE_AUTOPROV' doesn't work when pack existing binaries with CPack

2016-03-28 Thread Domen Vrankar 
CPackRPM generates spec files from which it generates the packages
(just search for *.spec in your build directory). It is possible that
Autoprov or Autoreqprov is not set correctly. Another possibility is
that rpmbuild executed from within CPack is executed with different
parameters.

Please check for the differences between your spec file and the one
that is generated by CPackRPM. I can also do that myself if you
provide me with a minimal working spec file and commands that you used
for generating the correct package.

Thanks,
Domen

2016-03-28 8:22 GMT+02:00 Wang, Peng 1. (Nokia - CN/Hangzhou)
:
> Thanks for your answer.
> Actually, I was trying this on RHEL, not ubuntu. rpmbuild and rpmdevtools are 
> correctly installed in my machine, I've tested that to generate RPM with my 
> spec file based on rpmbuild and rpmdevtools, it works, libraries information 
> is generated in the 'PROVIDES' fields of the RPM package. But with cpack, it 
> doesn't.
>
> Wang Peng (Rex)
> Seat: 21F
> HZ SE Team
> +86018605811125
>
> -Original Message-
> From: EXT Domen Vrankar [mailto:domen.vran...@gmail.com]
> Sent: Friday, March 25, 2016 5:52 PM
> To: Wang, Peng 1. (Nokia - CN/Hangzhou) 
> Cc: cmake@cmake.org
> Subject: Re: [CMake] 'CPACK_RPM_PACKAGE_AUTOPROV' doesn't work when pack 
> existing binaries with CPack
>
>> Does someone know why this "CPACK_RPM_PACKAGE_AUTOPROV" option doesn't take
>> effect? how can I make it auto generates these 'PROVIDES' information in the
>> RPM?  thanks for your time and it will be very appreciated if you can
>> provide some hints.
>
> CPackRPM relies on rpmbuild and other rpm tools to correctly create
> the package and rpm is not the most automation friendly beast because
> of its macro system.
>
> In cmake tests: Tests/RunCMake/CPack/RPM/DEPENDENCIES-specifics.cmake
> there is a comment
>
> # FIXME auto autoprov is not tested at the moment as Ubuntu 15.04 rpmbuild
> # does not use them correctly: https://bugs.launchpad.net/rpm/+bug/1475755
>
> I'm guessing that this is environment related (missing packages,
> failing/missing rpm macros, ...) as for the same version of rpmbuild
> installed on different Linux distros (each through their own package
> repository that came with the distro) it either worked or not and
> never told that it failed (you could see that only after inspecting
> the content of rpm package after it has already been created). I
> haven't looked deeper into it but perhaps you've stumbled across this
> as well.
>
> You could try to make the package on a different distro and see if it
> works there.
>
> Regards,
> Domen
-- 

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

Re: [cmake-developers] CPackRPM not dealing correctly with symlinks

2016-03-28 Thread Domen Vrankar 
Attached is CPackRPM.cmake that fixes cases where symlink points to
locations outside packaging directory.

Please confirm that it fixes your problem. Patched CPackRPM.cmake is
from master branch so please replace the file in your 3.5.0 version of
CMake.

Thanks,
Domen

2016-03-24 9:48 GMT+01:00 Attila Krasznahorkay :
> Hi Domen,
>
> Unfortunately I can't seem to create an easy-to-package example for the 
> issue. Since it seems that the file given to the install(...) command has to 
> be in a "very different place" than the source or binary directories for the 
> issue to come up. (My guess is that if the file shares some of its path with 
> the build directory, CPackRPM uses a different method for dealing with it 
> than if the two paths don't share any prefix.)
>
> In our case some files are picked up from a network drive, while the build 
> happens (naturally) on a local drive. I can reproduce the issue with a 
> CMakeLists.txt file like:
>
> cmake_minimum_required( VERSION 2.8 )
> project( CPackRPMLinkProblem )
>
> install( FILES /afs/cern.ch/.../some_link.txt DESTINATION . )
>
> set( CPACK_PACKAGE_RELOCATABLE TRUE )
> include( CPack )
>
> As long as the build directory's path name ends up being longer than the path 
> name of the file specified in the install(...) command, the RPM building 
> fails. As it does for instance here:
>
> http://atlas-computing.web.cern.ch/atlas-computing/links/distDirectory/nightlies/experimentalWebArea/nicos_web_areaCMAKE64BS6G49AnlOpt/NICOS_Log_rel_4/nicos_rpm_build.html
>
> Cheers,
>Attila
>
>> On 23 Mar 2016, at 15:57, Domen Vrankar  wrote:
>>
>> As a workaround you could set files that you would like to be excluded
>> from symlink relocation with CPACK_RPM_USER_FILELIST or
>> CPACK_RPM__USER_FILELIST.
>>
>> I'll have a look at how this could be solved for later versions of CPack.
>> Do I understand correctly that those errors occur when a symlink is
>> pointing to another simlink outside your project?
>> Could you please provide a minimal example of all your cases?
>>
>> Thanks,
>> Domen
>>
>>
>> 2016-03-23 14:13 GMT+01:00 Attila Krasznahorkay
>> :
>>> Hi Brad,
>>>
>>> I did. Then I get:
>>>
>>> CMake Error at 
>>> /afs/cern.ch/work/k/krasznaa/public/cmake/3.5.0/share/cmake-3.5/Modules/CPackRPM.cmake:981
>>>  (string):
>>> string begin index: 164 is out of range 0 - 156
>>> Call Stack (most recent call first):
>>> /afs/cern.ch/work/k/krasznaa/public/cmake/3.5.0/share/cmake-3.5/Modules/CPackRPM.cmake:1625
>>>  (cpack_rpm_prepare_install_files)
>>> /afs/cern.ch/work/k/krasznaa/public/cmake/3.5.0/share/cmake-3.5/Modules/CPackRPM.cmake:1787
>>>  (cpack_rpm_generate_package)
>>>
>>> You can find the full output here:
>>>
>>> http://atlas-computing.web.cern.ch/atlas-computing/links/distDirectory/nightlies/experimentalWebArea/nicos_web_areaCMAKE64BS6G49TrgOpt/NICOS_Log_rel_3/nicos_rpm_build.html
>>>
>>> Note that when I tried to build the project in a build area with a shorter 
>>> path, then the RPM building succeeded. Just because by chance in that case 
>>> in the expression
>>>
>>> string(SUBSTRING "${SYMLINK_POINT_}" ${WDR_LEN_} -1 SYMLINK_POINT_WD_)
>>>
>>> the work directory length was shorter than the length of the path outside 
>>> of the project.
>>>
>>> Of course this is the code that we're talking about:
>>>
>>> https://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/CPackRPM.cmake;h=7ffec136deabb8f28d6293cdc96e43cd4a2af70d;hb=HEAD#l994
>>>
>>> Cheers,
>>> Attila
>>>
 On 23 Mar 2016, at 13:50, Brad King  wrote:

 On 03/23/2016 08:44 AM, Attila Krasznahorkay wrote:
> CMake Error at /afs/cern.ch/sw/lcg/contrib/CMake/3.3.2/...

 Please try with CMake 3.5.

 -Brad

>>>
>
#.rst:
# CPackRPM
# 
#
# The builtin (binary) CPack RPM generator (Unix only)
#
# Variables specific to CPack RPM generator
# ^
#
# CPackRPM may be used to create RPM package using CPack.
# CPackRPM is a CPack generator thus it uses the ``CPACK_XXX`` variables
# used by CPack : https://cmake.org/Wiki/CMake:CPackConfiguration.
#
# CPackRPM has specific features which are controlled by the specifics
# :code:`CPACK_RPM_XXX` variables.
#
# :code:`CPACK_RPM__` variables may be used in order to have
# **component** specific values.  Note however that  refers to the
# **grouping name** written in upper case. It may be either a component name or
# a component GROUP name. Usually those vars correspond to RPM spec file
# entities, one may find information about spec files here
# http://www.rpm.org/wiki/Docs
#
# .. note::
#
#  `` part of variables is prefered to be in upper case (for e.g. if
#  component is named `foo` then use `CPACK_RPM_FOO_` variable name format)
#  as is with other `CPACK__` variables.
#  For the purposes of back compatibility (CMake/CPack version 3.5 and

[cmake-developers] [CMake 0016035]: Would like support for --remote option with git submodules

2016-03-28 Thread Mantis Bug Tracker 

The following issue has been SUBMITTED. 
== 
https://public.kitware.com/Bug/view.php?id=16035 
== 
Reported By:Clinton Stimpson
Assigned To:
== 
Project:CMake
Issue ID:   16035
Category:   CTest
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-03-28 11:55 EDT
Last Modified:  2016-03-28 11:55 EDT
== 
Summary:Would like support for --remote option with git
submodules
Description: 
CTest supports --init and --recursive options for git submodules, but not the
--remote option.

The --remote option is for submodules that track branches instead of commits.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-03-28 11:55 Clinton StimpsonNew 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

Re: [cmake-developers] [PATCH SET] Support of Clang/C2 compiler

2016-03-28 Thread Brad King 
On 03/27/2016 08:31 PM, Mariusz Pluciński wrote:
>>> 8. Tests: fix Module.WriteCompilerDetectionHeader
>>> 15. Tests: disable VSMidl on Clang/C2
>> I'm going to let these fail for now until someone has time to investigate
> I see. I didn't know, how do you handle that situations in CMake project.
[snip]
>> Would you be able to run nightly testing with this generator/compiler?
> 
> Sure I can. I have set it up today
> ( https://open.cdash.org/viewSite.php?siteid=17356 ), and now,

Wonderful, thanks!

> it seems that there're some more failures that I saw while running
> these tests before. I'm going to take a look on them and fix them if I manage
> to do so.

Yes, please look locally at the VSExcludeFromDefaultBuild-* test failures.

For the Module.WriteCompilerDetectionHeader and VSMidl tests we can
simply exclude them from testing until someone can investigate and
fix the underlying problems.  In your ctest scripts you can add

  set(CTEST_TEST_ARGS EXCLUDE "VSMidl|Module.WriteCompilerDetectionHeader")

before including cmake_common.cmake.

Thanks,
-Brad

-- 

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] CMAKE_SIZEOF_VOID_P is unset when building libgit2 on Windows

2016-03-28 Thread Brad King 
On 03/25/2016 05:08 PM, Sebastian Schuberth wrote:
> Looking at CMakeError.log was a good hint. I found:
> 
> C:/Ruby-DevKit/mingw/bin/gcc.exe-fPIC-o
> CMakeFiles/cmTC_c0166.dir/CMakeCCompilerABI.c.obj   -c "C:/Program
> Files (x86)/CMake/share/cmake-3.5/Modules/CMakeCCompilerABI.c"
> 
> /usr/bin/sh: -c: line 0: syntax error near unexpected token `('
> /usr/bin/sh: -c: line 0: `C:/Ruby-DevKit/mingw/bin/gcc.exe-fPIC
> -o CMakeFiles/cmTC_c0166.dir/CMakeCCompilerABI.c.obj   -c \C:/Program
> Files (x86)/CMake/share/cmake-3.5/Modules/CMakeCCompilerABI.c\'
> CMakeFiles/cmTC_c0166.dir/build.make:65: recipe for target
> 'CMakeFiles/cmTC_c0166.dir/CMakeCCompilerABI.c.obj' failed
> ---8<---
> 
> There seems to be some problem in escaping the non-alphanumeric chars
> in the path to "CMakeCCompilerABI.c".

Strange.  CMake is regularly used from "C:/Program Files (x86)/CMake".

> Any hint how to debug this further?

Try running the logged compiler command line by hand:

  C:/Ruby-DevKit/mingw/bin/gcc.exe -c "C:/Program Files 
(x86)/CMake/share/cmake-3.5/Modules/CMakeCCompilerABI.c"

Also try configuring a small test project in a fresh build tree:

 $ cat CMakeLists.txt
 cmake_minimum_required(VERSION 3.5)
 project(test C)
 message("${CMAKE_SIZEOF_VOID_P}")

If that reproduces the problem, try configuring with --debug-trycompile
so that the CMakeFiles/CmakeTmp/CMakeFiles/cmTC_*.dir/build.make files
will be left behind for inspection.

-Brad
-- 

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

Re: [cmake-developers] CMake API for warnings

2016-03-28 Thread Brad King 
On 03/28/2016 01:49 AM, Geoffrey Viola wrote:
> Thanks for the feedback. I’ll have to look more in-depth at Xcode specific 
> issues.
>> Take a look at this approach:
>> * https://github.com/ruslo/sugar/wiki/Cross-platform-warning-suppression
> 
> I took a look at your repository. It’s very sophisticated.

I'd prefer to see an approach that abstracts the warning levels
in a similar way to COMPILE_FEATURES, COMPILE_DEFINITIONS,
INCLUDE_DIRECTORIES, etc.  Project code would set directory or
target properties to specify warning levels and the generators
would map them to the proper flags or project file settings
automatically.

Something like this has long been missing for compiler warnings
and optimization levels.

-Brad

-- 

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] [CMake 0016030]: CMAKE_ASM_NASM_COMPILE_OBJECT lacks

2016-03-28 Thread Brad King 
On 03/25/2016 06:27 PM, Gregor Jasny wrote:
> I pushed a first commit to asm-includes topic but did not merge to next,
> yet. Looking at your quoted patch I wonder if  is missing as well?

Yes, but that would have been missing before  was split
out too.  The  were split out long before.  You'll have
to dig through the history a bit to figure out what happened.

Thanks,
-Brad

-- 

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] add_custom_command() OUTPUT does not accept generator expressions, why?

2016-03-28 Thread Brad King 
On 03/27/2016 06:11 AM, Dan Liew wrote:
> OUTPUT does not accept generator expressions, why?

It hasn't been implemented.  At least at one time it would have been
very hard to implement.  I'm not sure now because there has been a lot
of refactoring since I last looked at it.

There is some discussion here:

 https://cmake.org/Bug/view.php?id=13840
 https://cmake.org/Bug/view.php?id=12877#c28315

> If I can't use generator expressions with ``OUTPUT``, how am I
> supposed to output a file into the build directory of a target?

Unfortunately it is not possible to do cleanly without fixing the
above.  Approximations include:

* Use a POST_BUILD command on the target instead.

* Make the OUTPUT a timestamp file and generate the real output
  as a side effect.

If anyone is interested in trying to implement generator expressions
for custom command outputs, I can provide more details to get started.

-Brad

-- 

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

[Cmake-commits] CMake branch, next, updated. v3.5.1-666-g3884580

2016-03-28 Thread Brad King 
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  3884580aabce46aaff070ebbae61fac320552410 (commit)
   via  d29004756fa314119a91821a14eef81a2ffcf40a (commit)
   via  81cec38b99ce2a68a57b81fa138351f85a4536c9 (commit)
   via  c69ed0a8844ea5f417fefa758cdbcfc978d89712 (commit)
   via  aa9227aa4d2ff415abd7c9a24ff0cc21d9721640 (commit)
   via  6732749e5b89198ed391b516ee57d835893e723d (commit)
   via  9b5652846f131f188f919b6d5f7a906d43d2969a (commit)
  from  e5d7429c7033f1e67833fc55689f14cbd23146b8 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=3884580aabce46aaff070ebbae61fac320552410
commit 3884580aabce46aaff070ebbae61fac320552410
Merge: e5d7429 d290047
Author: Brad King 
AuthorDate: Mon Mar 28 09:25:58 2016 -0400
Commit: Brad King 
CommitDate: Mon Mar 28 09:25:58 2016 -0400

Merge branch 'master' into next


---

Summary of changes:
 Source/CMakeVersion.cmake |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, master, updated. v3.5.1-328-gd290047

2016-03-28 Thread Brad King 
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  d29004756fa314119a91821a14eef81a2ffcf40a (commit)
   via  c41b9dc7b5d9e38ec89c5865ee7a8d6409ad4dea (commit)
  from  81cec38b99ce2a68a57b81fa138351f85a4536c9 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d29004756fa314119a91821a14eef81a2ffcf40a
commit d29004756fa314119a91821a14eef81a2ffcf40a
Merge: 81cec38 c41b9dc
Author: Brad King 
AuthorDate: Mon Mar 28 09:25:45 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Mar 28 09:25:45 2016 -0400

Merge topic 'test-fix-FindGTK2-cxx11'

c41b9dc7 Tests: Fix GTK2Components.gtkmm test with sigc++ >= 2.5.1


---

Summary of changes:
 Tests/FindGTK2/gtkmm/CMakeLists.txt |5 +
 1 file changed, 5 insertions(+)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, master, updated. v3.5.1-324-gc69ed0a

2016-03-28 Thread Brad King 
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  c69ed0a8844ea5f417fefa758cdbcfc978d89712 (commit)
   via  06b7f5d2cac5e697b503337e870e34b11a592bd1 (commit)
  from  aa9227aa4d2ff415abd7c9a24ff0cc21d9721640 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c69ed0a8844ea5f417fefa758cdbcfc978d89712
commit c69ed0a8844ea5f417fefa758cdbcfc978d89712
Merge: aa9227a 06b7f5d
Author: Brad King 
AuthorDate: Mon Mar 28 09:25:40 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Mar 28 09:25:40 2016 -0400

Merge topic 'only_change_timeout_once'

06b7f5d2 CTest: Only apply the secondary test timeout once


---

Summary of changes:
 Source/CTest/cmCTestRunTest.cxx |2 ++
 1 file changed, 2 insertions(+)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, master, updated. v3.5.1-326-g81cec38

2016-03-28 Thread Brad King 
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  81cec38b99ce2a68a57b81fa138351f85a4536c9 (commit)
   via  a364d2513a3fac76cf12cf3db21b7e9600ac51a4 (commit)
  from  c69ed0a8844ea5f417fefa758cdbcfc978d89712 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=81cec38b99ce2a68a57b81fa138351f85a4536c9
commit 81cec38b99ce2a68a57b81fa138351f85a4536c9
Merge: c69ed0a a364d25
Author: Brad King 
AuthorDate: Mon Mar 28 09:25:43 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Mar 28 09:25:43 2016 -0400

Merge topic 'xcode73-xctest-location'

a364d251 Xcode: Fixup XCTest bundle location for Xcode 7.3


---

Summary of changes:
 Modules/FindXCTest.cmake |4 
 1 file changed, 4 insertions(+)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, next, updated. v3.5.1-659-ge5d7429

2016-03-28 Thread Brad King 
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  e5d7429c7033f1e67833fc55689f14cbd23146b8 (commit)
   via  a364d2513a3fac76cf12cf3db21b7e9600ac51a4 (commit)
  from  021e01c423475f7c358a50775e0fc4073be8e75c (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e5d7429c7033f1e67833fc55689f14cbd23146b8
commit e5d7429c7033f1e67833fc55689f14cbd23146b8
Merge: 021e01c a364d25
Author: Brad King 
AuthorDate: Mon Mar 28 09:23:54 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Mon Mar 28 09:23:54 2016 -0400

Merge topic 'xcode73-xctest-location' into next

a364d251 Xcode: Fixup XCTest bundle location for Xcode 7.3


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a364d2513a3fac76cf12cf3db21b7e9600ac51a4
commit a364d2513a3fac76cf12cf3db21b7e9600ac51a4
Author: Gregor Jasny 
AuthorDate: Fri Mar 25 22:20:14 2016 +0100
Commit: Brad King 
CommitDate: Mon Mar 28 09:23:35 2016 -0400

Xcode: Fixup XCTest bundle location for Xcode 7.3

Prior to Xcode 7.3 a XCTest bundle was built like an ordinary
bundle. But starting with Xcode 7.3 it is implicitely built as
a plugin for the test host. It looks like in that case the
'Build Products Path' is ignored.

This patch simply sets the CMake target output path to the value
Xcode expects internally to get a matching view of both.

The command:

  xcodebuild -showBuildSettings -target CocoaExampleTests -configuration 
Debug

Output with Xcode 7.2:

  TARGET_BUILD_DIR = .../Tests/XCTest/Debug

Output with Xcode 7.3

  TARGET_BUILD_DIR = 
.../Tests/XCTest/Debug/CocoaExample.app/Contents/PlugIns

Signed-off-by: Gregor Jasny 

diff --git a/Modules/FindXCTest.cmake b/Modules/FindXCTest.cmake
index 3cd9c22..805a58c 100644
--- a/Modules/FindXCTest.cmake
+++ b/Modules/FindXCTest.cmake
@@ -140,6 +140,10 @@ function(xctest_add_bundle target testee)
   set_target_properties(${target} PROPERTIES
 XCODE_ATTRIBUTE_BUNDLE_LOADER "$(TEST_HOST)"
 XCODE_ATTRIBUTE_TEST_HOST "$")
+  if(NOT XCODE_VERSION VERSION_LESS 7.3)
+set_target_properties(${target} PROPERTIES
+  LIBRARY_OUTPUT_DIRECTORY "$/../PlugIns")
+  endif()
 else(XCODE)
   target_link_libraries(${target}
 PRIVATE -bundle_loader $)

---

Summary of changes:


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

Re: [cmake-developers] CMake daemon for user tools

2016-03-28 Thread Stephen Kelly 
On 03/25/2016 09:25 AM, Tobias Hunger wrote:
> I am personally rather unsure about how to proceed. I can help make
> this branch production/merge ready, but I do not want to maintain it
> indefinitely after it is merged. It touches to many CMake internals
> for me to be comfortable hacking on that code. 

Yes, this lack of interest in general in maintaining it upstream is
currently a demotivator. I think we need a group of people interested in
doing that.

Brad/Ben, no response since I posted the blog or the code. Any word of
interest in any of it?

Thanks,

Steve.

-- 

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] 'CPACK_RPM_PACKAGE_AUTOPROV' doesn't work when pack existing binaries with CPack

2016-03-28 Thread Wang, Peng 1. (Nokia - CN/Hangzhou) 
Thanks for your answer.
Actually, I was trying this on RHEL, not ubuntu. rpmbuild and rpmdevtools are 
correctly installed in my machine, I've tested that to generate RPM with my 
spec file based on rpmbuild and rpmdevtools, it works, libraries information is 
generated in the 'PROVIDES' fields of the RPM package. But with cpack, it 
doesn't.

Wang Peng (Rex)
Seat: 21F
HZ SE Team
+86018605811125

-Original Message-
From: EXT Domen Vrankar [mailto:domen.vran...@gmail.com] 
Sent: Friday, March 25, 2016 5:52 PM
To: Wang, Peng 1. (Nokia - CN/Hangzhou) 
Cc: cmake@cmake.org
Subject: Re: [CMake] 'CPACK_RPM_PACKAGE_AUTOPROV' doesn't work when pack 
existing binaries with CPack

> Does someone know why this "CPACK_RPM_PACKAGE_AUTOPROV" option doesn't take
> effect? how can I make it auto generates these 'PROVIDES' information in the
> RPM?  thanks for your time and it will be very appreciated if you can
> provide some hints.

CPackRPM relies on rpmbuild and other rpm tools to correctly create
the package and rpm is not the most automation friendly beast because
of its macro system.

In cmake tests: Tests/RunCMake/CPack/RPM/DEPENDENCIES-specifics.cmake
there is a comment

# FIXME auto autoprov is not tested at the moment as Ubuntu 15.04 rpmbuild
# does not use them correctly: https://bugs.launchpad.net/rpm/+bug/1475755

I'm guessing that this is environment related (missing packages,
failing/missing rpm macros, ...) as for the same version of rpmbuild
installed on different Linux distros (each through their own package
repository that came with the distro) it either worked or not and
never told that it failed (you could see that only after inspecting
the content of rpm package after it has already been created). I
haven't looked deeper into it but perhaps you've stumbled across this
as well.

You could try to make the package on a different distro and see if it
works there.

Regards,
Domen
-- 

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