OpenSSL and cURL

The supported tools and software for both DL Reader and Book2png are the same. But if your goal is to build RMSDK so you can build DL Reader for an iOS platform, you need to build OpenSSL and CURL differently than we describe for building Book2png.

Copy the DLBuildIOSExternals.mak file and the Makefile to the RMSDK root folder.

Unzip cURL and OpenSSL in the RMSDK root directory. Rename the folders that result to "curl" and "openssl" under the RMSDK root directory.

Open a Mac terminal session, and change folder to RMSDK root folder. Run the makefile (DLBuildiOSExternals.mak) from the RMSDK root directory:
make -f DLBuildiOSExternals.mak
To verify that both libraries are built open this directory:
thirdparty/openssl/public
You should see iPhone folders for various architectures, and similarly for curl libraries.

If you see this error:
Error: "We can't compile without socket() support!"
Make sure that you have Xcode commandline tool installed, using the Xcode commandline tool installed, using the "xcode-select --install" command.

Building the dp library

Build the dp library from RMSDK. Run
make dp-ios-all
If this command fails, you might want to try to open the dp project in Xcode:
rmsdk_root/dp/build/xc5/dp.xcodeproj
Then close Xcode to refresh some of the project settings.

Configure your development certificate

Starting with RMSDK 11, all applications built using RMSDK require a certificate file from Adobe Systems to allow you to distribute your code. Without a valid certificate, RMSDK APIs will not function properly.

There are two types of certificates, development and distribution. The development certificate is for building a new application, and can be used on multiple projects and platforms, but it expires after 60 days. When your development certificate expires, you need to submit a new form to replace it. You will need a distribution certificate when you plan to release an eReader app to market. Distribution certificates do not expire, and are good for each build of an application. But you must request a new distribution certificate whenever you change the source code for your app, or release a new build for the product.

To learn more about distribution certificates, see the files included in RMSDK11_Signing_Certificate_Info_v2.zip, provided with the RMSDK deliverables. You can download this zip file from an FTP site provided by Datalogics after you purchase the product.

Request both types of certificates from Datalogics. See the Adobe Systems Development Certificate. Look at ReadMe1st_DL.txt in RMSDK_CERTIFICATION_v3.zip for details on how to place your request.

After you receive the Adobe development certificate from Datalogics you need to configure DL Reader to find it. The certificate comes in the form of a file called ReaderClientCert.sig.

1. Store the ReaderClientCert.sig file wherever you like.
2. Create a new config file called rmsdk_cert.cfg in the Scripts folder, at the root level of the DL Reader source tree.
3. Add the following lines to this config file. Substitute the path to your RMSDK development certificate where indicated below. The cert-path parameter references the folder where the ReaderClientCert.sig file is stored.

For example, edit the rmsdk_cert.cfg file to look like this:
[CertificateLocation] cert-path=path/to/RMSDK/certificate


Building DL Reader

Use Xcode to open the DLReader.xcworkspace found in the DL Reader root folder.  Follow the instructions for build configurations shown in the ReadMe.MD file found in the DL Reader iOS root folder. Start with building with the Debug build configuration.