hey,
why am I suddently getting 98 c4996 errors?
I know I can add _CRT_SECURE_NO_WARNINGS flag but can someone explain why this happens?
because I built my project before succesfully multiple times
mtk
c4996 errors (warnings)
c4996 errors (warnings)
Windows 10
Visual Studio (Visual C++)
Visual Studio (Visual C++)
Re: c4996 errors (warnings)
any of these imports are creating an error:
Code: Select all
#include <wx/artprov.h>
#include <wx/xrc/xmlres.h>
#include <wx/dataview.h>
#include <wx/gdicmn.h>
#include <wx/font.h>
#include <wx/colour.h>
#include <wx/settings.h>
#include <wx/string.h>
#include <wx/bitmap.h>
#include <wx/image.h>
#include <wx/icon.h>
#include <wx/button.h>
#include <wx/gbsizer.h>
#include <wx/frame.h>
Windows 10
Visual Studio (Visual C++)
Visual Studio (Visual C++)
Re: c4996 errors (warnings)
Something must have changed if you didn't get the warnings before.
Just to clarify: These warnings are all about CRT functions,right?
Just to clarify: These warnings are all about CRT functions,right?
Use the source, Luke!
Re: c4996 errors (warnings)
I think I changed the ui a little using wxFormBuilder before it started happening.
Debug build x86 : 49 CRT function warnings
Debug build x64 : 49 CRT function warnings and 1 error saying:
Code: Select all
__w64 can only be specified on int, long, and pointer types C:\wxWidgets-3.1.5\include\wx\types.h
When I remove inherit and remove import, build succeeds without warnings.
Do you need the error list?
Windows 10
Visual Studio (Visual C++)
Visual Studio (Visual C++)
Re: c4996 errors (warnings)
The warnings will always be there when an "unsafe" function is referenced. Just suppress the warnings in your project settings and be done with it.
IIRC, the __w64 "error" is not a build error but rather an IntelliSense one, its cause has been removed from the master just recently.
IIRC, the __w64 "error" is not a build error but rather an IntelliSense one, its cause has been removed from the master just recently.
Re: c4996 errors (warnings)
okay, thanks. I was asking because you shouldn't want "unsafe" things in your release.PB wrote: ↑Mon Aug 30, 2021 7:56 am The warnings will always be there when an "unsafe" function is referenced. Just suppress the warnings in your project settings and be done with it.
IIRC, the __w64 "error" is not a build error but rather an IntelliSense one, its cause has been removed from the master just recently.
Windows 10
Visual Studio (Visual C++)
Visual Studio (Visual C++)