3 Commits

Author	SHA1	Message	Date
Mark Mentovai	98cca0e5fc	compat/mac: 10.6 SDK compatibility for pre-Xcode 4.2 10.6 SDK. ... Some definitions were added to the 10.6 SDK during its lifetime, and aren’t present in older versions of the SDK. The AVX definitions are in this group. Apparently, not all of Chrome’s builders use the same version of this SDK. A try bot failure was encountered for https://codereview.chromium.org/1011503002/ in http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_compile_dbg_ng/builds/33868/steps/compile%20%28with%20patch%29/logs/stdio. This provides definitions in compat for when they aren’t available from the SDK. TEST=compile R=rsesek@chromium.org Review URL: https://codereview.chromium.org/1001733003	2015-03-16 13:41:48 -04:00
Mark Mentovai	850ec0657d	Drop 10.5 support. ... TEST=util_test R=rsesek@chromium.org Review URL: https://codereview.chromium.org/575823002	2014-09-16 11:55:55 -04:00
Mark Mentovai	dfe81014f7	Add compat to Crashpad. ... compat includes headers providing definitions normally provided by the system, in cases where the system SDK does not always provide the correct or up-to-date definitions, and cases where code on different platforms needs to access definitions normally only available on one platform. To provide definitions on a single platform, where the system SDK may not provide the definitions correctly, use subdirectories named for the platform, such as “mac”. To provide definitions normally available on only one platform to others, use subdirectories that identify that they are to be used on platforms other than the one that originated their definitions, such as “non_win”. In all cases, headers should be named as they are natively in their respective SDKs, so that it’s possible to #include them according to their usual names. R=rsesek@chromium.org Review URL: https://codereview.chromium.org/432843002	2014-07-31 13:45:51 -04:00