Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Matlab R2020b and VisualStudio 2019 #385

Closed
ArLip opened this issue Apr 26, 2021 · 0 comments · Fixed by #595
Closed

Matlab R2020b and VisualStudio 2019 #385

ArLip opened this issue Apr 26, 2021 · 0 comments · Fixed by #595

Comments

@ArLip
Copy link

ArLip commented Apr 26, 2021

While struggling to find the perfect match for the Matlab R2020b and suitable VisualStudio, I stumbled to the following advice by Prakash Devaraju and found it useful (https://se.mathworks.com/matlabcentral/answers/309117-how-to-get-mexcuda-running-compiler-settings?s_tid=srchtitle)
"Just a novice here, got the visual studio compiler to work instead of mingw-w64. It seems the CUDA and compiler have to match. You can downgrade one or upgrade another. Running Matlab R2020b and Visual studio 2019. Visual studio 2013 seems unsupported in R2020b. Installed visual studio 2019 earlier without installing C++ components and mex was defaulting to mingw-w64 compiler. And the latest visual studio installation is too much for a beginner - didn't know which component is required to help the compiler and so selected all the latest versions with C++ and restarted the computer after installing. Now mex -setup gave me the option to choose Microsoft Visual C++ 2019 (C) and now can get to a GUI.
If anyone is trying to use Kilosort GUI for neuropixels with R2020b in Windows 10, try installing visual studio 2019 community with C++ components. Then choose the Visual studio compiler in matlab using mex -setup, followed by mexGUPall.m and kilosort.m"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant