Replies: 2 comments
-
It looks like a bug in |
Beta Was this translation helpful? Give feedback.
-
Thanks, this all makes sense now. I've opened an issue on that project, but the author recently stated that they're no longer actively maintaining the project, so who knows if/when it might get addressed: machinezone/IXWebSocket#504 |
Beta Was this translation helpful? Give feedback.
-
I'm writing an application with vcpkg + cmake that depends on vcpkg's ixwebsocket package, using vcpkg manifest mode and cmake preset mode.
For some reason, if I only link
ixwebsocket::ixwebsocket
, cmake builds with-isystem .../include/ixwebsocket
, but if I also link against additional vcpkg dependencies (e.g.nlohmann_json::nlohmann_json
) it also adds in-isystem .../include
.Since my code uses
#include <ixwebsocket/xyz.h>
, it breaks depending on how many libraries I'm linking.Is this really how it's all supposed to work? Am I really supposed to use
#include <xyz.h>
instead of#include <ixwebsocket/xyz.h>
to make it work in all situations?It there something in vcpkg or cmake that I can set to tweak this behavior?
Edit: Also note that this behavior contradicts the example here, which says to use
#include <fmt/core.h>
: https://learn.microsoft.com/en-us/vcpkg/get_started/get-started?pivots=shell-cmd#3---add-dependencies-and-project-filesEdit 2: This may be a non-terrible workaround?
Beta Was this translation helpful? Give feedback.
All reactions