You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to work on Windows with a cross-platform toolchain so I'm using Ninja + Clang for my project. Since Clang for MSCV is ABI compatible with MSVC code, everything works fine with the anira binaries except for Clang errors related to the symbols \bigobjand \EHsc. Those flags are set in \lib\cmake\Caffe2\Caffe2Targets.cmake in the pre-built binaries (0.1.2), so it's possible to make it work by changing:
I don't know if this .cmake file is written as part of your code or if it comes with the libtorch library. In the latter case maybe there's a CMake command that could be used to intercept the MSVC flags and change them before compilation (this way there's no need to change the libtorch code), but I don't know it. If it's part of your code I suggest making the change so that this toolchain is readily enable on Windows.
Best,
Mathis.
The text was updated successfully, but these errors were encountered:
These cmake files are part of the libtorch library. They look like they are automatically generated by the libtorch cmake install command. So it's something we cann't change since we download the libs from their servers on build.
Hi !
I'm trying to work on Windows with a cross-platform toolchain so I'm using Ninja + Clang for my project. Since Clang for MSCV is ABI compatible with MSVC code, everything works fine with the anira binaries except for Clang errors related to the symbols
\bigobj
and\EHsc
. Those flags are set in\lib\cmake\Caffe2\Caffe2Targets.cmake
in the pre-built binaries (0.1.2), so it's possible to make it work by changing:into
I don't know if this
.cmake
file is written as part of your code or if it comes with the libtorch library. In the latter case maybe there's a CMake command that could be used to intercept the MSVC flags and change them before compilation (this way there's no need to change the libtorch code), but I don't know it. If it's part of your code I suggest making the change so that this toolchain is readily enable on Windows.Best,
Mathis.
The text was updated successfully, but these errors were encountered: