simulink not recoginzing nmake when using convhulln

20 vues (au cours des 30 derniers jours)
Daniel Delannes-molka
Daniel Delannes-molka le 10 Juil 2023
But was unique enough to merit its own post.
In short, i'm running a very simple .slx model (seen in attachments) to test out convhulln but its stating that: 'nmake' is not recognized as an internal or external command, operatable program or batch file.
I ran mex -setup and got : MEX configured to use 'Microsoft Visual C++ 2022' for C++ language compilation.
This problem is appearing in simulink simulation and hardware mode but if put in a .m file and run, the issue is no longer there. Even stranger, if convhulln is removed then it runs without issue. Any idea what is going on?

Réponse acceptée

Angelo Yeo
Angelo Yeo le 11 Juil 2023
Hi Daniel,
  1. I cannot reproduce your issue as I can run simulation for the given model. I also was able to build C++ code by changing the target tlc file to ert.tlc (I don't have your tlc files) and some configuration parameters.
  2. From your error message stating "'nmake' is not recognized", I believe the path to Visual Studio's nmake.exe is not added to your system environment path. One thing you can try is to include the path of "nmake.exe" into system environment path. For example, C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin
  3. If another error message follows like "Error: cannot determine the location of the VS common Tools folder", then adding the following path to the PATH environment can be helpful: C:\windows\system32
FYI, see what C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin has.
  1 commentaire
Daniel Delannes-molka
Daniel Delannes-molka le 11 Juil 2023
That seems to have been the issue, I think its fixed.
My enviromental variable path includes the following relevent links in this order:
C:\Windows\System32
C:\Windows\System32
C:\Program Files\Microsoft Visual Studio\2022\Community\VC
As an addional note, I was doing a clean reinstallion of my visual studio installation and deleted C:\Program Files (x86)\Microsoft Visual Studio 14.0, which broke a system variable VS140COMNTOOLS : C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools\.
I suspect that it was trying to find nmake via this path(that no longer existed) instead of using the fresh installation.
Thank you!

Connectez-vous pour commenter.

Plus de réponses (0)

Tags

Produits


Version

R2022b

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by