Tracking issue for https://github.com/MerosCrypto/Meros/tree/platform-support.
Ubuntu 18.04 and 20.04 should work without issue.
Arch Linux should work without issue.
macOS has several issues.
And there may be more I have yet to find. I also needed to set a manual CPATH/LIBRARY_PATH so gmpy2 would build. I installed the dependencies with brew install gmp mpfr libmpc and it worked without issue, yet after rebooting, and deciding to rebuild on Python 3.8 instead of 3.9 as an experiment, I needed to set a CPATH for gmp and LIBRARY_PATH for all three...
Windows hasn't been supported in ages. I have no idea if we'll want to go with msvc or mingw when we add support for it. While it'd be great to say "MS ecosystem! msvc!", I do remember msvc has some quirks, such as not supporting C99, and I believe horrible CMake integration. That said, the last system I tried on had so much development cruft it's hard to actually say. Multiple libraries only have Linux build instructions. We also don't support tracking file handles on Windows, so Meros will fail to build there as well.
Tracking issue for https://github.com/MerosCrypto/Meros/tree/platform-support.
Ubuntu 18.04 and 20.04 should work without issue.
Arch Linux should work without issue.
macOS has several issues.
-z muldefsis used due to our multiple Rust libraries. This flag doesn't exist on macOS and isn't needed.-framework WebKit.CoreFoundation,CoreGraphics,CoreVideo,ColorSync, andAppKitare also needed frameworks..sofile extension when not on Windows; macOS uses.dylib. I'm curious which BSD uses as well.booting Meros causes26 (invalid data!)to be printed which is another LMDB error.26 (invalid data!)on macOS.And there may be more I have yet to find. I also needed to set a manual CPATH/LIBRARY_PATH so gmpy2 would build. I installed the dependencies with
brew install gmp mpfr libmpcand it worked without issue, yet after rebooting, and deciding to rebuild on Python 3.8 instead of 3.9 as an experiment, I needed to set a CPATH for gmp and LIBRARY_PATH for all three...Windows hasn't been supported in ages. I have no idea if we'll want to go with msvc or mingw when we add support for it. While it'd be great to say "MS ecosystem! msvc!", I do remember msvc has some quirks, such as not supporting C99, and I believe horrible CMake integration. That said, the last system I tried on had so much development cruft it's hard to actually say. Multiple libraries only have Linux build instructions. We also don't support tracking file handles on Windows, so Meros will fail to build there as well.