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

LAST BUILD BRANCH: release/0.15.0
DEFAULT BRANCH: master
Ran
Jobs 1
Files 73
Run time 16s
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
coverage: 87.851%. Remained the same
#7857

push

travis-ci

web-flow 
Remove ObjCThemis.xcodeproj (#704)

* Remove ObjCThemis.xcodeproj

The idea behind building "objcthemis.framework" has been to unify import
syntax between Carthage and CocoaPods. Unfortunately, it turned out to
be a mistake. "objcthemis.framework" does not work without
"themis.framework" being present alongside it because of how module
resolution works. Despite "objcthemis.framework" providing the same
"themis" module as "themis.framework", the compiler will look for a
framework named "themis.framework" when resolving "import themis".

Moreover, the original issue that "objcthemis.framework" has been called
to rectify can be resolved more elegantly by importing the module:

    @import themis;

which work well with "themis.framework" in both Carthage and CocoaPods.

Since "objcthemis.framework" does not bring any value, remove it. Move
all new things added to ObjCThemis.xcodeproj into Themis.xcodeproj
(such as testing Swift 4 vs 5). Remove the import warning. Now Carthage
will build only one framework: "themis.framework" from Themis.xcodeproj.

I am sorry for the trouble and confusion of this fizzled migration.

* Change "product name" to "themis"

Make sure that Xcode targets produce "themis.framework", not
"objcthemis.framework".

* Recreate Xcode schemes

It seems that some components stick the schemes after renaming. Recreate
them to make sure that we're building "themis.framework" and there are
no traces of the old Xcode project.

* Bring back proxy umbrella header "themis.h"

Since the framework is named "themis.framework", its umbrella header
is expected to be called "themis.h". The actual umbrella header for
ObjCThemis is "objcthemis.h" which we simply include.

* Use alternative imports in unit tests

One of the reasons for "objcthemis.framework" existence was to run
ObjCThemis unit tests from Xcode. Initially, "themis.framework" has
prevented that due to import issues, and "objcthemis.framework" h... (continued)

3789 of 4313 relevant lines covered (87.85%)

19269.07 hits per line

Jobs
ID Job ID Ran Files Coverage
1 #7857.1 0
87.85
Source Files on build #7857
Detailed source file information is not available for this build.