Sebastian Messmer 6706e9af19 Make C10_MOBILE consistent with how feature macros are usually used (#17481) ... Summary: Pull Request resolved: https://github.com/pytorch/pytorch/pull/17481 Usually, feature macros are either defined or undefined and checked accordingly. C10_MOBILE was a weird special case that was always defined but either defined to 1 or to 0. This caused a lot of confusion for me when trying to disable something from mobile build and it also disabled it from the server build (because I was using ifdef). Also, I found a place in the existing code base that made that wrong assumption and used the macro wrongly, see https://fburl.com/y4icohts Reviewed By: dzhulgakov Differential Revision: D14214825 fbshipit-source-id: f3a155b6d43d334e8839e2b2e3c40ed2c773eab6		2019-02-27 17:57:51 -08:00
..
detectron	Update the cmake build configuration for AppleClang compiler (#15820)	2019-02-04 08:53:47 -08:00
module_test	Generate PDB files for better debugging on Windows (#16008)	2019-01-16 23:34:32 -08:00
observers	Make C10_MOBILE consistent with how feature macros are usually used (#17481)	2019-02-27 17:57:51 -08:00
rocksdb	Using c10 namespace across caffe2. (#12714)	2018-10-17 12:57:19 -07:00
CMakeLists.txt	Windows shared build (#13550)	2018-11-16 12:16:28 -08:00