🚀 go-pugleaf

Hello,

I know I can call the matlab engine from C/C++
using:

    gcc -o engdemo \
    -I/opt/matlab13/extern/include \
    engdemo.c \
    -L /opt/matlab13/extern/lib/sol2 \
    -leng /opt/matlab13/bin/sol2 -lmx

But that's really a mouthful.  I'd rather use the
mex script, and specify my own options.  I
compared engopt.sh parameters for linux/gcc
and solaris/SUNspro-cc.  I'll be using specifications
from both parameter sets, since I'm using gcc on
solaris.  Some of the different parameters are easy
to resolve, since they don't necessarily have a
counter part.  The hard differences to resolve are
the -D<NAME>, since they define stuff that is
meant to be recognized inside the source code
(somewhere).

For example, linux/gcc parameters include
-D_GNU_SOURCE in the compile flags,
while the SUNWspro-cc parameters include
-D__EXTENSIONS__ .   Should I include
any/both of these when using gcc on solaris?

What about the linux/gcc -ansi compile flag?
It seems that the SUNWspro-cc counterpart is
one of -Xa, -Xc, -Xs, or -Xt.  But none of
these show up in the SUNWspro-cc compile flags.

Thanks for any wisdom about this.

Fred

-- 
Fred Ma, fma@doe.carleton.ca
Carleton University, Dept. of Electronics
1125 Colonel By Drive, Ottawa, Ontario
Canada, K1S 5B6