I’m talking about syntax highlighting.
When a library, function, or something like that is used, you can tell by the color.
That’s why I noticed that this one isn’t being recognized.
For comparison, when I want to use the Boost library, it’s immediately highlighted in color.
So I must have made a mistake during installation, or I need to manually add the library to KDevelop. I just don’t know how to fix it right now, which is why I’m asking.
I hope I’ve made myself clear.
Regarding development: No, I just want to use the library for programming. I’m not developing it myself.
Incidentally I also have an experiment using Wt. So I’ll share how I set up my dev env:
in ~/projects/install I create a complete separate hierarchy (let make install create it).
IOW: the installation path is set to ~/projects/install. This is achieved in the configure stage of Wt : $ cmake ../ -DCMAKE_INSTALL_PREFIX=~/projects/install
Then make install installs it into that directory. This has the advantage of never polluting the system, every single file outside of /home being managed by the package manager.
Most linux distros install into /usr, so you’d have to pass -DCMAKE_INSTALL_PREFIX=/usr for it to be picked up automatically.
I set up my project using cmake, searching for Wt using find_package(wt REQUIRED)
Then in KDevelop’s project configuration I set the CMAKE_PREFIX_PATHenvironment variable to ~/projects/install, that way CMake will also search my hierarchy for dependencies. Attached screenshot to hopefully help you out.
I’ve both reloaded the project and re-imported it completely.
But to no avail.
This is starting to get really strange.
As I said, I got the Boost libraries from the package repositories, and they work.
I just installed curlpp (a C++ wrapper—curl is also installed) from the package repositories as well.
That doesn’t work either.
I really don’t understand this right now.
The only thing I can think of is a permission issue with the Flathub version of KDevelop or a problem directly within KDevelop.
I’ve run some more tests and can confirm that it doesn’t work with the version installed via snap or the older one directly from the Debian package repositories either.
I also added a profile to the environment variables in the options and set CMAKE_PREFIX_PATH to
/usr/
But that didn’t work either.
Do you see any errors bvy me?
Or should I open a bug ticket? If so, do you have a link?