Uncrustify_vendor build failed on Windows 10 -ros2 Galactic version
I followed the exact steps trying to debug build ros2 galactic, and it failed with this error
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.29.30037/bin/Hostx64/x64/cl.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.29.30037/bin/Hostx64/x64/cl.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found ament_cmake: 1.1.4 (D:/MyGit/ros2-debug-build/ros2_galactic/install/share/ament_cmake/cmake)
-- Found PythonInterp: C:/Python38/python.exe (found suitable version "3.8.3", minimum required is "3")
-- Using PYTHON_EXECUTABLE: C:/Python38/python.exe
-- Configuring done
-- Generating done
-- Build files have been written to: D:/MyGit/ros2-debug-build/ros2_galactic/build/uncrustify_vendor
Microsoft (R) Build Engine version 16.10.2+857e5a733 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.
Checking Build System
Creating directories for 'uncrustify-45b836cff040594994d364ad6fd3f04adc890a26'
Performing download step (git clone) for 'uncrustify-45b836cff040594994d364ad6fd3f04adc890a26'
Cloning into 'uncrustify-45b836cff040594994d364ad6fd3f04adc890a26'...
HEAD is now at 45b836cf Merge pull request #2308 from emersonknapp/md5-armhf
No update step for 'uncrustify-45b836cff040594994d364ad6fd3f04adc890a26'
Performing patch step for 'uncrustify-45b836cff040594994d364ad6fd3f04adc890a26'
Performing configure step for 'uncrustify-45b836cff040594994d364ad6fd3f04adc890a26'
-- Selecting Windows SDK version 10.0.18362.0 to target Windows 10.0.18363.
-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
CMake Error at CMakeLists.txt:3 (project):
No CMAKE_C_COMPILER could be found.
I have vs2019 good installed, my cmake is definitely good, i can build other cmake projects. I believe is a bug in the galactic repos, but i am not sure. any one has such error?
My build command:
python_d c:\Python38\Scripts\colcon.exe build --merge-install --cmake-args -DCMAKE_BUILD_TYPE=Debug
console output:
---
Finished <<< tinyxml_vendor [46.6s]
Starting >>> ament_cmake_flake8
Failed <<< uncrustify_vendor [1min 24s, exited with code 1]
Aborted <<< ament_cmake_cpplint [27.4s]
Aborted <<< ament_cmake_flake8 [12.1s]
Aborted <<< foonathan_memory_vendor [43.5s]
Aborted <<< shared_queues_vendor [1min 9s]
Aborted <<< iceoryx_posh [2min 1s]
Aborted <<< yaml_cpp_vendor [1min 29s]
Aborted <<< sqlite3_vendor [1min 28s]
Summary: 50 packages finished [3min 47s]
1 package failed: uncrustify_vendor
7 packages aborted: ament_cmake_cpplint ament_cmake_flake8 foonathan_memory_vendor iceoryx_posh shared_queues_vendor sqlite3_vendor yaml_cpp_vendor
50 packages had stderr output: ament_cmake ament_cmake_copyright ament_cmake_core ament_cmake_cppcheck ament_cmake_export_definitions ament_cmake_export_dependencies ament_cmake_export_include_directories ament_cmake_export_interfaces ament_cmake_export_libraries ament_cmake_export_link_flags ament_cmake_export_targets ament_cmake_gmock ament_cmake_google_benchmark ament_cmake_gtest ament_cmake_include_directories ament_cmake_libraries ament_cmake_lint_cmake ament_cmake_pytest ament_cmake_python ament_cmake_target_dependencies ament_cmake_test ament_cmake_version ament_cmake_xmllint ament_copyright ament_cppcheck ament_cpplint ament_flake8 ament_index_python ament_lint ament_lint_auto ament_lint_cmake ament_mypy ament_package ament_pep257 ament_xmllint domain_coordinator gmock_vendor gtest_vendor iceoryx_posh iceoryx_utils launch launch_testing osrf_pycommon osrf_testing_tools_cpp rosidl_cli rpyutils shared_queues_vendor sqlite3_vendor tinyxml_vendor urdfdom_headers
272 packages not processed
Asked by pfnus on 2021-07-07 04:55:34 UTC
Comments
Hi~ I met the same problem Have you solved it ?
Asked by cshmilyc on 2021-11-02 06:18:42 UTC
wait, what was the errors log like in the failed package? I am not sure yours was due to cmake
Asked by pfnus on 2022-04-27 03:52:23 UTC