![]() ![]() If you run which cmake you are going to see /snap/bin/cmake which is a link to /usr/bin/snap. ![]() build-wrapper is using dynamic library concept to observe created processes, in this case it is not able to follow snap children because snap statically link exec* family calls. The reason is because of snap, you are invoking a cmake which has been installed through. ninjaĪnd I have been surprised : It works and my pipeline finishes without any issues.īUT I will still need to infer the CMake Generator at one point, so my question : does some one already encounter a similar case and found what was the problem with the cmake -build. So, I tried not infering the Generator with the following command build-wrapper-linux-x86-64 -out-dir. I was hoping to be able to infer the underlying CMake Generator (as seen on this answer ), but instead I was blocked by the following error : : The “build-wrapper-dump.json” file was found empty. In my pipeline, I was using the following command to build my project and satisfy Sonar’s needs : build-wrapper-linux-x86-64 -out-dir. sonar-scanner (version 4., downloaded automatically by Azure DevOps’ SonarCloudAnalyse task).build-wrapper-linux-x86_64 (version 6.23, installed locally and set in the Azure Agent’s PATH variable).OS : Ubuntu Server 18.04 LTS (custom builder host for Azure DevOps).I stumbled recently on an issue related to the build-wrapper usage, but first, here are few technical information as context :
0 Comments
Leave a Reply. |