• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

cossacklabs / themis / #8041
88%
master: 83%

Build:
Build:
LAST BUILD BRANCH: release/0.15.0
DEFAULT BRANCH: master
Ran 27 Oct 2020 12:45PM UTC
Jobs 1
Files 72
Run time 15s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

27 Oct 2020 12:44PM UTC coverage: 88.652% (+0.9%) from 87.723%
#8041

push

travis-ci

web-flow
Make Themis a static framework (#731)

* Clean up whitespace

First of all, to get this thing out of sight, remove all trailing
whitespace that got recently added to the file.

* Make Themis a static framework

Tell CocoaPods to build ObjCThemis as a 'static framework'. That is,
your usual framework bundle but with a static library inside, not a
dynamic one as you would have normally use.

Using static linkage greatly simplifies our life on iOS platforms which
tend to be very picky about dynamic linkage and loading of frameworks.
These issues are not really visible until you archive the app for
distribution, actually install it on the device, and try launching it.
Debugging these issues takes enormous amount amount of time which we
don't have. Let Apple engineers fiddle with dynamic linkage for system
frameworks. That at least makes sense.

Using static linkage for Themis has advantages, such as improved startup
time (no extra symbol resolution) and improved app size (unused parts of
Themis and its dependencies could be cut out by the linker). As Themis
is distributed under a permissive license, there are no legal downsides
of including it as an integral part of an application, it does not have
to be a completely separate binary.

On the other hand, there are not many advantages of dynamic linkage.
We don't get to share the memory and storage as Themis is not a system
framework. The only real advantage is that it's easier to verify that
Themis binaries have not been tampered with and to check Themis version,
but iOS deployment process is know to heavily process the binaries,
making this point mostly moot.

3789 of 4274 relevant lines covered (88.65%)

19443.71 hits per line

Jobs
ID Job ID Ran Files Coverage
1 #8041.1 27 Oct 2020 12:45PM UTC 0
88.65
Source Files on build #8041
Detailed source file information is not available for this build.
  • Back to Repo
  • 3f858f41 on github
  • Prev Build on HEAD
  • Next Build on HEAD
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc