I followed the intructions given in the ReadMe file and stuck in the
step where we have to navigate to the JNI directory and execute, make
APP=droidreader,
Because there is no makefile here. There is a Android.mk, but no make
file which invokes this.
Is this a typo here, should I be going to android-ndk root folder and
execute make or is there something obvious I am missing.
Rgds
Sriram
that step is to be executed within the NDK directory. The code hasn't
seen updates for a while now, I hope I'll get some spare time in
december to bring the code a bit up to date, but I can't promise.
-hwh
2011/11/24 sriram <srim...@gmail.com>:
Those instructions are well out of date, but I'm not sure if they
still apply in some cases. Hans-Werner, do you still use some variant
on that, or should we update the README?
Here's what I'd do (assuming you're building on Linux):
1) Get a clean droidreader source tree from svn.
2) extract it in (for example) /home/sriram/droidreader
3) make a new folder, called (for example) /home/sriram/thirdparty
4) copy all the files from the droidreader "docs" directory to your
thirdparty directory
5) go to the thirdparty directory, and make sure all the files are
executable.
6) run dr-getdeps. This assumes you have darcs, subversion, git, and
wget available.
7) run dr-updatedeps ../droidreader. This will copy all of the
dependency source files to the droidreader directory.
8) copy the buildit script to your droidreader folder
9) go into your droidreader folder and execute ./buildit. This will
build everything and install it on a device if one happens to be
connected.
Let me know how this goes for you!
By the way, I just committed some changes to make the code build with
new deps. I also made it render in grey-scale rather than full colour
when the display is inverted - I think that looks better than the
negative-colour effect. Let me know if you agree or not.
Cheers,
Rob.
> Rgds
> Sriram
I really need to get back to the code. I think that I'll have some
spare time between christmas and new year's eve as my workplace closes
its doors during that time and we're expected to take some of our free
days then.
My plan is to beat the code back into shape to build with a current
NDK and a current version of muPDF.
Admittedly, purchasing an ebook reader has taken a lot of pressure out
of my motivation to read PDFs on my Android phone. But I see that
there's a niche for Open Source PDF readers on Android. Maybe I'll
even take some money into my hands and bring it to the Market (it is
already there, although for money that does not go to me or you).
-hwh
2011/12/3 Rob Brown <rob.cob...@gmail.com>:
The code does build with the latest mupdf and NDK, it's actually been
pretty good all along. I tried building it for ARMv7, and it worked,
but I didn't notice any performance improvement. Hardly surprising, I
guess.
I still use DroidReader! It's an ideal no-fuss reader and the night
mode is better than anything else I've found. Maybe I'm biased :) The
page pre-loading that I've always wanted to do would be an
enhancement, but I don't think I'll have time for it anytime soon.
I hope you have a great holiday!
Rob.
On Dec 9, 2:15 am, Hans-Werner Hilse <hwhi...@googlemail.com> wrote:
> Hi,
>
> I really need to get back to the code. I think that I'll have some
> spare time between christmas and new year's eve as my workplace closes
> its doors during that time and we're expected to take some of our free
> days then.
>
> My plan is to beat the code back into shape to build with a current
> NDK and a current version of muPDF.
>
> Admittedly, purchasing an ebook reader has taken a lot of pressure out
> of my motivation to read PDFs on my Android phone. But I see that
> there's a niche for Open Source PDF readers on Android. Maybe I'll
> even take some money into my hands and bring it to the Market (it is
> already there, although for money that does not go to me or you).
>
> -hwh
>
> 2011/12/3 Rob Brown <rob.cobblew...@gmail.com>: