Re: Mkoctfile, need dynamic linking even for compiling a .cc file?

[Paul Kienzle]

On Jan 13, 2004, at 11:55 PM, Henry F. Mollet wrote:

> Many thanks. These .oct files are very large!?

I solved that problem on windows by making a dynamic version
of libstdc++ (with lots of help).  Anyone care to take this on
for os x?

> Probably should rename the first one to MyHell.oct.

MyHell.oct must have the function FMyHell in it for the loader
to find it.  You can't rename the oct-file without changing the
name of the DEFUN_DLD in the .cc file.

> As you explained earlier, even if I had oregonator.m in the same 
> directory,
> oregonator.oct would be used. I saw no difference in speed when running
> oregegonator.m but I would have to incorporate cputime () into the 
> files
> because both are completed so quickly.

You won't see major gains until you move for-loops out
of octave and into C++.  Often you can do well enough
just by vectorizing loops, but some loops can't be
vectorized.

Paul Kienzle
address@hidden



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------