-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vcpkg include directories incorrect #75
Comments
Hi! Do you use CMake? With CMake, you get correct include paths. Sample standalone project: CMakeLists.txt
sail-probe.cpp
Compilation
Running
|
Please re-open in case of any issues. |
I am still having this issue and am trying not to use CMake, has this been fixed for Visual Studio 2022?
It is the same wether I use x86, x64 or x64-static. |
@AlexMollard Do you use the MSVS vcpkg integration? |
Yeah, I am currently using a few other libraries without issue. |
As a temporary workaround, try adding |
Tried your suggestion but still am having trouble, All files are being linked now but can't seem to figure out why
Also just tried in CMake with the same error this is my current CMake:
|
Oh, I see. I didn't notice this error before as I use universal sail headers. I think you can try the following potential fixes:
|
There may be more errors like take. I've just pushed several fixes. Until the fixes reach vcpkg, using universal includes is recommended. For C++: |
SAIL-RC2 with the missing includes fix has been merged into vcpkg. Please update the local copy of vcpkg and install rc2. Adding VcpkgInstalledDir/include/sail to the project include path is still required if you don't use cmake. |
It seems that when installing using vcpkg, the headers expect that the include root is in the
sail
directory, but vcpkg places the includes undersail
. To include something in your own project, you needbut the sail headers includes other sail headers as
Am I missing something here? Was this project updated since it was set up for vcpkg that caused this?
The text was updated successfully, but these errors were encountered: