Since I updated Xcode to a later version (can't remember the exact one) I get a huge amount of warnings one at the bottom. Can we please fix this or suppress the warning. The amount of output this generates is ridiculously annoying.
2 warnings generated. [919/1174] Compile ‘Frameworks/buffer/src/symbols.cc’… In file included from Frameworks/buffer/src/symbols.cc:1: In file included from /Users/jacob/development/objective-c/textmate/Shared/PCH/prelude.cc:25: In file included from /Users/jacob/development/objective-c/textmate/build/include/sparsehash/dense_hash_map:104: In file included from /Users/jacob/development/objective-c/textmate/build/include/sparsehash/internal/densehashtable.h:100: /Users/jacob/development/objective-c/textmate/build/include/sparsehash/internal/hashtable-common.h:167:29: warning: unused typedef 'serializing_int_requires_an_unsigned_type' [-Wunused-local-typedef] serializing_int_requires_an_unsigned_type); ^ /Users/jacob/development/objective-c/textmate/build/include/sparsehash/internal/hashtable-common.h:54:49: note: expanded from macro 'SPARSEHASH_COMPILE_ASSERT' typedef SparsehashCompileAssert<(bool(expr))> msg[bool(expr) ? 1 : -1] ^ /Users/jacob/development/objective-c/textmate/build/include/sparsehash/internal/hashtable-common.h:180:29: warning: unused typedef 'serializing_int_requires_an_unsigned_type' [-Wunused-local-typedef] serializing_int_requires_an_unsigned_type); ^ /Users/jacob/development/objective-c/textmate/build/include/sparsehash/internal/hashtable-common.h:54:49: note: expanded from macro 'SPARSEHASH_COMPILE_ASSERT' typedef SparsehashCompileAssert<(bool(expr))> msg[bool(expr) ? 1 : -1]
On 27 Oct 2015, at 15:11, Jacob Carlborg wrote:
Since I updated Xcode to a later version (can't remember the exact one)
https://github.com/textmate/textmate/commit/00a20aefb6afe1535176d9a778baeee5...
I have no warnings with Apple LLVM version 7.0.0 (clang-700.1.76)
On 2015-10-27 09:22, Allan Odgaard wrote:
I have no warnings with Apple LLVM version 7.0.0 (clang-700.1.76)
Hmm, seems I have not updated sparsehash in a while. Updating that fixed the problem. Sorry for the noise.