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

[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

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

[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

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

[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

[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

[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-developers] CMake API for warnings

[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

[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-developers] CMake daemon for user tools

[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