Re: Octave compiler

[Rob Vermaas]

Hi John,

John W. Eaton wrote:

> On  8-Sep-2004, Rob Vermaas <address@hidden> wrote:
>
> | That said, I have a small feature-request (sorry if this is the wrong 
> | list to post this on). We are using mkoctfile in the back-end of the 
> | compiler. At the moment I'm patching mkoctfile manually to allow .oct 
> | files to be passed as object files when compiling a stand-alone 
> | application. I was wondering if it is possible to add this to the 
> | mkoctfile in Octave itself, or are there any objections to this? I have 
> | attached a patch to this email.
>
> Why is this needed?  A .oct file is not an object file.  It is usually
> a shared library object, and it is intended to be loaded by dlopen (or
> a similar mechanism).
>
> If you want to link in the code for a .oct file directly to an
> application, wouldn't it make more sense to do something like
>
>  mkoctfile -c my_oct_file.cc
>  mkoctfile [other options and files] my_oct_file.o
>
>  
The issue was that I wanted to be able to use existing dld-function/.oct 
files (e.g. the ones from octave, or any other in the path) without 
having to recompile them, basically. And as I was able to use them to 
link the compiled program against, I have chosen this option. What would 
be the advantages of loading them dynamically instead?

greetings,
Rob Vermaas