Hi,
I'm not sure if this is the right place to do it but I didn't find anywhere else to report this.
I just installed MGD 2.1.0 and instead of appending it's path to windows PATH it completely rewrote it so now my path only contains MGD installation folder.
Hi philira,
Thanks for your report, this forum is a perfect place to report issues with Mali Graphics Debugger and other tools.
I've just tried to reproduce the problem using Mali Graphics Debugger 2.1.0 on Windows 7 32bit but on my machine everything worked as expected: the path to MGD installation folder was added to the system path.Having said that we have already seen that problem internally, but we are not sure how to reproduce it.Could you please let us know if the problem is reproducible in your setup?What version of Windows are you using?Have you installed/uninstalled any other ARM Mali Tools (e.g. Mali Offline Compiler) on your machine?
Thanks,
Jacek
Hi Jacek,
Thanks for your feedback. I'm running on Windows 7 64-bit.
I had MGD 2.0.1 installed before. I installed MGD 2.1.0 over it (although to a different folder under ARM). I also installed DS-5 Community 5.21.1 64 bit. I'm just not sure if I installed it before or after MGD.
Thanks for the information, I've added it to the internal ticket that tracks this issue.
After a brief investigation we suspect that there is a problem with 3rd party installation framework we are using...
Sorry for the inconvenience caused, we hope to fix the installer soon.Jacek
Once again - thanks for your report, I'm happy to say that the next Mali Graphics Debugger release will have this bug fixed.In the meantime please be aware that the installer may corrupt the PATH environment variable if it is longer than 1k.
Cheers,Jacek