Replies: 1 comment 14 replies
-
|
quickcpplib and outcome are header only libraries. It would be useful if you did post the unresolved externals. Usually it is due to using a different C++ standard in the final binary than was used to build the libraries. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, Niall. And thank you for the fix on the Linux side. Ironically, we only discovered that due to having to work on the Linux side due to my challenges in getting LLFIO integrated on the Windows side ;-) But mostly, I thank you for providing this library. It is exactly what we needed for our project. We are re-writing a database engine that has been Windows based for the past 30 years to run on Linux. We have 30 years of experience writing code with unbuffered i/o on Windows, but have been trying to re-engineer our software to run on both Windows and Linux. I had researched how to do the same things on Linux, and it's not that it's difficult, it's just that I would rather that our source code was cross-platform, and the platform specific implementation was done by someone else (competent). So thank you for being that person. Writing the code to deal with sparse files was so much easier with LLFIO. I am attempting to build from the develop branch, partly because I knew we'd be wanting the Linux sparse file fix. If you are saying that this build problem is known, and that I could switch to the 20240823 tag and expect success, I will start with that. |
Beta Was this translation helpful? Give feedback.
-
|
On Linux, 20240823 builds cleanly for me, but the develop branch does not. I get 2 errors reported like this: In file included from /home/tastewar/xp/llfio/src/../include/llfio/v2.0/file_handle.hpp:562, |
Beta Was this translation helpful? Give feedback.
-
|
On Windows, attempting to build 20240823 also fails. The "cmake .." step lists a FATAL error early, but carries on. Here is that error: -- Missing dependency quickcpplib is NOT installed in cmake packages! But then later on (after the FATAL error...), I get 3 unresolved externals from main.obj when building outcome. I believe this is the same as in the develop branch: main.obj : error LNK2019: unresolved external symbol main.obj : error LNK2019: unresolved external symbol main.obj : error LNK2019: unresolved external symbol C:\projects\llfio\build\outcome\repo\src\outcome-build\bin\Debug\outcome-link-test-experimental-c-result-type_SHARED-vis_default.exe |
Beta Was this translation helpful? Give feedback.
-
|
Both the Linux build and Windows builds should now be fixed. Thanks for your patience. I'm not allowed merge to master branch until the Boost release happens next month. Until then, anything fetching master branch under the bonnet will continue to fail. Once Boost releases, I generally do a github release of everything here. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. I can build both Windows and Linux now locally. Still struggling with linking everything into a single Windows exe, but still plugging away at it. Linux links just fine. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
When building a project that incorporates llfio on Windows, I have the project setup to link against the import libraries that were included, llfio and ntkernel-error-category, but when I attempt to build, during the link phase I get 2 unresolved externals. The names are well decorated, so I won't paste them here, but one appears to be from quickcpplib and the other from outcome. I don't see either import libraries or dlls for these in the llfio pre-built download, and I don't see them available in their root projects either.
Beta Was this translation helpful? Give feedback.
All reactions