Hi Brad, thanks for that information. It is great to see that you are working on this.
Could you already verify if this problem is also the cause for the coverage issue? On 09/05/2017 01:31 PM, Brad King wrote: > On 09/02/2017 03:14 AM, Gerhard Gappmeier wrote: >> This is quite annoying, inconsistent with Makefiles and was already >> reported once here: https://cmake.org/Bug/print_bug_page.php?bug_id=13894 >> AFAIK this was never fixed. > Discussion of that issue is now here: > > https://gitlab.kitware.com/cmake/cmake/issues/13894 > > We made a serious attempt to fix it, but ran into a major problem > described here: > > https://gitlab.kitware.com/cmake/cmake/issues/13894#note_233789 > > Fixing it requires a feature in Ninja: > > https://github.com/ninja-build/ninja/issues/1251 > > I posted a proposal to their list about it but got no response: > > https://groups.google.com/forum/#!topic/ninja-build/yJvs7u0n2iA > > --- > > One may use out-of-source builds to get absolute paths to the files > in the main source tree. > > -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
