Home / Browse / Octave Forge / Mail / Archive

Octave Forge

Email Archive: octave-dev (read-only)

[OctDev] How to reduce DLL dependencies for mkoctfile --standalone ?

From: Toby <streumix@go...> - 2010-07-15 10:31

Hi,

since I got used to the C++ API during the course of writing my own oct functions,
I've started to make use of the Octave stuff, basically the math classes, for tiny helper
programs running standalone. (Generated via mkoctfile --standalone)

There's no issue with the programming, but with the long list of DLL dependencies of these executables.
A lot of collegues, who do not use Octave or have it installed on their machines, are asking for my tools and I've
started to bundle everything required. Now, the list of DLLs (number, total size,...) is enormous.
Therefore, I'm looking for a way to get dependencies reduced.

Is there a "fully static" Octave for Windows, which allows to link everything statically ?
Did anyone succeed in comiling such a version based on MinGW  ?

As a first step I'm planning to set up a dedicated Octave version, which is used exclusively to compile 
standalone tools based on mkoctfile. My strategie is to strip off unneeded features at configure as much as possible.
Maybe I can go with static versions of  some of the support libs, too.

Is there an easy way to get rid of the interpreter related stuff (causing a bunch of unused dependencies like readline,ncurses, ...).

Any sugestions ?

Toby

Thread View

Thread	Author	Date
[OctDev] How to reduce DLL dependencies for mkoctfile --standalone ?	Toby <streumix@go...>

Re: [OctDev] How to reduce DLL dependencies for mkoctfile --standalone ?

From: Benjamin Lindner <lindnerben@gm...> - 2010-07-15 14:42

> Hi,
> 
> since I got used to the C++ API during the course of writing my own oct
> functions,
> I've started to make use of the Octave stuff, basically the math classes,
> for tiny helper
> programs running standalone. (Generated via mkoctfile --standalone)
> 
> There's no issue with the programming, but with the long list of DLL
> dependencies of these executables.
> A lot of collegues, who do not use Octave or have it installed on their
> machines, are asking for my tools and I've
> started to bundle everything required. Now, the list of DLLs (number,
> total size,...) is enormous.
> Therefore, I'm looking for a way to get dependencies reduced.
> 
> Is there a "fully static" Octave for Windows, which allows to link
> everything statically ?
> Did anyone succeed in comiling such a version based on MinGW  ?

No, I don't know of one. I haven't tried this actually, so I can't tell you if this is possible to do or not. I guess it should be possible. 
You would require all dependency libraries as static libraries, and build octave with static libraries. Then you'll need to build everything against static GCC libraries. You'll then end up with one giant octave.exe executable - in theory.
Or you can build octave's libraries shared and all dependency libraries static.

libraries using configure to build usually have an options --enable-static --disable-shared to get static libraries (Some libraries cannnot be built shared and static at the sme time)
 
> 
> As a first step I'm planning to set up a dedicated Octave version, which
> is used exclusively to compile 
> standalone tools based on mkoctfile. My strategie is to strip off unneeded
> features at configure as much as possible.
> Maybe I can go with static versions of  some of the support libs, too.
> 
> Is there an easy way to get rid of the interpreter related stuff (causing
> a bunch of unused dependencies like readline,ncurses, ...).

there is a --disable-readline option to octave's configure
See configure --help for options

benjamin

-- 
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01