You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am learning Nanogui use. I made a local version of Example #1, as example11.cpp with calls to SQLite3 (in development) and can easily compile the code without modifications on Win10 and Linux 64 bit, and run the executable in a graphical environment. What I would like to learn is why does MS Visual Studio 2019 complain as shown below, when I review the code block (in x64-Debug mode, and in Linux-GCC-Debug mode), where it says concerning several invocations of "std::cerr", or stderr - yet the program compiles in both environments with vcpkg + Cmake and runs well. So, is this fully normal, or do we need to have a #ifdef ... #endif block to define a gnu-C++ specific c++ function call?
Hi, I am learning Nanogui use. I made a local version of Example #1, as example11.cpp with calls to SQLite3 (in development) and can easily compile the code without modifications on Win10 and Linux 64 bit, and run the executable in a graphical environment. What I would like to learn is why does MS Visual Studio 2019 complain as shown below, when I review the code block (in x64-Debug mode, and in Linux-GCC-Debug mode), where it says concerning several invocations of "std::cerr", or stderr - yet the program compiles in both environments with vcpkg + Cmake and runs well. So, is this fully normal, or do we need to have a #ifdef ... #endif block to define a gnu-C++ specific c++ function call?
namespace "std" has no member "cerr"
and this is related to the code snippet:
thanks
The text was updated successfully, but these errors were encountered: