Re: Octave on Android

[c.]

On 22 Oct 2013, at 21:21, Corbin Champion <address@hidden> wrote:

> On Tue, Oct 22, 2013 at 11:50 AM, c. <address@hidden> wrote:
> 
> On 22 Oct 2013, at 19:31, John Swensen <address@hidden> wrote:
> 
> > c.,
> > This is actually the easier part (assuming you have installed the Android 
> > SDK with the cross compilation tools). I have built a lot of GPL 
> > libraries/programs that use autotool for iOS and it is as simple as running 
> > the configure script pointing to the cross-compiler toolchain.
> > And example of a script that does this can be found at 
> > https://gist.github.com/nddrylliog/4688209
> 
> John, thanks for the example!
> Yet, I think when all dependencies are considered the script for Octave
> will become much more involved, so I'd really appreciate if Corbin could 
> share this ...
> c.
> 
> Carlo,
> 
> Octave is built in a normal (cross compiled fashion).  It uses the normal 
> configure; make; make install flow.  The dependencies are the same as a 
> normal build of Octave and can be obtained from the normal places.  I am not 
> re-documenting how to build octave or the octave-forge packages.  It is 
> already well documented.  Similarly, I am also not documenting how to 
> download eclipse, the Android SDK and build an Android application.  I am not 
> doing any special in these regards and did not develop any scripts to perform 
> these pieces.  As far as the java front end, it is on github.  There is one 
> more piece which is the converting of the files to lib_*.so names.  I will 
> provide that very soon.  Once that is provided, I think it will be all out 
> there (also need to push other packages).  In the future, I will try to wrap 
> everything possible in a script so it is easier.  I will at least explain the 
> flow next time I go through it.  I really have never had anyone interested in 
> building it from scratch before, so I am not well setup for others, but will 
> fix that.
> 
> Thanks,
> Corbin

Corbin, 

Thanks for this explanation. I'm sure your setup procedure 
is no more then a set configure, make, make install instructions 
which perform cross-compilation. Still I'd really like you to share
those scripts.

Thanks,
Carlo