westonpace commented on issue #139: URL: https://github.com/apache/arrow-cookbook/issues/139#issuecomment-1030413501
I resolved `UseAsync` so that error should go away. The googletest errors I can reproduce if I use googletest 1.10 instead of 1.11. The googletest dependency is defined here: https://github.com/apache/arrow-cookbook/blob/main/cpp/code/CMakeLists.txt#L9-L18 I also noticed that your log files show it is using include headers from a conda build of googletest: `/home/antoine/miniconda3/envs/pyarrow/include/gtest/gtest.h` I'm not sure if the call `include(GoogleTest)` is somehow finding the conda googletest instead of the one we just built or if the include path is getting specified in the wrong order. I suspect it is the latter. I do notice on my system that the compile command is: ``` /home/pace/miniconda3/envs/conbench3/bin/cmake -E __run_co_compile --tidy="clang-tidy-12;--extra-arg-before=--driver-mode=g++" --source=/home/pace/dev/arrow-cookbook/cpp/code/datasets.cc -- /usr/bin/clang++-12 -isystem /home/pace/dev/arrow-cookbook/cpp/code/conbench-build/_deps/googletest-src/googletest/include -isystem /home/pace/dev/arrow-cookbook/cpp/code/conbench-build/_deps/googletest-src/googletest -fvisibility-inlines-hidden -std=c++17 -fmessage-length=0 -march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-strong -fno-plt -O2 -ffunction-sections -pipe -isystem /home/pace/miniconda3/envs/conbench3/include -stdlib=libstdc++ -g -Wall -Wextra -Wpedantic -Werror -std=gnu++17 -MD -MT CMakeFiles/datasets.dir/datasets.cc.o -MF CMakeFiles/datasets.dir/datasets.cc.o.d -o CMakeFiles/datasets.dir/datasets.cc.o -c /home/pace/dev/arrow-cookbook/cpp/code/datasets.cc ``` This adds the include path `/home/pace/miniconda3/envs/conbench3/include` at the end of the includes list (after the include for google test) which would explain your behavior. I can't figure out where in CMakeLists.txt it is specifying that. Do you have any idea? If not I can keep messing around with cmake. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
