I send a pull request for update SDKLauncher-ios.
This is to include unchanged RDContainer.mm/h files which are detached from the Readium SDK project.
The reason why those files are attached SDKLauncher-iOS rather than Readium SDK is:
Since RDContainer.mm needs to be modified to include LCP related header file and initialization code int the future, it is better to be in the SDKLauncher-iOS side in order to make Readium-SDK a DRM agnostic library.
In Launcher-OSX case, the initialization process including ePub3::InitializeSdk() is in the LauncherOSX/LOXePubSdkApi.mm file, not in the Readium SDK, which is pretty natural.
The merge should be done together with disposal of the pull request of the Readium SDK.
Because only one disposal of either SDKLauncher-iOS or Readium SDK could make duplication or missing files problem.
And for the consistency of the Readium codes, in the future, we recommend all Launcher related files should locate at Launcher project instead of Readium SDK like Launcher-OSX case.
Dear Readium SDK people.
I send a pull request for update SDKLauncher-ios. This is to include unchanged RDContainer.mm/h files which are detached from the Readium SDK project.
The reason why those files are attached SDKLauncher-iOS rather than Readium SDK is:
The merge should be done together with disposal of the pull request of the Readium SDK. Because only one disposal of either SDKLauncher-iOS or Readium SDK could make duplication or missing files problem.
And for the consistency of the Readium codes, in the future, we recommend all Launcher related files should locate at Launcher project instead of Readium SDK like Launcher-OSX case.