deploytool (2016a) stalling when opening projects?
1 Ansicht (letzte 30 Tage)
Ältere Kommentare anzeigen
When I try to open an existing *.prj (deploytool application) in 2016a, MATLAB stalls and will not open the project. The project is largish but opens fine in 2015b. The source code is sitting in a large directory structure, is this the problem?
0 Kommentare
Antworten (1)
Krishna Chaitanya Duggineni
am 16 Mai 2016
Source code location should not be a problem. Try the following troubleshooting steps
1) Is this delay specific to one project ? Can you open a project normally if it is a simple standalone executable ?
If your answers to the above questions are not true then try the step below.
2) 'deploytool projectname' will checkout a compiler license before opening deploytool. So, see if the license checkout is causing the MATLAB to lag. To do this, do
>> edit deploytool.m
put breakpoints in the code, then do
>> deploytool projectname
Step through the code. Identify which part of the code is taking more time.
2 Kommentare
Krishna Chaitanya Duggineni
am 20 Mai 2016
I am not aware of any report that MATLAB R2016a is slow while accessing networks locations. Ideally MATLAB R2016a's performance in this regard should be either the same or better than R2015b.
Perhaps, it is a good idea to create a case with Mathworks Technical Support at this point. You can do so by creating a service request from the link below.
Siehe auch
Produkte
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!