[GLUTEN-11287][VL] Use IWYU tool to check code format#11287
[GLUTEN-11287][VL] Use IWYU tool to check code format#11287xinghuayu007 wants to merge 1 commit into
Conversation
d4c97f3 to
6e2680a
Compare
a51b2eb to
4ac46bc
Compare
1884480 to
ba200ee
Compare
bbef1fc to
6aaab1a
Compare
philo-he
left a comment
There was a problem hiding this comment.
Can we enable IWYU in a way embed in cmake? We can enable the check only when code changes are made under cpp/ path.
if(ENABLE_IWYU)
find_program(IWYU_PATH NAMES include-what-you-use iwyu)
if(IWYU_PATH)
set(CMAKE_CXX_INCLUDE_WHAT_YOU_USE ${IWYU_PATH})
endif()
endif()
Compiling include-what-you-use needs clang and source code. Currently design can ensure only check modified cpp files. |
philo-he
left a comment
There was a problem hiding this comment.
Thanks for the update. The current implementation looks a bit complex to me. Do you know how IWYU is enabled in Velox?
| @@ -237,7 +242,13 @@ function build_gluten_cpp { | |||
| rm -rf build | |||
| mkdir build | |||
| cd build | |||
|
|
|||
| if [ $USE_CLANG = "ON" ]; then | |||
There was a problem hiding this comment.
Seems no need to add a new build option. Just let the compilation depend on the setting for CC and CXX in the env.
There was a problem hiding this comment.
To separate the builds, we can run ./dev/builddeps-veloxbe.sh build_velox xxx with gcc to utilize vcpkg cache in docker. Then, run ./dev/builddeps-veloxbe.sh build_gluten_cpp with clang to build Gluten c++ code.
|
Errors reported by CI. |
Thanks. Done. |
|
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
|
This PR was auto-closed because it has been stalled for 10 days with no activity. Please feel free to reopen if it is still valid. Thanks. |
What changes are proposed in this pull request?
Use IWYU tool to check code format
How was this patch tested?
Related issue: #11287