🚀 go-pugleaf

Cheryl Jones wrote:

> The gccopts for sol2 in R13 uses the compiler to link.  It is always
> better to use the compiler to link because only the compiler knows what
> libraries it wants to link against.
>
> The map file shipped with MATLAB is used to mark only the functions
> mexFunction and mexVersion as accessible from outside the MEX
> executable.  It does not affect runtime at all.  You can successfully
> build MEX-files without using it.

I need the mexFunction gateway function.  I guess one could do
without it, if one were a guru in under-the-hood details of interfacing
matlab and C/C++, so that excludes me.

> On Solaris, you can build shared libraries that are not pic but in the
> distant past I have gotten into trouble with them so since that time,
> MEX-files by default are built pic.  SUN's always builds their own
> shared libraries as pic.

Yes, I was thinking of PIC and shared libraries as synonymous,
even though I am told that they are not.  I'm not too interested in
their differences, I was just curious about whether my code will
run any slower when compiled via the mex way, but I'll find out
once I've finished recoding (getting familiar with passing/returning
structs and extracting parameters, changing all references to
cout and cerr to use matlab printing functions, changing all
exit(EXIT_FAILURES) to throws that are caught by my toplevel
function, etc..).  I was hoping to get an idea of whether the interfacing
was all worth it, since my matlab modules only do graphing to
monitor progress, and digesting results returned by many runs of
my C++ number cruncher.  Responses in the other newsgroups
seem to indicate that PIC doesn't adversely affect speed.

Fred