Generating docs when cross-compiling

[John W. Eaton]

On 19-Apr-2012, Corbin Champion wrote:

| I can cross compile octave, specifying -host=xyz but, now I want to build the
| docs as well to get help working etc.  When I don't use --disable-docs, but I
| specify -host=xyz, I fail when it tries to run munge-texi.  The build process
| needs to NOT cross compile munge-texi and a few other executables.  I can work
| around this by building octave without cross compiling, saving off these
| executables and then copying these over when I am cross compiling.  But, I
| assume there is an easier way.  What is the easier/correct way to do this?  I
| am guessing the guys that cross compile for mingw have to solve the same 
thing.

I don't think this problem has been solved yet.

Is munge-texi the only compiled program that we have that is used in
the build process?  If so, maybe we could replace it with a script.

Are there other compiled programs that are used as part of the build
process?

jwe