Builds were failing in various ways on 32-bit platforms, due to various assumptions (and the fact that pretty much everything is 64-bit nowadays). This PR should fix all of them so that it builds clean.
* host: libbladeRF/thirdparty/adi: fix build error on 32-bit systems
sizeof(void*) is not necessarily equal to sizeof(uint64_t)
* host: libbladeRF/doc: fix 32-bit build failure on doc example
sizeof(size_t) does not always equal sizeof(uint64_t)
* host: docker: remove centos-7-i386 build
it doesn't work, and this is an edgy-enough case that i think we'll be
okay with the ubuntu i386 builds
* host: libbladeRF/bladerf2: explicitly note constant types
On non-64-bit platforms, these integer constants can be ambiguous, which
throws compiler warnings.
* host: libbladeRF_test: explicitly note constant types
On non-64-bit platforms, these integer constants can be ambiguous, which
throws compiler warnings.
Visual Studio 2013 now includes these headers, so they have
been moved as not to conflict (even though they are intended to
be equivalent.)
Our stdbool.h was providing an incorrect typedef; sizeof(bool)
should have been 1, not sizeof(int).
Per http://msdn.microsoft.com/en-us/library/tf4dy80a.aspx:
"In Visual C++4.2, the Standard C++ header files contained a typedef
that equated bool with int. In Visual C++ 5.0 and later, bool is
implemented as a built-in type with a size of 1 byte. That means
that for Visual C++ 4.2, a call of sizeof(bool) yields 4, while in
Visual C++ 5.0 and later, the same call yields 1. This can cause
memory corruption problems if you have defined structure members of
type bool in Visual C++ 4.2 and are mixing object files (OBJ) and/or
DLLs built with the 4.2 and 5.0 or later compilers."