Well, I was coming here to say that I installed a vanilla Windows 7 on another machine, installed VS2010, then VS2010 SP1, then installed Nsight Tegra, and finally got NVNDK with 4.7.2.
So just for you, I checked on my main machine: “C:\Program Files (x86)\NVIDIA Corporation\Nsight Tegra 1.1\NVPACK” contained “android-ndk-r8d.exe” and “ndk-uninstall.bat”, but no r8d or 4.7.2 folders existed anywhere else. I’m running an administrator account, the permission settings on the folder tree and files show full control for admins, and I don’t have any policies other than the standard W7 ones.
As a test, I renamed the NVPACK and Nsight Tegra 1.1 folders to make sure the installer wasn’t having problems overwriting or deleting files, and re-ran (yet again) the installer. Same thing, no NVNDK. But I can manually run the r8d.exe in the Nsight Tegra 1.1 folder and self-extract it to C:\NVPACK\NVNDK.
I kept an eye on the installer and folders as it was running. There was no extra ndk installation action after the ndk extractor filled the C:\NVPACK\android-ndk-r8d folder. Perhaps you have a timing issue in your installer? If the android-ndk-r8d.exe file isn’t available by the time the installer gets to installing it (because of a busy system or background services), your installer may just bypass it. I did note that the environment variables on my main machine for the ndk were pointing to C:\NVPACK and not C:\NVPACK\NVNDK like on the vanilla test install machine, so the installer didn’t even get to that point in the script.
I am also getting a warning in the 4.7.2 compiler with my project that: “note: the mangling of ‘va_list’ has changed in GCC 4.4” in jni.h for a bunch of compiled files. This is extremely annoying and doesn’t happen with the 4.7 toolchain. For now, I’ve included “-Wno-psabi” in the compiler options, but obviously this isn’t the correct solution. Could you patch this in the next version of your software?