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
In order to support the swift sdk we need to release a statically linked binary which works for both the emulator and a real device.
This means that on MacOS we need to use cargo lipo to build an ios binary and upload it with the other ironoxide_java artifacts.
In addition to uploading the statically linked library for ios.
As part of this we should also rename the ironoxide_shared to just ironoxide
The text was updated successfully, but these errors were encountered:
ernieturner
changed the title
Upload OSX & iOS artifacts for the c++ binding to releases.
Upload iOS artifacts for the c++ binding to releases.
Jun 8, 2020
I started this work over on the osx_build branch. I renamed the library to ironoxide.
We need to change crate-type to staticlib on the machine that's doing the ironoxide ios build (which must be on OSX).
After setting up the crate-type, we should install cargo-lipo. Then we should run cargo lipo --release in the cpp dir. Once we do that, we should upload it to the release as ironoxide_ios.a.
We want to do the ios suffix in the release so if we produce a different lib later which is statically linked we can handle it.
coltfred
changed the title
Upload iOS artifacts for the c++ binding to releases.
Upload homebrew artifact for the c++ binding to releases.
Jun 10, 2020
In order to support the swift sdk we need to release a statically linked binary which works for both the emulator and a real device.
This means that on MacOS we need to use cargo lipo to build an ios binary and upload it with the other ironoxide_java artifacts.
In addition to uploading the statically linked library for ios.
As part of this we should also rename the
ironoxide_shared
to justironoxide
The text was updated successfully, but these errors were encountered: