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
Cloned didkit and ssi in the same level in a folder
Ran cargo build in the didkit root folder
Ran cd ./lib
Ran make ../target/test/android.stamp
Got this error:
error: linking with `i686-linux-android19-clang` failed: exit status: 1
|
= note: LC_ALL="C" PATH="... "-o" "~/Desktop/didkit/target/i686-linux-android/release/deps/libdidkit.so" "-Wl,--gc-sections" "-shared" "-Wl,-z,relro,-z,now" "-Wl,-O1" "-nodefaultlibs"
= note: ld: error: unable to find library -lunwind
clang: error: linker command failed with exit code 1 (use -v to see invocation)
error: could not compile `didkit` (lib) due to previous error
make: *** [../target/i686-linux-android/release/libdidkit.so] Error 101"
I ran brew install lunwind:
➜ lib git:(main) ✗ brew install lunwind
Warning: No available formula with the name "lunwind". Did you mean luabind or libunwind?
==> Searching for similarly named formulae and casks...
==> Formulae
luabind
To install luabind, run:
brew install luabind
I ran brew install luabind:
➜ lib git:(main) ✗ brew install luabind
Error: luabind has been disabled because it is not maintained upstream!
I ran brew install libunwind:
➜ lib git:(main) ✗ brew install libunwind
libunwind: Linux is required for this software.
Error: libunwind: An unsatisfied requirement failed this build.
The text was updated successfully, but these errors were encountered:
Use forked repository https://github.com/alan-turing-institute/trustchain-mobile.git
and follow the instructions from install_trustchain_mobile.md file to setup the project.
This is updated latest repo.
Android and iOS running successfully without any issues.
cargo build
in thedidkit
root foldercd ./lib
make ../target/test/android.stamp
Got this error:
I ran
brew install lunwind
:I ran
brew install luabind
:I ran
brew install libunwind
:The text was updated successfully, but these errors were encountered: