Thread Subject: Problems linking MEX'ed object files.

Subject: Problems linking MEX'ed object files.

From: Nicolai Brejnholt

Date: 30 Apr, 2007 05:36:27

Message: 1 of 9

Hello
First of all, should mention that I'm using MATLAB 6.5 release 13.
I'm trying to MEX some C-code. For this purpose, I've written the
proper interface. I found out early on, that the lcc C version 2.4
included with MATLAB 6.5, was outdated for my purpose. Therefore I
switched to MCSV6.0 (and also installed Watcom 10.6). If I use the -c
(compile only) option, I can compile my code fine to .obj's. IF I try
to link it however, I get this:

Warning: Ignoring invalid option
'LIBPATH:"C:\MATLAB6p5\extern\lib\win32\microsoft\msvc60"
Warning: Cannot locate 'libmx.lib'; skipping -- fuzzy name matching
may not work
Warning: Cannot extract external symbols from 'libmx.lib' -- fuzzy
linking may not work
----same warning repeats for the 3 other files needed (libmex.lib,
libmatlb.lib and libmat.lib)----
Warning! EW1008: cannot open libmx.lib : No such file or directory
----same warning repeats for the 3 other files needed----
Error! E2028: mxGetNumberofElements_ is an undefined reference
----same error repeats for the other mx-types I use----

It doesn't take a genius to see what happens, but why? The needed
files ARE located in the LIBPATH path, so why does it "ignore invalid
option"?

Also, if I try to use Watcom to link it, I get the same problem
(albeit in less details. It just tells me, that the references are
undefined).

And while we are at it. It also fails to include a .lib file, that I
added to my compilation. I've tried adding it after my .c-files
simply as libname.lib and also tried adding it, when simply linking
the objects. Doesn't use it.

Subject: Problems linking MEX'ed object files.

From: Nicolai Brejnholt

Date: 3 May, 2007 10:09:23

Message: 2 of 9

Wonder if it's allowed to bump posts?

Anyway, I added the .lib files to the list in my mexopts .bat file
and put the .bat file in the library where I link my objects. It now
finds .lib files, but it still doesn´t recoignize the functions. I
get:

Error! E2028: mxGetNumberOfElements_ is an undefined reference
Error! E2028: mxCalloc_ is an undefined reference
Error! E2028: mxGetString_ is an undefined reference
Error! E2028: mexWarnMsgTxt_ is an undefined reference
Error! E2028: ffiopn_ is an undefined reference
Error! E2028: ffgipr_ is an undefined reference
Error! E2028: ffgics_ is an undefined reference
Error! E2028: ffgpv_ is an undefined reference
Error! E2028: ffclos_ is an undefined reference
Error! E2028: ffwldp_ is an undefined reference
Error! E2028: fftplt_ is an undefined reference
Error! E2028: ffmnhd_ is an undefined reference
Error! E2028: ffukyj_ is an undefined reference
Error! E2028: ffukye_ is an undefined reference
Error! E2028: LoadElt_ is an undefined reference
Error! E2028: ffopentest_ is an undefined reference
Error! E2028: ffgnrw_ is an undefined reference
Error! E2028: ffukys_ is an undefined reference
Error! E2028: ffrprt_ is an undefined reference
Error! E2028: ffrsim_ is an undefined reference
Error! E2028: ffppre_ is an undefined reference
Error! E2028: ffgtvf_ is an undefined reference
Error! E2028: ffghdn_ is an undefined reference
Error! E2028: ffthdu_ is an undefined reference
Error! E2028: ffgkys_ is an undefined reference
Error! E2028: ffcmsg_ is an undefined reference
Error! E2028: ffcopy_ is an undefined reference
Error! E2028: ffmahd_ is an undefined reference
Error! E2028: ffgkye_ is an undefined reference
Error! E2028: ffgtam_ is an undefined reference
Error! E2028: ffgtnm_ is an undefined reference
Error! E2028: GetValInTable_ is an undefined reference
Error! E2028: erf_ is an undefined reference
Error! E2028: ffgerr_ is an undefined reference
Error! E2028: ffgmsg_ is an undefined reference
Error! E2028: ffpmsg_ is an undefined reference
Error! E2028: setall_ is an undefined reference
Error! E2028: ignlgi_ is an undefined reference
Error! E2028: rint_ is an undefined reference
Error! E2028: ffgcv_ is an undefined reference
Error! E2028: ffpcn_ is an undefined reference
Error! E2028: ffpdat_ is an undefined reference
Error! E2028: ffgstm_ is an undefined reference
Error! E2028: ffphis_ is an undefined reference
Error! E2028: ffukls_ is an undefined reference
Error! E2028: ffuky_ is an undefined reference
Error! E2028: ffgcvd_ is an undefined reference
Error! E2028: ffukyd_ is an undefined reference
Error! E2028: ffpunt_ is an undefined reference
Error! E2028: ffghsp_ is an undefined reference
Error! E2028: ffgrec_ is an undefined reference
Error! E2028: ffgnxk_ is an undefined reference
Error! E2028: ffflus_ is an undefined reference
Error! E2028: ffflnm_ is an undefined reference
Error! E2028: ffgtcl_ is an undefined reference
Error! E2028: ffgcnn_ is an undefined reference
Error! E2028: ffgkyn_ is an undefined reference
Error! E2028: ffgkyj_ is an undefined reference
file grimex.obj(C:\MATLAB6p5\work\grimex\grimex.c): undefined symbol
mxGetNumberOfElements_
file grimex.obj(C:\MATLAB6p5\work\grimex\grimex.c): undefined symbol
mxCalloc_
file grimex.obj(C:\MATLAB6p5\work\grimex\grimex.c): undefined symbol
mxGetString_
file grimex.obj(C:\MATLAB6p5\work\grimex\grimex.c): undefined symbol
mexWarnMsgTxt_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffiopn_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffgipr_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffgics_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffgpv_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffclos_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffwldp_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol fftplt_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffmnhd_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffukyj_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffukye_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol LoadElt_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffopentest_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffgnrw_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffukys_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffrprt_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffrsim_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffppre_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffgtvf_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffghdn_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffthdu_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffgkys_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffcmsg_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffcopy_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffmahd_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffgkye_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffgtam_
file GRILib_DataIO.obj(C:\MATLAB6p5\work\grimex\GRILib_DataIO.c):
undefined symbol ffgtnm_
file GRILib_LensSimu.obj(C:\MATLAB6p5\work\grimex\GRILib_LensSimu.c):
undefined symbol GetValInTable_
file GRILib_LensSimu.obj(C:\MATLAB6p5\work\grimex\GRILib_LensSimu.c):
undefined symbol erf_
file GRILib_LensSimu.obj(C:\MATLAB6p5\work\grimex\GRILib_LensSimu.c):
undefined symbol ffwldp_
file GRI_BuildLens.obj(C:\MATLAB6p5\work\grimex\GRI_BuildLens.c):
undefined symbol LoadElt_
file GRI_BuildLens.obj(C:\MATLAB6p5\work\grimex\GRI_BuildLens.c):
undefined symbol ffukye_
file GRI_BuildLens.obj(C:\MATLAB6p5\work\grimex\GRI_BuildLens.c):
undefined symbol ffclos_
file GRILib_Errors.obj(C:\MATLAB6p5\work\grimex\GRILib_Errors.c):
undefined symbol ffgerr_
file GRILib_Errors.obj(C:\MATLAB6p5\work\grimex\GRILib_Errors.c):
undefined symbol ffgmsg_
file GRILib_Errors.obj(C:\MATLAB6p5\work\grimex\GRILib_Errors.c):
undefined symbol ffpmsg_
file GRILib_Errors.obj(C:\MATLAB6p5\work\grimex\GRILib_Errors.c):
undefined symbol ffcmsg_
file GRILib_Math.obj(C:\MATLAB6p5\work\grimex\GRILib_Math.c):
undefined symbol setall_
file GRILib_randlib.obj(C:\MATLAB6p5\work\grimex\GRILib_randlib.c):
undefined symbol ignlgi_
file GRILib_SpcTools.obj(C:\MATLAB6p5\work\grimex\GRILib_SpcTools.c):
undefined symbol rint_
file GRILib_SpcTools.obj(C:\MATLAB6p5\work\grimex\GRILib_SpcTools.c):
undefined symbol LoadElt_
file GRILib_SpcTools.obj(C:\MATLAB6p5\work\grimex\GRILib_SpcTools.c):
undefined symbol GetValInTable_
file GRILib_SpcTools.obj(C:\MATLAB6p5\work\grimex\GRILib_SpcTools.c):
undefined symbol erf_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffgcv_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffpcn_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffukys_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffpdat_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffgstm_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffphis_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffukls_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffukye_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffgerr_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffcmsg_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffuky_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffghdn_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffthdu_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffmahd_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffcopy_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffgcvd_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffukyd_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffpunt_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffpmsg_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffghsp_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffgrec_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffgnxk_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffflus_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffflnm_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffgkys_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffgnrw_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffgtcl_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffgcnn_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffgkyn_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffgkyj_
file
GRILib_FitsTools.obj(C:\MATLAB6p5\work\grimex\GRILib_FitsTools.c):
undefined symbol ffmnhd_

Which is basicly ALL the functions defined in the .lib files as well
as a few defined in code and included (without giving warnings during
compilation)

Subject: Problems linking MEX'ed object files.

From: Tom Clark

Date: 3 May, 2007 11:19:38

Message: 3 of 9

Hi,

I have had a problem similar to yours; although using Intel Fortran
compiler. I couldn't get it to recognise linked objects.

I found it to be sensitive to the order in which files were specified
in the mex command:

i used (e.g)
mex -g pvl.f forces.f dmods.f

which wouldn't link the modules contained in dmods.f which are used
in pvl.f

In the end, I used
mex -g dmods.f pvl.f forces.f
to create intermediate objects with the mex compiler, then the
original command:
mex -g pvl.f forces.f dmods.f
and this worked fine.

I'm not a specialist; so am sorry if this is incorrect- but it might
be worthwhile trying!

good luck!

Subject: Problems linking MEX'ed object files.

From: Nicolai Brejnholt

Date: 4 May, 2007 12:13:25

Message: 4 of 9

Tom Clark wrote:
> I found it to be sensitive to the order in which files were
> specified
> in the mex command:

Hi

I tried rearranging the files in a way that made sense (given from
what functions it seemed to be missing and where these were located),
but it made no difference. Then I just tried arranging them randomly
and again, it made no impact (except on the order in which they are
displayed in the error log:p ).
Could be that there is a magical way of arranging them, but if it is
truely so random, I guess I am out of look, seeing as I have more
than 10 files. (Which means I can arrange them in 10! different ways,
I guess.)

Subject: Problems linking MEX'ed object files.

From: Nicolai Brejnholt

Date: 4 May, 2007 16:44:00

Message: 5 of 9

Well, turns out it is MATLAB 6.5 release 13, which is unable to use
newer compiler/linkers appearently. To explain:

[1] Borland C/C++ version 5.0 in C:\BC5
[2] Digital Visual Fortran version 6.0 in C:\Program Files\Microsoft
Visual Studio
[3] Lcc C version 2.4 in C:\MATLAB6P5\sys\lcc
[4] Microsoft Visual C/C++ version 6.0 in C:\Program Files\Microsoft
Visual Studio
[5] WATCOM C/C++ version 10.6 in C:\WATCOM

If I use the default (lcc) or the Borland (which is from, what,
1995ish?) I can mex yprime.c (example included with MATLAB). If I use
MSVC or WATCOM (both of which are only a few years old) I get the
exact same errors trying to mex yprime.c, as I do when trying to mex
my own large collection of code.

MSVC:
Warning: Ignoring invalid option
'LIBPATH:"C:\MATLAB6p5\extern\lib\win32\microsoft\msvc60"'
Warning: Cannot locate 'libmx.lib'; skipping -- fuzzy name matching
may not work
Warning: Cannot extract external symbols from 'libmx.lib' -- fuzzy
linking may not work
Warning: Cannot locate 'libmex.lib'; skipping -- fuzzy name matching
may not work
Warning: Cannot extract external symbols from 'libmex.lib' -- fuzzy
linking may not work
Warning: Cannot locate 'libmatlb.lib'; skipping -- fuzzy name
matching may not work
Warning: Cannot extract external symbols from 'libmatlb.lib' -- fuzzy
linking may not work
Warning: Cannot locate 'libmat.lib'; skipping -- fuzzy name matching
may not work
Warning: Cannot extract external symbols from 'libmat.lib' -- fuzzy
linking may not work
Warning: Cannot locate 'cfitsio.lib'; skipping -- fuzzy name matching
may not work
Warning: Cannot extract external symbols from 'cfitsio.lib' -- fuzzy
linking may not work
Warning! W1008: cannot open libmx.lib : No such file or directory
Warning! W1008: cannot open libmex.lib : No such file or directory
Warning! W1008: cannot open libmatlb.lib : No such file or directory
Warning! W1008: cannot open libmat.lib : No such file or directory
Warning! W1008: cannot open cfitsio.lib : No such file or directory
Error! E2028: mexWarnMsgTxt_ is an undefined reference
Error! E2028: mexErrMsgTxt_ is an undefined reference
Error! E2028: mxGetM_ is an undefined reference
Error! E2028: mxGetN_ is an undefined reference
Error! E2028: mxIsDouble_ is an undefined reference
Error! E2028: mxIsComplex_ is an undefined reference
Error! E2028: mxCreateDoubleMatrix_ is an undefined reference
Error! E2028: mxGetPr_ is an undefined reference
file yprime.obj(C:\MATLAB6p5\extern\examples\mex\yprime.c): undefined
symbol mexWarnMsgTxt_
file yprime.obj(C:\MATLAB6p5\extern\examples\mex\yprime.c): undefined
symbol mexErrMsgTxt_
file yprime.obj(C:\MATLAB6p5\extern\examples\mex\yprime.c): undefined
symbol mxGetM_
file yprime.obj(C:\MATLAB6p5\extern\examples\mex\yprime.c): undefined
symbol mxGetN_
file yprime.obj(C:\MATLAB6p5\extern\examples\mex\yprime.c): undefined
symbol mxIsDouble_
file yprime.obj(C:\MATLAB6p5\extern\examples\mex\yprime.c): undefined
symbol mxIsComplex_
file yprime.obj(C:\MATLAB6p5\extern\examples\mex\yprime.c): undefined
symbol mxCreateDoubleMatrix_
file yprime.obj(C:\MATLAB6p5\extern\examples\mex\yprime.c): undefined
symbol mxGetPr_

WATCOM:

Error! E1073: Invalid option '-7'
Error: Compiler returned a bad status compiling "yprime.c"
 
  C:\MATLAB6P5\BIN\WIN32\MEX.PL: Error: Compile of 'yprime.c' failed.

Subject: Problems linking MEX'ed object files.

From: Nicolai Brejnholt

Date: 4 May, 2007 16:46:37

Message: 6 of 9

(Ah, btw, worth to mention, that I need the newer compilers/linkers
to use the code at all. Several newer types etc. used in it. So any
help would still be highly sought after.)

Subject: Problems linking MEX'ed object files.

From: Martin Ozimek

Date: 20 Jun, 2007 09:30:46

Message: 7 of 9

Are you sure that something like Borland c++ can't get it done? I
had this same problem as you. I have Visual Studio.net 2005 and it
is not compatabile with current versions of Matlab as far as I know.
I ended up finding a free version of the Borland c++ compiler. (I
googled free borland c++ builder). Now obviously we may be compiling
different codes, but if nothing else is working it may be worth a
shot. All of my files are now compiling, since previously, I only
had the internal lcc compiler which will not even compile a *.cpp
file. Well you said *any* help would be sought after, so I'm not
sure this was much, but it's an attempt.

Good luck,

Marty

Nicolai Brejnholt wrote:
>
>
> (Ah, btw, worth to mention, that I need the newer compilers/linkers
> to use the code at all. Several newer types etc. used in it. So any
> help would still be highly sought after.)

Subject: Problems linking MEX'ed object files.

From: Eric Sampson

Date: 20 Jun, 2007 12:07:46

Message: 8 of 9

Martin Ozimek wrote:
>
>
> Are you sure that something like Borland c++ can't get it done? I
> had this same problem as you. I have Visual Studio.net 2005 and it
> is not compatabile with current versions of Matlab as far as I
> know.
> I ended up finding a free version of the Borland c++ compiler. (I
> googled free borland c++ builder). Now obviously we may be
> compiling
> different codes, but if nothing else is working it may be worth a
> shot. All of my files are now compiling, since previously, I only
> had the internal lcc compiler which will not even compile a *.cpp
> file. Well you said *any* help would be sought after, so I'm not
> sure this was much, but it's an attempt.
>
> Good luck,
>
> Marty
>

Martin, Microsoft Visual C++ 2005 has been supported since MATLAB 7.2
(R2006a), which was released in March of 2006.

Sincerely,
Eric Sampson
The MathWorks, Inc.

Subject: Problems linking MEX'ed object files.

From: Martin Ozimek

Date: 20 Jun, 2007 12:17:11

Message: 9 of 9

Eric Sampson wrote:
>
>
> Martin Ozimek wrote:
>>
>>
>> Are you sure that something like Borland c++ can't get it done?
> I
>> had this same problem as you. I have Visual Studio.net 2005
and
> it
>> is not compatabile with current versions of Matlab as far as I
>> know.
>> I ended up finding a free version of the Borland c++ compiler.
> (I
>> googled free borland c++ builder). Now obviously we may be
>> compiling
>> different codes, but if nothing else is working it may be worth
a
>> shot. All of my files are now compiling, since previously, I
> only
>> had the internal lcc compiler which will not even compile a
*.cpp
>> file. Well you said *any* help would be sought after, so I'm
not
>> sure this was much, but it's an attempt.
>>
>> Good luck,
>>
>> Marty
>>
>
> Martin, Microsoft Visual C++ 2005 has been supported since MATLAB
> 7.2
> (R2006a), which was released in March of 2006.
>
> Sincerely,
> Eric Sampson
> The MathWorks, Inc.
  
Well let me be more clear, my Matlab version is 7.0, and I'm unable
to run Visual Studio.net 2005 through the mex interface, so I was
just going with my own personal experience and not making a company
claim here.

Tags for this Thread

Add a New Tag:

Separated by commas
Ex.: root locus, bode

What are tags?

A tag is like a keyword or category label associated with each thread. Tags make it easier for you to find threads of interest.

Anyone can tag a thread. Tags are public and visible to everyone.

rssFeed for this Thread
 

MATLAB Central Terms of Use

NOTICE: Any content you submit to MATLAB Central, including personal information, is not subject to the protections which may be afforded information collected under other sections of The MathWorks, Inc. Web site. You are entirely responsible for all content that you upload, post, e-mail, transmit or otherwise make available via MATLAB Central. The MathWorks does not control the content posted by visitors to MATLAB Central and, does not guarantee the accuracy, integrity, or quality of such content. Under no circumstances will The MathWorks be liable in any way for any content not authored by The MathWorks, or any loss or damage of any kind incurred as a result of the use of any content posted, e-mailed, transmitted or otherwise made available via MATLAB Central. Read the complete Terms prior to use.

Contact us at files@mathworks.com