[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: oct (and mex) files for different architectures

From: Richard Crozier
Subject: Re: oct (and mex) files for different architectures
Date: Mon, 12 Sep 2011 14:37:06 +0100
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv: Gecko/20100713 Lightning/1.0b2 Thunderbird/3.1.1

 On 12/09/2011 14:30, Jordi Gutiérrez Hermoso wrote:
> On 12 September 2011 08:14, Richard Crozier <address@hidden> wrote:
>> On Matlab, I can compile several different mex files for different machine
>> architectures and Matlab will call the appropriate one for the local setup.
>> The compiled mex files are given appropriate extensions e.g. mexa64 for
>> 64bit linux, mexglx for 32 bit linux, mexw32 for 32 bit windows etc.
>> Is the equivalent possible for oct files (or mex files created in Octave)?
> Not currently, no. I find that putting the architecture in the
> filename extension is a little weird to begin with. Why don't you see
> .exe64 and .exe extensions for Windows executables? Can't you just
> recompile and distribute your oct files for the architecture you need
> them? I get the feeling that Matlab lets you do that because people
> don't like recompiling and/or don't like source code.
> - Jordi G. H.

I have matlab instances running on several different platforms all
accessing the same code directory simultaneously (hosted on a SAMBA file
share). If I recompiled the source, I would need a new directory for the
mex file for that machine and would have to tell the matlab instance on
that machine to access that mex file rather than another mex file in the

The matlab way lets me have one directory for the C/C++/Fortran code and
compile my mex file in that directory without fiddling with the path
etc. If there's a better way which does not involve my copying my entire
matlab path to a local directory on every machine I'd consider it.

The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]