cmake_minimum_required(VERSION 3.0)
project(helloworld LANGUAGES C)
project(nghttp2 VERSION 1.50.0)
add_executable(helloworld main.c)
install(TARGETS helloworld RUNTIME DESTINATION bin)
BTW: not sure why you need the project(nghttp2 VERSION 1.50.0) line in your CMakeLists.txt file
You are correct! That statement makes no difference to the error message. I was simply trying out a suggested resolution from the GitHub nghttp2 repository but presumably it had nothing to do with my error message.
I must have libnghttp2 installed owing to the following output:
So now it’s my turn to ask a stupid question: what does the -G Ninja directive do? In my system (KDE Neon) it seems like cmake is failing with that directive (in a different way than yours), however running the following
I don’t believe this error is related to your CMake project at all. It seems that your cmake executable is using libcurl for some functionality internally, so it loads libcurl’s shared object, but on your distro the shared object can’t be loaded. So the whole thing crashes before it even executes much code to begin with.
It looks like your libcurl was built (presumably by your distro) against a version of nghttp2 that provided the nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation function. But now the nghttp2 library was swapped out for a version that does not provide this function, so libcurl won’t load. Presumably this would break a lot more software on your system than just CMake.
Now, given that your CMakeLists.txt contains some sort of reference to nghttp2, I have to ask: did you install a different version of nghttp2 that replaced the original one by your distro?
All I want to do is to build a Hello World project (in C/C++). I did not create the original source file, main.c, nor the CMakeLists.txt file. These were generated by the “wizard” while I attempted to create my first project.
If nghttp2 is broken in my platform (owing to my self-inflicted ignorance), how do I recover? Same request for help with libcurl. I don’t use these libraries explicitly, so the libraries got messed up during the installation of some package. Simply re-install? I need KDevelop to work and can sort out issues with other packages (e.g. Kdenlive) if anything outside of KDevelop breaks.
How do I put Humpty Dumpty back together again? Thanks.
Ninja is a build system that I avoid. I didn’t explicitly enter the command to include it. I am surprised that it shows up.
I can run make for my example without issues for this trivial example. Your example will work, undoubtedly. Let me try ccmake and step through the other parameters, if any. Thanks.
I fail to understand why I can use cmake & make from the command line and successfully build the program yet when I use the KDevelop IDE to do something similar, extraneous parameters are being applied.
Are you aware of any edit that I can perform to remove the superfluous parameters? Thanks.
Regards.
P.S.
I reinstalled libcurl-dev and nghttp2 but that didn’t resolve the issue.
Thanks, @jsalatas! I will try another platform with a clean slate. It would be an arm64 environment rather than the amd64 which is my primary dev environment.
Ok, I think I know a root cause.
The issue is related the only to a SNAP package.
When you are running a cmake command from the command line you are using you OS/system environment and set of libs. But when snapped KDevelop does that it runs command from isolated environment. Thus, I think libnghttp2-14 is not a part of the snap package vfs, and thus cmake is not able to find this lib.
I still don’t understand how to configure (or rather override) the automatic inclusion of the directive for a specific build package (either Ninja or CMake) in my original installation of KDevelop. The default was Ninja (how & where beats me) but using a documented environment variable I could change it to CMake. And as you perhaps rightly pointed out, the snap environment conflict persisted.
My workaround was to uninstall KDevelop and use the AppImage version. In this mode neither Ninja nor CMake are explicitly invoked and the build proceeds successfully. Of course, in this mode, updates to KDevelop are manual, but that is the least of my worries since I have a lot to learn with whatever is working.
I need a crash course on KDevelop. Any suggestions, please?
KDevelop will build my simple OpenCV (read and display) test, but upon launching the executable, there is no display window for the test image. Yet, running the same executable from the command line, works perfectly as expected (i.e. display window pops up).
So the build system is being selected upon importing/creating of the project. IF you selected a file (to import) CMakeLists.txt than build system would be CMake.
The other thing is generator which cmake uses to produce actual build rules, and by default it is makefiles (you can change that either by specifying extra command line options or via kdev project file)
