workaround for building with express toolchain on windows
intsafe.h and stdint.h both define INT8_MIN et al. with no guards, and so can't both be included. Because dependencies do this deep in their internals, avoid this problem by including intsafe.h, and then #undef'ing the conflicts in precompile.h (which is included in all .cc files). intsafe.h's include guard symbol stays defined so that any subsequent inclusions do not cause problems. R=thestig@chromium.org BUG=225822 Review URL: https://chromiumcodereview.appspot.com/13484002 git-svn-id: http://src.chromium.org/svn/trunk/src/build@192341 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This commit is contained in:
Родитель
ce5ef5afb0
Коммит
59703c396f
19
precompile.h
19
precompile.h
|
@ -106,3 +106,22 @@
|
|||
#include <string>
|
||||
#include <utility>
|
||||
#include <vector>
|
||||
|
||||
// Workaround for:
|
||||
// http://connect.microsoft.com/VisualStudio/feedback/details/621653/
|
||||
// http://crbug.com/225822
|
||||
// Note that we can't actually include <stdint.h> here because there's other
|
||||
// code in third_party that has partial versions of stdint types that conflict.
|
||||
#include <intsafe.h>
|
||||
#undef INT8_MIN
|
||||
#undef INT16_MIN
|
||||
#undef INT32_MIN
|
||||
#undef INT64_MIN
|
||||
#undef INT8_MAX
|
||||
#undef UINT8_MAX
|
||||
#undef INT16_MAX
|
||||
#undef UINT16_MAX
|
||||
#undef INT32_MAX
|
||||
#undef UINT32_MAX
|
||||
#undef INT64_MAX
|
||||
#undef UINT64_MAX
|
||||
|
|
Загрузка…
Ссылка в новой задаче