search for: _crt_nonstdc_no_deprecate

...52 All the errors are reported in LLVM header files, mostly llvm/Support/COFF.h and llvm/Object/COFF.h I'm using Visual Studio Community 2015, the CXX compiler identification is MSVC 19.0.23026.0 My CPP includes are: WIN32 _WINDOWS NDEBUG _CRT_SECURE_NO_DEPRECATE _CRT_SECURE_NO_WARNINGS _CRT_NONSTDC_NO_DEPRECATE _CRT_NONSTDC_NO_WARNINGS _SCL_SECURE_NO_DEPRECATE _SCL_SECURE_NO_WARNINGS __STDC_CONSTANT_MACROS __STDC_FORMAT_MACROS __STDC_LIMIT_MACROS _GNU_SOURCE %(PreprocessorDefinitions) Now, a couple of things are suspicious: - in googling around it seems like there are some problems with including Windo...

..., Óscar Fuentes <ofv at wanadoo.es> wrote: > /* snip */ Thanks so much for that information. :) For note, this is my usual line I add to the end of my preprocessor definitions in *every* single project I ever open now (thanks to some very bad memories associated with not having them). ;_CRT_NONSTDC_NO_DEPRECATE;_CRT_SECURE_NO_DEPRECATE;_SECURE_SCL=0;_SCL_SECURE_NO_DEPRECATE;_HAS_ITERATOR_DEBUGGING=0 Most of those will be obvious, but as stated, both _SECURE_SCL and _HAS_ITERATOR_DEBUGGING (especially this last one, you can 'sometimes' get by with linking on just _SECURE_SCL, but not with _HAS_ITE...

"Cory Nelson" <phrosty at gmail.com> writes: > On Mon, Nov 24, 2008 at 8:18 PM, Óscar Fuentes <ofv at wanadoo.es> wrote: >> OvermindDL1 <overminddl1 at gmail.com> writes: >>> As long as instructions are supplied on how to pass in user defined >>> macros to the build system. I have to turn off a lot of the extra >>> safety crap that

Hi all, I am Sahana. I am currently working on Libtheora for windows platform and very new to it. I am getting a lot of compiling errors. Since Libtheora depends on libogg and libvorbis i have added these as well to my workspace in VC++ 6. I have a doubt regarding the x86 and x86_vc folders described in the libtheora software.Since both these folders have the same set of files which one do we