james94 commented on PR #1793: URL: https://github.com/apache/nifi-minifi-cpp/pull/1793#issuecomment-2156261471
@szaszm @martinzink with respect to commit **"[49de56c](https://github.com/apache/nifi-minifi-cpp/pull/1793/commits/49de56cd6a559a567e4df7e6037473f8eebd74f6)"**: I verified I can build MiNiFi C++ using conan with the specific conan profile `etc/conan/profiles/release-linux` and with the sources for MINIFI_LIBCURL_SOURCE, MINIFI_OPENSSL_SOURCE and MINIFI_ZLIB_SOURCE all set to CONAN successfully. There were 2 ENABLED options that I needed to set to OFF, which were ENABLE_LIBARCHIVE and ENABLE_AWS since the build would fail, but later I can get those working again since on my bigger PR-1775 "https://github.com/apache/nifi-minifi-cpp/pull/1775";, I was able to keep those options ENABLED when building MiNiFi C++ with conan. I used the following command to build MiNiFi C++ with conan: ~~~bash conan build . --build=missing --output-folder=build_conan -pr=etc/conan/profiles/release-linux ~~~ I did double check I can still build MiNiFi C++ using standalone CMake approach with all the default ENABLED options set to their original values as specified in MiNiFiOptions.cmake too. I used these commands to build MiNiFi C++ with cmake: ~~~bash mkdir build_cmake cd build_cmake cmake .. make -j $(nproc) ~~~ Please try the conan build MiNiFi C++ approach again when you get a chance -- 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]
