VS Code extensions have the same problem as any other extension: if you look at the repository and see what is required to install and run the extension? You'll probably never install an extension again. That is why if you're going to be forced to pay $5k for a proprietary tool, it has to be justified in other ways than "it can get the job done". The work-around is to use OS tools to remove Matlab and other proprietary tools from the loop entirely. They do have a free RTE but you still need some form of Matlab IDE to write in plus the Matlab Compiler toolbox to build the project out for the RTE. I suspect that you're right, and it comes down to a choice between embedding "foreign" code into an m-file, or making calls to the matlab engine from within a foreign IDE.
because at some point you need at least ONE working matlab install just to develop the m-file :) You can then run the C/C++ code from within the long discourse is necessary, because having the extension without a valid MATLAB license+installation won't work.T"
Thus no, you cannot execute MATLAB code directly within VSCode, you can only covertly call the MATLAB engine from inside VSCode.Ī possible workaround would be to export your MATLAB code to C/C++ using the MATLAB Coder. You might be able to get other IDEs to have syntax highlighting and typing-hints like MATLAB's own IDE through importing its mlint functionality, like you did, but that won't execute the code. Without a working, licensed MATLAB installation you cannot run MATLAB code.Īs MATLAB is proprietary, there are only two ways to run MATLAB code: by running the code from the MATLAB IDE (with a valid license of course), or by compiling it to an executable file with the MATLAB compiler. It does not invalidate the below though you need to have a working, licensed MATLAB installation, which will be called in the background. There is a way, this VSCode extension suggests that you can use it to run MATLAB code from within VSCode without having to open the MATLAB GUI.
0 kommentar(er)
