是否存在无内联汇编的AngelScript版本以适配MSVC x64编译？

Great question! I’ve dealt with this exact headache when working with AngelScript and MSVC’s x64 toolchain—let me walk you through the fixes:

• Use the official AngelScript build with a preprocessor macro
  You don’t need a special "no-inline-assembly" fork of AngelScript. The official codebase already supports x64 MSVC by providing a fallback implementation that avoids inline assembly. All you need to do is define the AS_NO_INLINE_ASSEMBLY preprocessor macro when compiling. This tells AngelScript to use pure C++ or compiler intrinsic functions instead of x86-style inline assembly, which plays nicely with MSVC’s x64 restrictions.

• Update to the latest AngelScript version if you’re on an older release
  If you’re using a really old version of AngelScript, it might not have the AS_NO_INLINE_ASSEMBLY option yet. Grab the latest code from the official repository—newer releases have completely removed x64 inline assembly dependencies, relying instead on compiler-specific attributes like __fastcall and portable C++ code to handle function invocation.

• Double-check your project settings
  When targeting x64 in MSVC:

  1. Add AS_NO_INLINE_ASSEMBLY to your project’s preprocessor definitions.
  2. Use a modern MSVC toolchain (VS2019 or later)—older versions have more restrictive support for certain C++ features needed by the non-assembly fallback.
  3. Verify none of your custom build flags are forcing inline assembly usage for x64.

Once you set that macro and update your code if needed, the x64 linking errors should disappear entirely, matching the smooth experience you have with the x86 build.

内容的提问来源于stack exchange，提问作者user13455484