[Octave-bug-tracker] [bug #57486] mex missing outdir option

[Guillaume]

Follow-up Comment #12, bug #57486 (project octave):

I, for example, compile MEX files by calling 'mkoctfile --mex' from outside
Octave so I am not sure how separate option parsing could take place.

Concerning the -outdir and -output flags, a backward-compatible way forward
could be to do:

* -outdir X: accept
* -output Y: accept, even if Y contains a path (i..e Octave's current
behavior)
* -outdir X -output Y: accept if Y doesn't contain a path (or if path is not
absolute?)
* -outdir X -output Y: if Y has an absolute path, there's a conflict. Either
throw an error or a warning and ignore X.

Not depending on liboctave for mkoctfile might be preferred but the
implementation of above would require access to cross-platform equivalents of
filesep, fullfile, is_absolute_filename.


    _______________________________________________________

Reply to this item at:

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

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