summaryrefslogtreecommitdiff
path: root/monero_libwallet2_api_c/CMakeLists.txt
AgeCommit message (Collapse)Author
2024-06-12fix wownero build issues, rename target to proper tripletCzarek Nakamoto
2024-05-27macos fixesCzarek Nakamoto
2024-05-23mingw and android fixesCzarek Nakamoto
2024-05-23-DCMAKE_SYSTEM_VERSION=1Czarek Nakamoto
is the workaround to update to newer ndk without breaking the entire build system
2024-05-16WIP: UR support in moneroCzarek Nakamoto
2024-05-15add {aarch64,x86_64}-host-apple-darwin targetsCzarek Nakamoto
2024-05-15MAKE_OSX_ARCHITECTURESCzarek Nakamoto
2024-05-15fix amd64 builds on macosCzarek Nakamoto
fix homebrew_prefix
2024-04-29windows supportCzarek Nakamoto
2024-04-26fix darwin cross compilation buildv0.18.3.3-RC40Czarek Nakamoto
2024-04-25wownero-seed supportCzarek Nakamoto
2024-04-02actually fix and not workaround the iOS issue.v0.18.3.3-RC16Czarek Nakamoto
2024-04-02feat: iOS buildsv0.18.3.3-RC15Czarek Nakamoto
includes patches to - randomx: https://github.com/tevador/RandomX/pull/294 - randomwow: https://git.wownero.com/wownero/RandomWOW/pulls/2
2024-04-01un-conflict exported symbols on macosCzarek Nakamoto
2024-04-01feat: macos host buildsCzarek Nakamoto
2024-04-01fix: wownero and monero wallets in the same processv0.18.3.3-RC12Czarek Nakamoto
ci: cache ~/.ccache directory
2024-03-31feat: split MONERO and WOWNERO prefixed functionsv0.18.3.3-RC11Czarek Nakamoto
So basically: when we open the .so file, we define some symbols, and it appears that if we load something else, with the same symbols, under the same thread we cause some funky behaviour - like calling function a wownero function MONERO_Wallet_address() resulting in a monero address being generated. Needless to say, this is undesired, and a blocker for https://github.com/cypherstack/stack_wallet/pull/818 I'm afraid that this may not solve all of our issues (but will solve some significant roadblocks), because of the "genesis block" issue, as output of nm -gDC release/wownero/x86_64-linux-gnu_libwallet2_api_c.so | grep genesis indicate that these functions may share *something* in common across both WOW and XMR libraries. In a case in which this fix won't be sufficient, I think that the way forward would be to close the dynamic libraries, but before we do that I want to check if maybe there is a change to run multiple wallets at once.