Work around for Visual Studio manifest permission denied error?
33 Ansichten (letzte 30 Tage)
Ältere Kommentare anzeigen
I am also experiencing the issue asked here: https://www.mathworks.com/matlabcentral/answers/807892-mt-general-error-c101008d-failed-to-write-the-updated-manifest-to-the-resource-of-file-_ssf-m
In a nutshell, when compiling mex files or building simulink accelerator targets, Visual Studio linker can fail with a message like
mt : general error c101008d: Failed to write the updated manifest to the resource of file "<...>_msf.mexw64". Access is denied.
Some googling of this issue seems to blame anti-virus software, as does the above answer. However, in a corporate environment, uninstalling/disabling anti-virus software is not an option. I did notice that VS has an option to disable manifest generation by specifying the /MANIFEST:NO command line option to mt.exe.
I wonder if it's possible to configure Matlab/Simulink to provide /MANIFEST:NO linker option for mex file builds and/or simulink accelerator targets? Would this cause problems in calling the mex-files?
References:
2 Kommentare
Karl Molnar
am 31 Jan. 2022
I'm using R2021b, and in the file: C:\Users\XXX\AppData\Roaming\MathWorks\MATLAB\R2021b\mex_C++_win64.xml, delete the mt command. Creating the manifest file isn't the problem. The manifest file is being created, but denied to be incorporated into the mex file. You can see the compile/linker info using the -v mex option.
Antworten (1)
Benjamin Thompson
am 31 Jan. 2022
See this example in the help on mex:
mex -v COMPFLAGS="$COMPFLAGS -Wall" yprime.c
Try adding /MANIFEST:NO inside the double quotes. Or maybe -MANIFEST:NO. Not sure.
0 Kommentare
Siehe auch
Kategorien
Mehr zu Introduction to Installation and Licensing finden Sie in Help Center und File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!