Building the SDK and Test App for iOS

22 posts / 0 new
Last post

It is highly recommended to first follow the build instructions and successfully build for OS/X before attempting to build for iOS.
Below link does not show the build the SDK for and Test App for IOS .
See: http://readium.org/readium-sdk-building-the-sdk-and-apps

so kindly post the following steps to build the Readium SDK for IOS .
I download the Readium SDK master zip file in GITHUB in below link

https://github.com/readium/readium-sdk
but i don't know how to implement and test.
kindly provide sample ios examples for epub files read using readium sdk and post the steps for creating the ePub reader with Readium SDK for IOS

Thanks Advance for your answer .
kindly help me!

Thanks Advance.
kindly help me.

where is the answer?

That webpage is rather out of date. Please consult the Google doc here:

https://docs.google.com/document/d/1DphaTO2fu7mQoBKalzyfphIlOB2Ncp7yHbIb...

Also, because we use submodules the zip functionality of github doesn't work properly. Please clone the repo as discussed in the doc above.

Thanks a lot.

That Google doc certainly solved a few mysteries for me – thanks! I went down the ReadiumJS Viewer route, as I want to deploy this on a server.

There is a little bit of a learning curve involved for the average Joe who might just want to grab some code, drop it on a server and see it work. In some cases installing NodeJS will not be an option and in others the time/skills required might not be available. This project could definitely do with a simpler entry point.

Following the process in the Google doc to the letter should get something running, but there are a couple of things that might trip a few people up. Firstly, you may need to configure proxy settings for Git and/or NodeJS – if either appear to be having issues getting stuff from the internet, that's the first thing to check. Secondly running the final Grunt command (running Gruntfile.js) might appear to fail if you have anything else using port 8080. I happen to have a local instance of Tomcat running on that port, so I needed to edit Gruntfile.js and set the port option to something different.

Trying to get this on a server that other people could see uncovered a potential bug. It seems the paths for a few files, most notably /epub_content/epub_library.json and some interface icons, have their paths pointing to the root of the server, e.g.
[server_root]/epub_content/epub_library.json

What's really needed is
[server_root][/some/optional/path]/epub_content/epub_library.json

A fairly brief look at the source code didn't turn up any obvious (to me) way to add the missing path information in a reliable fashion. (I tried copy & pasting a build to the servers and running the builds in situ – no difference.) For my local Tomcat instance, a partial workaround was to copy the missing files to the server root, but there were still some things that failed e.g. the link back to the library from a book. For the development server I'm using, I didn't have access to the root directory, so the partial fix was hacking line 16 in StaticStorageManager.js to hard code the extra path info. Again, this is not a complete solution.

For reference, the icons that didn't load correctly are:
[server_root]/images/ico_singlepage_up.png
[server_root]/images/ico_doublepage_up.png

Hope that's some help.

Thanks Jase, we are taking a look.

I consulted the Google doc, the SDKLauncher-iOS part, to clone the repo, but I can not successfully build the iOS App.
My error is in the 'property_holder.cpp', and the error is :
Semantic Issue
No viable conversion from 'bool' to 'PropertyPtr' (aka 'shared_ptr<ePub3::Property>')

Could you instruct me to solve this problem?
Thanks !

Because we use submodules in the repos for the Launchers (as we call the sample apps), the zip doesn't work. Please clone the repo as detailed in the instructions. Let us know if that doesn't work.

Oops. Not enough coffee, Read the first post instead of the last. :-)

Master is a little out of date. I suggest you clone develop. The error you are seeing results from the fact that XCode upgraded their internal compiler which is pickier that the old one. The code IS an error. Now fixed in the develop branch. We will update master early next week.

Thanks for your answer.

My colleague help me fixed it:
change the code from “return false;” to “return nullptr;
then it works! Great !

But when I run the App in iOS simulator - iPad, the home page can't be scrolled to the top, so the menu is hidden and can't be clicked. I'll try the develop branch later, and check if it can work smoothly or not.

Glad you fixed it. That is in fact the correct fix.

Sorry, which home page? What document? Can you be more explicit and/or supply the document in question (I am rkwright@readium.org)

Hello,

I'm trying to build SDKLauncher-iOS,
I've downloaning with git clone --recursive https://github.com/readium/SDKLauncher-OSX.git
and open the xcodeproj in xcode 5
when I try to build I got this error :

PhaseScriptExecution Run\ Script /Users/ordi/Library/Developer/Xcode/DerivedData/SDKLauncher-iOS-doxdjpmikuldptgsfrbxyevnxfvk/Build/Intermediates/ePub3.build/Debug-iphonesimulator/ePub3-iOS.build/Script-AB5D1071172AD540001D3C95.sh
cd /Users/ordi/Desktop/SDKLauncher-iOS/readium-sdk/Platform/Apple
/bin/sh -c /Users/ordi/Library/Developer/Xcode/DerivedData/SDKLauncher-iOS-doxdjpmikuldptgsfrbxyevnxfvk/Build/Intermediates/ePub3.build/Debug-iphonesimulator/ePub3-iOS.build/Script-AB5D1071172AD540001D3C95.sh

MakeHeaders.sh: line 22:
: command not found
MakeHeaders.sh: line 37: syntax error: unexpected end of file
Command /bin/sh failed with exit code 2

Do you know what to do with this ?

Thanks

I finaly find how to resolve,
may be the problem came because I downloaded the sources on Windows and after copy it on a Mac, it should be hidden chars or something like that.
I remplaced the files and it work now

Is there any document on how to integrate SDK / what files from the SDK-Launcher demo will be required to import in a project where I would like to use readium sdk? Google doc provides info about how to run the demo but can't find info about implementation/integration in actual project.

At present the documentation is rather meagre in that regard.  We will try to provide more systematic docs in the new year, but in the meantime, I would carefull study the iOS Launcher code ( which is a big part of its purpose).

1.If i opened an ePub book in Readium SDK Launcher for iOS application.The problem is that if i zoom out any page and then if i try to move next page, loading time to load next page is very high.
2.Do Readium-IOS have any plan to support Adobe DRM books ?
3.How could we implement our own functionality in to book (like adding Highlight, change background colour of book etc)?

1.If i opened an ePub book in Readium SDK Launcher for iOS application.The problem is that if i zoom out any page and then if i try to move next page, loading time to load next page is very high.
2.Do Readium-IOS have any plan to support Adobe DRM books ?
3.How could we implement our own functionality in to book (like adding Highlight, change background colour of book etc)?

1.If i opened an ePub book in Readium SDK Launcher for iOS application.The problem is that if i zoom out any page and then if i try to move next page, loading time to load next page is very high.
2.Do Readium-IOS have any plan to support Adobe DRM books ?
3.How could we implement our own functionality in to book (like adding Highlight, change background colour of book etc)?

@Menca:  Can you please not re-purpose these forum threads.  But better than a forum post is to open an issue here:

https://github.com/readium/SDKLauncher-iOS/issues

More info here:

http://readium.github.io/contributing.html

some notes about the iOS test app:

The App represents our 'sprint 0' features, meaning that it does not yet include js pagination.
The master and develop branch are identical at this point, js pagination work will be done on the develop branch
The App builds against the Readium-SDK but that project is not a submodule in the Git sense yet. The App expects that the SDK folder is a sibling to the main iOS launcher directory:
- <SomeDirectory>
+ readium-sdk
+ SDKLauncher-iOS
The App builds against the develop branch of readium-sdk HOWEVER, there is a linker error in the SDK for iOS that was introduced after change d558570. Setting your SDK source to change d558570 will allow the project to link and the App to build.
At present the App can run in an iOS simulator but you cannot yet build the SDK for iOS devices so the runtime is confined to the simulator.

Secondary menu