How to build and setup on iOS
First, follow all the instructions on
Setup and Build on OSX
. While some steps could be skipped if you only
want to build for iOS, it is useful to diagnose problems during the initial iOS project setup by replicating it on OSX.
The C++ REST SDK depends on Boost and OpenSSL when used on iOS. It is a non-trivial task to cross-compile libraries for iOS, however there are scripts available online with nonrestrictive licenses to compile many popular libraries -- among these libraries are
Boost and OpenSSL.
This document will walk through the steps to build the C++ REST SDK and its dependencies into a form suitable for use with iOS applications.
For this walkthrough, we assume you are working within the
directory of the project.
git clone https://git.codeplex.com/casablanca
To build OpenSSL, use the script provided by the OpenSSL-for-iPhone project.
git clone --depth=1 https://github.com/x2on/OpenSSL-for-iPhone.git
After building the library, move the include files and libraries to
mv OpenSSL-for-iPhone/include openssl
mv OpenSSL-for-iPhone/lib openssl
This completes building OpenSSL.
project link: https://github.com/x2on/OpenSSL-for-iPhone
To build Boost, use the script provided by the boostoniphone project. The main project author seems to have not continued maintaining the project, however there are a few actively maintained forks. We now recommend using the following repository from faithfracture:
git clone https://gist.github.com/c629ae4c7168216a9856.git boostoniphone
The script `boost.sh` provided by the boostoniphone project has a variable at the top of the file to specify which parts of boost need be compiled. This variable must be changed to include the parts needed for the C++ REST SDK: thread, chrono, filesystem, regex,
system, and random. This can easily be done by applying our patch which sets the IPhone SDK version to 8.0 and Boost version to 1.57.
git apply ../fix_boost_version.patch
The headers need to be moved to allow inclusion via `"boost/foo.h"`.
mv Headers Headers2/boost
mv Headers2 Headers
Finally, the product framework must be moved into place.
mv boostoniphone/ios/framework/boost.framework .
This completes building Boost.
Preparing the C++ REST SDK build
The C++ REST SDK uses CMake for cross-platform compatibility. To build on iOS, we specifically use the toolchain file provided by a ios-cmake fork on GitHub. Also unless you have the Clang compiler on your path the toolchain will need to be patched to correctly
look in /usr/bin/.
git clone https://github.com/cristeab/ios-cmake.git
git apply ../fix_ios_cmake_compiler.patch
This completes the preparation for building Casablanca.
project link: https://github.com/cristeab/ios-cmake
Building the C++ REST SDK
Now we are ready to build the C++ REST SDK for iOS. Invoke the ios-buildscripts subproject in the usual CMake fashion:
cmake .. -DCMAKE_BUILD_TYPE=Release
This will produce a universal static library called "libcpprest.a" inside the 'build.ios' directory for the i386 simulator, x86_64 simulator, armv7, armv7s, and arm64.
If you want to run the tests in the iOS simulator you can simply execute 'make test'.
This will go and run all the tests in the iOS simulator, but the output of the tests won't be displayed. If you want to run the tests directly and see the full output you can manually execute the tests directly with xcodebuild.
xcodebuild test -project ios_runner.xcodeproj -configuration=Release -scheme ios_runner -destination "platform=iOS Simulator,name=iPhone 6"
Now you will see the output of each of the tests cases as they run.
Using the C++ REST SDK
You will need to link against the following from your project:
- libiconv.dylib (Available within the default list of libraries to link)
- Security.framework (Available within the default list of libraries to link)
You will also need to add the following paths as additional include directories:
This should allow you to reference and use the C++ REST SDK from your C++ and Objective-C++ source files. Note: you should change all .m files in your project to .mm files, because even if the source file itself does not use the C++ REST SDK, it is possible
that some C++ code will be pulled in via header includes. To avoid errors later, it is easiest to simply rename all your project sources to use '.mm'.