Re: [CMake] cmake 3.5 vs 3.6 + qt
Thanks On Thu, 21 Jul 2016, 23:33 Brad King <brad.k...@kitware.com> wrote: > On 07/18/2016 06:53 PM, Tom Kulaga wrote: > > I'll try and get together a minimal example to highlight the difference. > > This has now been reported with additional information here: > > https://gitlab.kitware.com/cmake/cmake/issues/16209 > > We will have to revert the offending changes until another > solution is found. > > -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] cmake 3.5 vs 3.6 + qt
I'll try and get together a minimal example to highlight the difference. On Tue, 19 Jul 2016 at 03:16 Brad King <brad.k...@kitware.com> wrote: > On 07/15/2016 04:50 AM, David Callu wrote: > > 2016-07-15 1:54 GMT+02:00 Tom Kulaga: > >> I'm using 3.5.2 for a qt based project and I've updated to 3.6 and the > RCC feature > >> seems to fail. Here's a summary > >> When I swtiched to 3.6, the compiler can no longer link to the > generated rcc files. > > > > Same thing on my side. I call in my code functions defined in generated > .cpp from moc/rcc. > > Functions name are based on file path used during .cpp generation. > > And this path change from cmake 3.5 to 3.6. > > The location likely changed in the topic by Sebastian Holtermann merged > here: > > Merge topic 'autogen-updates' > https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=76e793b9 > > The goal is to support same-named files in different subdirectories. > See this issue: > > https://gitlab.kitware.com/cmake/cmake/issues/12873 > https://cmake.org/Bug/view.php?id=12873 > > and discussion on the dev list here: > > http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/16229 > > I'm not particularly familiar with rcc/AUTORCC/etc. but it is not clear > why the path to the generated file matters. CMake generates a file and > adds the proper references to it. Its location is an implementation > detail. I don't think our documentation ever guaranteed a specific > location. > > Please post a more complete code example that shows the failure case. > > 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
Re: [CMake] cmake 3.5 vs 3.6 + qt
Should this have changed in 3.6 I couldn't see anything in the change log? How can I control where they are generated? On Fri, 15 Jul 2016, 18:51 David Callu <ledocc@gmail.com> wrote: > Hi Tom, > > Same thing on my side. I call in my code functions defined in generated > .cpp from moc/rcc. > Functions name are based on file path used during .cpp generation. > And this path change from cmake 3.5 to 3.6. > > You should check functions in generated .cpp files that you used in your > code. > > HTH > David > > 2016-07-15 1:54 GMT+02:00 Tom Kulaga <tommy8...@gmail.com>: > >> Hi All, >> >> I'm using 3.5.2 for a qt based project and I've updated to 3.6 and the >> RCC feature seems to fail. Here's a summary >> >> CMAKE settings: >> >> cmake_policy(SET CMP0015 NEW) # relative linker paths >> >> cmake_policy(SET CMP0020 NEW) # linking to qmainlib >> >> >> # Tell CMake to run moc when necessary: >> >> set(CMAKE_AUTOMOC ON) >> >> set(CMAKE_AUTOUIC ON) >> >> set(CMAKE_AUTORCC ON) >> >> # As moc files are generated in the binary dir, tell CMake >> >> # to always look for includes there: >> >> set(CMAKE_INCLUDE_CURRENT_DIR ON) >> >> >> When I swtiched to 3.6, the compiler can no longer link to the generated rcc >> files. >> >> >> Anyone else face this or know what I'm doing wrong? >> >> >> -- >> >> 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 >> > > -- > > 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 -- 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] cmake 3.5 vs 3.6 + qt
Hi All, I'm using 3.5.2 for a qt based project and I've updated to 3.6 and the RCC feature seems to fail. Here's a summary CMAKE settings: cmake_policy(SET CMP0015 NEW) # relative linker paths cmake_policy(SET CMP0020 NEW) # linking to qmainlib # Tell CMake to run moc when necessary: set(CMAKE_AUTOMOC ON) set(CMAKE_AUTOUIC ON) set(CMAKE_AUTORCC ON) # As moc files are generated in the binary dir, tell CMake # to always look for includes there: set(CMAKE_INCLUDE_CURRENT_DIR ON) When I swtiched to 3.6, the compiler can no longer link to the generated rcc files. Anyone else face this or know what I'm doing wrong? -- 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
