Open lsl330 opened 4 months ago
Failed in dependency marisa-trie:arm64-windows
which does not provide arm64
configuration platform by s-yata/marisa-trie - vs2019/vs2019.sln.
As for the fixes you mentioned, probably it was against to the unofficial BYVoid/OpenCC - deps/marisa-0.2.6/CMakeLists.txt that maintained by OpenCC.
Please request platform arm64
support from upstream marisa-trie
.
Failed in dependency
marisa-trie:arm64-windows
which does not providearm64
configuration platform by s-yata/marisa-trie - vs2019/vs2019.sln.As for the fixes you mentioned, probably it was against to the unofficial BYVoid/OpenCC - deps/marisa-0.2.6/CMakeLists.txt that maintained by OpenCC.
Please request platform
arm64
support from upstreammarisa-trie
.Failed in dependency
marisa-trie:arm64-windows
which does not providearm64
configuration platform by s-yata/marisa-trie - vs2019/vs2019.sln.As for the fixes you mentioned, probably it was against to the unofficial BYVoid/OpenCC - deps/marisa-0.2.6/CMakeLists.txt that maintained by OpenCC.
Please request platform
arm64
support from upstreammarisa-trie
.
the marisa can build on arm64,but i don't know how to fix on vcpkg.
here is my step: 1、./vcpkg install marisa-trie:arm64-windows --allow-unsupported,and will show the error. 2、unzip the marisa-trie file on vcpkg/download 3、use vs studio open the 2019.sln,and copy x64 setting to arm64 4、build arm64 success
hope will help for the marisa-trie:arm64-windows
@lsl330 Thank you for your investigation, there is currently no easy way to increase the build configurations for sln
, and given that the upstream does not explicitly provide support for the arm64
or arm64ec
support, the most appropriate way is still to request the upstream.
Is your feature request related to a problem? Please describe.
here is an error,opencc is only supported on '!(arm | uwp)', which does not match arm64-windows.
Proposed solution
opencc Fix build on win arm64 since 1.1.5(lastest is 1.1.7) https://github.com/BYVoid/OpenCC/releases/tag/ver.1.1.5
Describe alternatives you've considered
No response
Additional context
No response