[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #48511] mxe-octave: mex library dependencies n
From: |
Joris Gillis |
Subject: |
[Octave-bug-tracker] [bug #48511] mxe-octave: mex library dependencies not picked up |
Date: |
Thu, 14 Jul 2016 12:48:29 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:44.0) Gecko/20100101 Firefox/44.0 Iceweasel/44.0.2 |
URL:
<http://savannah.gnu.org/bugs/?48511>
Summary: mxe-octave: mex library dependencies not picked up
Project: GNU Octave
Submitted by: jgillis42
Submitted on: Thu 14 Jul 2016 12:48:26 PM GMT
Category: Configuration and Build System
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Matlab Compatibility
Status: None
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 4.0.2
Operating System: Microsoft Windows
_______________________________________________________
Details:
Consider a mex file linked with a dll file, both living in some directory.
After simply addpath-ing the directory, calling the mex file works in Matlab
yet fails in Octave.
For Matlab, the loader searches for dlls in the same directory as where the
mex file resides.
It would make sense if Octave copied this behaviour.
I'm aware that EXEC_PATH allows Octave to run the mex file, but it just feels
cleaner if a binary package can be made available in an Octave session with
just one atomic action, an addpath command.
For linux, this is not an issue, since you have the RPATH property for shared
libraries there.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?48511>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #48511] mxe-octave: mex library dependencies not picked up,
Joris Gillis <=