Re: [cmake-developers] Export files in the build tree have a total path length which is unnecessarily long

2016-08-09 Thread Alan W. Irwin
On 2016-08-09 10:11-0400 Brad King wrote: On 08/08/2016 02:54 PM, Alan W. Irwin wrote: For all such staging areas, would it be straightforward to hash the paths for the cmake-generated EXPORT files in the build tree to substantially reduce their pathlengths for the absolute install location

Re: [cmake-developers] Export files in the build tree have a total path length which is unnecessarily long

2016-08-09 Thread Brad King
On 08/08/2016 02:54 PM, Alan W. Irwin wrote: > For all such staging areas, would it be straightforward to hash the > paths for the cmake-generated EXPORT files in the build tree to > substantially reduce their pathlengths for the absolute install > location case while still avoiding name

Re: [cmake-developers] QtAutogen 3.6.0 directory nesting overflow patch

2016-08-09 Thread Brad King
On 08/08/2016 04:19 PM, Sebastian Holtermann wrote: > It is back to what it was in 3.5 for the all-qrc-names-unique case. > So yes, existing projects get the same symbol name they used to get. Good, thanks. > New projects that now can use non unique file names > may get a symbol name based on

Re: [cmake-developers] QtAutogen 3.6.0 directory nesting overflow patch

2016-08-09 Thread Brad King
On 08/09/2016 11:45 AM, Sebastian Holtermann wrote: > In the non-unique-qrc-name case the checksum is hard to reproduce for a > user. In this case I'd say CMake does not make any guaratees for > - the actual symbol name > - the symbol name to not change in the future > It only guarantees the

Re: [cmake-developers] QtAutogen 3.6.0 directory nesting overflow patch

2016-08-09 Thread Sebastian Holtermann
Am 09.08.2016 um 17:52 schrieb Brad King: On 08/09/2016 11:45 AM, Sebastian Holtermann wrote: In the non-unique-qrc-name case the checksum is hard to reproduce for a user. In this case I'd say CMake does not make any guaratees for - the actual symbol name - the symbol name to not change in

Re: [cmake-developers] QtAutogen 3.6.0 directory nesting overflow patch

2016-08-09 Thread Sebastian Holtermann
Am 09.08.2016 um 16:11 schrieb Brad King: On 08/08/2016 04:19 PM, Sebastian Holtermann wrote: It is back to what it was in 3.5 for the all-qrc-names-unique case. So yes, existing projects get the same symbol name they used to get. Good, thanks. New projects that now can use non unique file

Re: [cmake-developers] [PATCH] Fix RunCMake.Framework on case sensitive file systems.

2016-08-09 Thread Brad King
On 08/09/2016 03:47 PM, Chaoren Lin via cmake-developers wrote: > The file is lowercase: Tests/RunCMake/Framework/osx.cmake Thanks, applied: Tests: Fix RunCMake.Framework on case sensitive file systems. https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=677e73cb -Brad -- Powered by

[cmake-developers] Email feed for new CMake bugs

2016-08-09 Thread Gregor Jasny via cmake-developers
Hello, in the past (with Mantis) I found it quite helpful to see new bugs posted here on this mailing list. Is it planned to restore that functionality? Thanks, Gregor -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Re: [cmake-developers] [PATCH] Fix RunCMake.Framework on case sensitive file systems.

2016-08-09 Thread Gregor Jasny via cmake-developers
On 09/08/16 22:01, Brad King wrote: > On 08/09/2016 03:47 PM, Chaoren Lin via cmake-developers wrote: >> The file is lowercase: Tests/RunCMake/Framework/osx.cmake > > Thanks, applied: > > Tests: Fix RunCMake.Framework on case sensitive file systems. >

Re: [cmake-developers] Email feed for new CMake bugs

2016-08-09 Thread Brad King
On 08/09/2016 03:46 PM, Gregor Jasny via cmake-developers wrote: > in the past (with Mantis) I found it quite helpful to see new bugs > posted here on this mailing list. Is it planned to restore that > functionality? Not currently. GitLab has notification settings you can use to "Watch" a

[cmake-developers] [PATCH] Fix RunCMake.Framework on case sensitive file systems.

2016-08-09 Thread Chaoren Lin via cmake-developers
The file is lowercase: Tests/RunCMake/Framework/osx.cmake --- Tests/RunCMake/Framework/RunCMakeTest.cmake | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Tests/RunCMake/Framework/RunCMakeTest.cmake b/Tests/RunCMake/Framework/RunCMakeTest.cmake index d810283..eeea6f1 100644