[Octave-bug-tracker] [bug #49503] [mxe-octave] cross-building packages with configure script calling octave itself have issues

[Markus Mützel]

Update of bug #49503 (project octave):

                  Status:                    None => In Progress            

    _______________________________________________________

Follow-up Comment #20:

You are right. And I agree that binary (Octave Forge) packages should avoid
using Octave in their build scripts if that is possible.

If it is reliable or not, depends on for what Octave is used in the build
process: It's probably not a good idea to rely on it for configure options or
similar things.
However, the image package - as an example - uses the "exist" function to
check whether some functions are provided by core Octave. John D suggested to
use "mkoctfile -p FCNFILEDIR" as an alternative. But that won't work for
built-in functions and it relies on internal knowledge where which file is
stored (which could change between versions).
AFAICT there is no alternative way how that information can be reliably
queried atm.
That kind of information would also be reliable with a minimal Octave. (If a
feature is disabled, the corresponding functions are still present but they
throw an error or warning afaict.)

I'm attaching a work in process patch that adds a build-octave target to MXE
Octave. With it, of-image builds successfully for me.
No logic yet to alternatively use an Octave that is installed on the build
system. And the warning message about a missing native build of Octave is
still displayed. And probably a lot of other missing parts...

(file #49769)
    _______________________________________________________

Additional Item Attachment:

File name: bug49503_build_octave_wip.patch Size:5 KB
   
<https://file.savannah.gnu.org/file/bug49503_build_octave_wip.patch?file_id=49769>



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?49503>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/