Re: [cmake-developers] toolset Clang 3.7 with Microsoft CodeGen (v140_clang_3_7) debug is broken
On 08/12/2016 08:59 AM, Forumer 4umer wrote: > I have tested cmake 3.6.1 with the last release of the clang platform by > Microsoft (v140_clang_c2) and nothing has changed. No one is actively working on support for Clang toolsets currently. The experimental support in 3.6 was contributed but no one has maintained it. There is an issue covering the main problem: https://gitlab.kitware.com/cmake/cmake/issues/16153 Discussion there has links to some of the other problems. -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] toolset Clang 3.7 with Microsoft CodeGen (v140_clang_3_7) debug is broken
Le 2016-05-02 20:48, foru...@.com a écrit : Le 2016-05-02 20:41, Brad King a écrit : On 05/02/2016 02:17 PM, foru...@x.com wrote: Don't know if it's the best place to report it but I am testing nightly builds(3.5.20160429) to generate some projects for Visual Studio 2015 and the clang toolset now provided by Microsoft. Yes, this is the right place to report it, especially since this is recent development. For reference, support for this toolset was added in a topic merged here: Merge topic 'vs-clang-cl' https://cmake.org/gitweb?p=cmake.git;a=commit;h=612a8b3b based on discussion in this thread: [PATCH SET] Support of Clang/C2 compiler. http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/15902 I have found some changes that seems to be necessary to be able to debug, here are the changes I have found: 1) DebugInformationFormat should be set FullDebug, AdditionalOptions MUST BE removed and optimizations must be disabled ... REMOVE AdditionalOptions ... FullDebug ... Disabled false 2)GenerateDebugInformation must be set to true and ProgramDataBaseFile must be empty because clang doesn't use pdb for now ... true ... Mariusz, please take a look at this. See also this hack: VS: Fix VS 2015 .vcxproj debug setting for older toolsets https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=dc422d27 Basically we need to have a different flag table for each possible toolset. Also it looks like additional special handling may be needed for PDBs and perhaps other limitations of the Clang/C2 toolchain. Thanks, -Brad Just a small update about what I wrote regarding AdditionalOptions, I found that it's not necessary to remove the whole line but only the -gline-tables-only parameter. Hi, I have tested cmake 3.6.1 with the last release of the clang platform by Microsoft (v140_clang_c2) and nothing has changed. By default cmake generates wrong projects with this toolset. So could we fix it step by step: In the next release of cmake could you please remove the -gline-tables-only (and maybe all the additional arguments you provide because Microsoft don't add them when using Visual to generate projects) Then if you have time please Disable Optimizations in Debug and finally please set DebugInformationFormat for debug configurations. For now I have to manually fix all my projects everytime I regenerate them and it's not very funny. Thanks -- 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] toolset Clang 3.7 with Microsoft CodeGen (v140_clang_3_7) debug is broken
Le 2016-05-02 20:41, Brad King a écrit : On 05/02/2016 02:17 PM, foru...@smartmobili.com wrote: Don't know if it's the best place to report it but I am testing nightly builds(3.5.20160429) to generate some projects for Visual Studio 2015 and the clang toolset now provided by Microsoft. Yes, this is the right place to report it, especially since this is recent development. For reference, support for this toolset was added in a topic merged here: Merge topic 'vs-clang-cl' https://cmake.org/gitweb?p=cmake.git;a=commit;h=612a8b3b based on discussion in this thread: [PATCH SET] Support of Clang/C2 compiler. http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/15902 I have found some changes that seems to be necessary to be able to debug, here are the changes I have found: 1) DebugInformationFormat should be set FullDebug, AdditionalOptions MUST BE removed and optimizations must be disabled ... REMOVE AdditionalOptions ... FullDebug ... Disabled false 2)GenerateDebugInformation must be set to true and ProgramDataBaseFile must be empty because clang doesn't use pdb for now ... true ... Mariusz, please take a look at this. See also this hack: VS: Fix VS 2015 .vcxproj debug setting for older toolsets https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=dc422d27 Basically we need to have a different flag table for each possible toolset. Also it looks like additional special handling may be needed for PDBs and perhaps other limitations of the Clang/C2 toolchain. Thanks, -Brad Just a small update about what I wrote regarding AdditionalOptions, I found that it's not necessary to remove the whole line but only the -gline-tables-only parameter. -- 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] toolset Clang 3.7 with Microsoft CodeGen (v140_clang_3_7) debug is broken
On 05/02/2016 02:17 PM, foru...@smartmobili.com wrote: > Don't know if it's the best place to report it but I am testing nightly > builds(3.5.20160429) to generate some projects > for Visual Studio 2015 and the clang toolset now provided by Microsoft. Yes, this is the right place to report it, especially since this is recent development. For reference, support for this toolset was added in a topic merged here: Merge topic 'vs-clang-cl' https://cmake.org/gitweb?p=cmake.git;a=commit;h=612a8b3b based on discussion in this thread: [PATCH SET] Support of Clang/C2 compiler. http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/15902 > I have found some changes that seems to be necessary to be able to > debug, here are the changes I have found: > > 1) DebugInformationFormat should be set FullDebug, AdditionalOptions > MUST BE removed and optimizations must be disabled > > > ... REMOVE AdditionalOptions ... > FullDebug > ... > Disabled > false > > > > 2)GenerateDebugInformation must be set to true and ProgramDataBaseFile > must be empty because clang doesn't use pdb for now > > ... >true > ... > > > > Mariusz, please take a look at this. See also this hack: VS: Fix VS 2015 .vcxproj debug setting for older toolsets https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=dc422d27 Basically we need to have a different flag table for each possible toolset. Also it looks like additional special handling may be needed for PDBs and perhaps other limitations of the Clang/C2 toolchain. 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