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
Given the gcc/gas-specific aspect of this implementation and the default development kits on Apple Mac OSX being LLVM-based, do you think it would make sense to distribute a libhashtree.a with Mach-O files for the current x86_64 implementation and (hopefully) future ARM64 implementation?
If so, would it make sense to also distribute ELF/COFF object files at the same time? (The COFF maybe as a Windows .lib).
The text was updated successfully, but these errors were encountered:
Windows is kinda special in that it's only supported on AMD64. I'm happy if someone provides ARM code for windows. I won't be setting an emulator for that. I just finished porting the AARCH64 code with sha2 instructions. After that's tested enough and cpu detection is added, will start thinking about a binary release.
Given the gcc/gas-specific aspect of this implementation and the default development kits on Apple Mac OSX being LLVM-based, do you think it would make sense to distribute a
libhashtree.a
with Mach-O files for the current x86_64 implementation and (hopefully) future ARM64 implementation?If so, would it make sense to also distribute ELF/COFF object files at the same time? (The COFF maybe as a Windows
.lib
).The text was updated successfully, but these errors were encountered: