|
From: | John W. Eaton |
Subject: | Re: Compiled Octave 3.8.2 for Android. Plotting with gnuplot? |
Date: | Sat, 20 Dec 2014 18:49:20 -0500 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.2.0 |
On 12/20/2014 03:42 PM, hl2modrift wrote:
I have fixed this problem by recompiling Octave in a path that reflects the one on-device. It seems when compiled, the links octave uses to find things are hard-coded rather than relative. (E.G. /usr/lib/liboctave.so instead of ../lib/liboctave.so from the point of the binary.) This is rather inconvenient for cross-compiling, where on some systems you can't place things into /usr/lib, although I recognize this is a niche-case.
The LD_LIBRARY_PATH and OCTAVE_HOME environment variables can probably fix this problem for you. They have to be set before Octave starts, so you need a script to do that which then invokes the real Octave. Take a look at the octave-wrapper.in file in
http://hg.octave.org/mxe-octave for example.
Also, if anyone is interested, I will eventually do a writeup on XDA, as well as provide a binary. I have yet to work out a few kinks, gnuplot refusing to recognize libgd on configure and the overall size of octave (>1GiB), but I don't believe these will be as hard as some previous ones.
Did you know that there is already a build of Octave and gnuplot for Android distributed through the google play store?
https://play.google.com/store/apps/details?id=com.octave&hl=en jwe
[Prev in Thread] | Current Thread | [Next in Thread] |