Why do only two .c files from libsvm compile to mex files?

Question

craig 2015-8-6

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/232701-why-do-only-two-c-files-from-libsvm-compile-to-mex-files

评论： Konstantina Tsekoura 2018-4-21

I am using MATLAB 2015a and have loaded libsvm 3.20. Following the instructions in README only libsvmread and libsvmwrite are changed to .mexw64 files. Here is what I have done:

>>make
Building with 'Microsoft Windows SDK 7.1 (C)'.
MEX completed successfully.
Building with 'Microsoft Windows SDK 7.1 (C)'.
MEX completed successfully.
If make.m fails, please check README about detailed instructions.
>>mex -setup
MEX configured to use 'Microsoft Windows SDK 7.1 (C)' for C language compilation.
Warning: The MATLAB C and Fortran API has changed to support MATLAB
   variables with more than 2^32-1 elements. In the near future
   you will be required to update your code to utilize the
   new API. You can find more information about this at:
   http://www.mathworks.com/help/matlab/matlab_external/upgrading-mex-files-to-use-64-bit-api.html.
To choose a different language, select one from the following:
mex -setup C++ 
mex -setup FORTRAN

The above is what I see when I follow the README instructions. And only two of the files are compiled to .mexw64. I have all the up to date SDK and .NET programs installed on Windows 8.1. If I select C++ I have the same problem. Please advise.

1 个评论
显示 -1更早的评论隐藏 -1更早的评论

Omar 2016-2-11

Hi Craig, I have the same problem. Did you manage to resolve it? Thanks!

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Walter Roberson 2015-8-7

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/232701-why-do-only-two-c-files-from-libsvm-compile-to-mex-files#answer_188535

Hypothetically, two (or even one) mex* could be enough: each .mex* file is an object library, the equivalent of a dll if it needs to be, so all of the *.c could compile and link together into a small number of object libraries.