From maintainers-request at octave dot org Wed Sep  8 10:17:00 2004
Subject: Octave compiler
From: "John W. Eaton" <jwe at bevo dot che dot wisc dot edu>
To: Rob Vermaas <robv at cs dot uu dot nl>
Cc: octave maintainers mailing list <maintainers at octave dot org>
Date: Wed, 8 Sep 2004 11:16:04 -0400

On  8-Sep-2004, Rob Vermaas <robv at cs dot uu dot nl> 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

?

jwe