help-octave
[Top][All Lists]
Advanced

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

Re: producing a self-standing program


From: c.
Subject: Re: producing a self-standing program
Date: Wed, 5 Sep 2012 10:37:38 +0200

On 5 Sep 2012, at 09:57, Laurent Hoeltgen wrote:

> On 05/09/12 07:04, Yury T. wrote:
>> Hi all
>> 
>> Is it possible to produce a self-standing linux executable from octave
>> script, which would use and enclose in itself one of the octave-only
>> parallel solutions (most likely I wouldn't need any fancy parallelization)?
>> 
>> I'd want to run my program on 'foreign' cluster, on which I'm unsure I'd be
>> able to permanently keep >1G of octave binaries, and in fact, I'm reluctant
>> to undertake the compilation itself there.
>> 
>> Is it doable at all or partly only?
>> 
>> 
>> 
>> --
>> View this message in context: 
>> http://octave.1599824.n4.nabble.com/producing-a-self-standing-program-tp4643715.html
>> Sent from the Octave - General mailing list archive at Nabble.com.
>> _______________________________________________
>> Help-octave mailing list
>> address@hidden
>> https://mailman.cae.wisc.edu/listinfo/help-octave
>> 
> 
> Hi,
> 
> As far as I know, you can't produce self-standing executables with octave.

you can but you will have to write at least parts of it using Octave's C++ API.
Have a look at "mkoctfile" in the manual, specifically at the option 
"--link-stand-alone".
But even if you do manage to have it all statically linked (which is an 
absolutely non trivial task)
youll'end up whith a file that is the same size as the full Octave installation.
So to put it in short, it might be possible but I really don't see the point in 
doing such a thing.

> However, you can write scripts using the usual shebang notation
> 
> #! /bin/octave
> 
> as the first line of your script. These scripts can then be simply run from a 
> terminal. Of course, this requires octave to be installed on the machine that 
> you are running the script.
> 
> Regards,
> Laurent


c.

reply via email to

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