Mex 'include' path merged with working directory path

Question

John Anderson 2019-2-8

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/443823-mex-include-path-merged-with-working-directory-path

评论： Walter Roberson 2019-2-8

I am attempting to compile a mex function. For some reason, the 'include' path I specify gets merged into my current working directory path. I don't recall seeing this before, although I spend most of my time in Linux and am working short-term on a Windows machine.

Below is the error message I get. Note that the line that is cited in error has the correct path but it is somehow interpreted to the wrong path.

Error using mex

C:\Users\john.anderson\Documents\MATLAB_Toolboxes\KWtools\TestPost\Matlab_mexa64\source\Files\Altair\2017\hm\include\ not found;

check that you are in the correct current folder, and check the spelling of

'C:\Users\john.anderson\Documents\MATLAB_Toolboxes\KWtools\TestPost\Matlab_mexa64\source\Files\Altair\2017\hm\include\'.

Error in makemex64 (line 30)

mex -v CC=g++ -O -DSNPRINTF=snprintf -IC:\Program Files\Altair\2017\hm\include\ ./RunHyper.c ...

0 个评论
显示 -2更早的评论隐藏 -2更早的评论

请先登录，再进行评论。

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

Answer 1

Walter Roberson 2019-2-8

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/443823-mex-include-path-merged-with-working-directory-path#answer_360072

在 MATLAB Online 中打开

 mex -v CC=g++ -O -DSNPRINTF=snprintf -IC:\Program Files\Altair\2017\hm\include\        ./RunHyper.c ...

means

mex ...
    -v ...
    CC=g++ ...
    -O ...
    -DSNPRINTF=snprintf ...
    -IC:\Program ...
    Files\Altair\2017\hm\include\ ...
    ./RunHyper.c ...

where each of those is a separate input argument.

The space in the directory name is confusing it.

You should be using

-I"C:\Program Files\Altair\2017\hm\include\"

but since some of that part is automatically generated, it sometimes is not worth fighting it to force it to generate quotes at the proper places. Much of the time it turns out to be easier to move include directories and libraries to paths that do not include spaces (or non-ANSII characters for that matter.)

2 个评论
显示无隐藏无

John Anderson 2019-2-8

Ah, yes. Those pesky blanks in Windows directory names. Another reason I usually dwell in Linux. I put my stuff in a directory without spaces in the path and it works fine now. Thanks for your help!

Walter Roberson 2019-2-8

Linux is even worse, with / and null being the only characters forbidden in a filename -- but Linux shell script programmers have been burned often enough that they routinely put in quotes.

No, it turns out that mex.m is badly programmed, and although it accepts separated arguements, it slams tokens together into one long character vector and system()'s it, without bothering to put in protective quotes where appropriate :( :(

请先登录，再进行评论。