openh264/test/build
Martin Storsjö ef82e18d74 Silence warnings about insecure CRT functions in the test suite
There is no problem in using the "insecure" CRT functions, as long as
they are used correctly - especially not within the test suite where
they are only are exposed to the test suite input data.

Within the library, these are used via the library internal wrappers
in codec/common/src/crt_util_safe_x.cpp, but we'd rather not use them
in the test suite - just use the normal standard C functions here.
2015-01-16 13:38:06 +02:00
..
android checking the scripits for unittest automatically on mobile 2014-07-25 14:05:36 +08:00
ios/codec_unittest checking the scripits for unittest automatically on mobile 2014-07-25 14:05:36 +08:00
win32/codec_ut Silence warnings about insecure CRT functions in the test suite 2015-01-16 13:38:06 +02:00