[bug #68040] mkoctfile compatibility with mex

Rik <[email protected]> Wed, 11 Feb 2026 08:29:24 -0500 (EST)

Newsgroups	gmane.comp.gnu.octave.bugs
Message-ID	<[email protected]>

Please use the bug tracker to post updates to a bug report.  The mailing list is intended as a read-only notification stream.  Info posted to this mailing list address won't appear in the tracker database where it is most useful.

URL:
  <https://savannah.gnu.org/bugs/?68040>

                 Summary: mkoctfile compatibility with mex
                   Group: GNU Octave
               Submitter: rik5
               Submitted: Wed 11 Feb 2026 05:29:20 AM PST
                Category: Octave Function
                Severity: 1 - Wish
                Priority: 5 - Normal
              Item Group: Matlab Compatibility
                  Status: Confirmed
             Assigned to: None
         Originator Name:
        Originator Email:
             Open/Closed: Open
         Discussion Lock: Unlocked
                 Release: dev
        Operating System: Any
           Fixed Release: None
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Wed 11 Feb 2026 05:29:20 AM PST By: Rik <rik5>
Comparing Matlab *mex* function and Octave *mkoctfile*, there are a few things
that could be improved.

The *mex* options *-R2017b* and *-R2018a* are supported, but not documented.
Since those are specific to *mex*, perhaps documentation should go in *mex.m*
rather than in *mkoctfile.in.cc*.

Similarly, *-largeArrayDims* and *-compatibleArrayDims* are undocumented
(although they also don't do anything).

There is no documentation for *-U* which should go in *mkoctfile.in.cc*.

The *-outdir* option is not currently supported.  If it is an easy hack, then
I would add it.









    _______________________________________________________

Reply to this item at:

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

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

signature.asc (application/pgp-signature, 228 B)