We have just upgraded to 2023.1.8.8601 and can build successfully against x64_vc170 prebuilt libs when using msvc toolchain.
However we are seeing a compilation issue building against x64_vc170 prebuilt libs when using vanilla clang (ie. https://clang.llvm.org/). The error appears in several places in "C:\Program Files (x86)\Audiokinetic\Wwise2023.1.8.8601\SDK\include\AK\Tools\Common\AkBitFuncs.h" due to the fact that _MSC_VER is #defined by default in clang on windows. See the following link for more info: https://clang.llvm.org/docs/UsersManual.html#microsoft-extensions
For example, the following code snippet relies on the _BitScanForward MSVC-specific helper function, which does not exist in clang.
I have modified the guard as shown in the comment below to fix this issue, but wanted to post here bring it to the attention of the AK developers to ideally avoid this pattern in future releases.
//#if defined _MSC_VER && !defined(__clang__)
#if defined _MSC_VER
AkForceInline AkUInt32 AkBitScanForward(AkUInt32 in_bits)
{
unsigned long ret = 0;
_BitScanForward(&ret, in_bits);
return in_bits ? ret : 32;
}
#elif defined(__clang__) || defined (__GNUC__)
AkForceInline AkUInt32 AkBitScanForward(AkUInt32 in_bits)
{
return in_bits ? __builtin_ctz(in_bits) : 32;
}
#else
AkForceInline AkUInt32 AkBitScanForward(AkUInt32 in_bits)
{
if (in_bits == 0) return 32;
AkUInt32 ret = 0;
if ((in_bits & 0x0000FFFFULL) == 0) { ret += 16; in_bits >>= 16; }
if ((in_bits & 0x000000FFULL) == 0) { ret += 8; in_bits >>= 8; }
if ((in_bits & 0x0000000FULL) == 0) { ret += 4; in_bits >>= 4; }
if ((in_bits & 0x00000003ULL) == 0) { ret += 2; in_bits >>= 2; }
if ((in_bits & 0x00000001ULL) == 0) { ret += 1; in_bits >>= 1; }
return ret;
}
#endif