Thanks, yes, that's what I ultimately did. On Wed, Dec 3, 2025 at 12:14 PM Vidar Hasfjord vattila@users.sourceforge.net wrote: Description has changed: Diff: --- old+++ new@@ -1,13 +1,8 @@-I am migrating my codebase to C++20 via the -std:c++20 flag to MSVC. This gives the following compilation errors in OWLNext 7.0.19:+I am migrating my codebase to C++20 via the -std:c++20 flag to MSVC. This gives the following compilation error in OWLNext 7.0.19: -dib.cpp-..\roomedit\owl-7.0.19\source\owlcore\dib.cpp(343):...
C++20 compilation errors
Yes, I understand that I could reproduce the logic for generating the library filename and generating version.h, but that's duplication and complexity I don't want. KISS! And yes, I no longer need OWL_NO_AUTO_LINK. If it existed, I would use it, as it's simpler than listing a zillion extra libraries. On Sun, Sep 28, 2025 at 3:42 PM Vidar Hasfjord vattila@users.sourceforge.net wrote: @akirmse https://sourceforge.net/u/akirmse/profile/ wrote: urllink.cpp (removed?) Yes — or not quite. TUrlLink was...
Thanks, /NODEFAULTLIB did the trick. Unfortunately it doesn't take wildcards, so I had to disable all default libraries, which meant adding a ton of explicit libraries to the link line (C runtime, C++ runtime, etc.). But at least now I don't need to manually modify the OWL code (except for version.h, which I'd also like to avoid modifying if possible). On Sun, Sep 28, 2025 at 2:09 PM Vidar Hasfjord vattila@users.sourceforge.net wrote: @akirmse https://sourceforge.net/u/akirmse/profile/ wrote: For...
For system libraries, auto-link makes a lot of sense, as the files have well-known names and are pretty much guaranteed to be in the lib path already. But I'm obviously not a fan of auto-linking for generated files that may not exist. Here are the changes I needed to make when going from version 6 to 7: Manually edit version.h since I'm not using OWLMaker GetClassName -> GetWindowClassName, plus change the return type. Stop compiling urllink.cpp (removed?) Link with Windows comdlg32.lib (now that...
Hm, that could be pretty difficult. Since I'm building the libraries myself, I would have to reproduce the logic that constructs the name in owllink.h in my makefile, and I'd need to remember to update it every time I upgrade the library. Commenting out is certainly easier. Personally I find it hard to work with "magic" like #pragma comment(lib) as it's inflexible and hard to debug. I'd rather be explicit about where all my files are coming from. On Sat, Sep 27, 2025 at 1:54 PM Vidar Hasfjord vattila@users.sourceforge.net...
I've just moved our codebase from OWLNext 6.43 to 7.0.19 because we're migrating to C++17. We have our own (old) nmake-based build system and thus I didn't use OWLMaker. I had to disable the auto-linking of the OWL library in include\owl\private\owllink.h (by commenting out the #pragma) because my build system doesn't name the library in that very specific way. Might we get a compile-time symbol that would disable this auto-linking for cases like this? Something like -D OWL_NO__AUTO_LINK. I don't...
Sure, here's a screenshot and a blurb: https://shared.fastly.steamstatic.com/store_item_assets/steam/apps/893390/ss_97909315404912e3ed4e43c15a8f5b3b5f50295a.1920x1080.jpg?t=1705866175 Meridian 59 (https://meridian59.com) was the first 3D massively-multiplayer online game, launched in 1996. It won roleplaying game of the year, and in 2012 was released as open source. It continues to run for free today. The room editor was a forked version of WinDEU, an editor for the game Doom, built with OWL in Borland...