-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document known-good versions #6
Comments
I managed to run it using the following versions:
I agree that having submodules, some script to fetch the dependencies or the info would be helpful. |
I have been building using Bibletime master branch on commit 1a8467dc72ff9fdcc79d671e582f17261b10c836. This is shown in the About dialog if you using the Android package I build. There were numerous api changes in later versions and I did not want to follow while these were changing. It is on my short list to get up to date with Bibletime. I have been using sword 1.8.1. Since I was the only one compiling Bibletime Mobile, I have not documented the build process. I will work on this in the next few days. I have been working on a new Bookshelf Manager which works much like Bibletime desktop. I should be able to finish this shortly. |
I have created a README.md file and put build information into it. Is there something else you can suggest adding? I also fixed a linux build issue. |
Thank you. Maybe a link could be added for the sword library. |
I added the Sword link. |
There should be some sort of documentation of known-good versions of attendant libraries. I'm trying to re-create the build for this on my PinePhone after the latest merge added the appropriate profile. The source tree does not match the current state of the Bibletime source tree (several files are missing that this project expects), and the same goes for SWORD. I'm presuming that they're expecting some released version rather than the head of the development for both of those, but it would be nice to have that documented somewhere.
It could be possible to tag specific commit hashes as a git submodule, or at least some info on how to build would be appreciated.
The text was updated successfully, but these errors were encountered: