On Wed, 26 Sep 2001 15:36:25 ryan.braden@xxxxxxxxxxxxx wrote:
>
> Yes, I did just do a "path %PATH%...." command to find the nmake.exe
> directory. Is that not the correct way to do it? I did run the
> vcvars32.bat file before attempting the build. But as you mentioned I
> think there may be a problem with the way MSVC was installed. I am
> running
> it off my work computer and I'm not sure how it was installed. When I
> type
> 'cl' on the command line I get an error box saying that "The dynamic link
> library mspdb60.dll could not be found in the specified path......." and
> it
> lists my path.
>
Yes, your installation is fouled up. You should be able to run nmake
and cl after running vcvars32.bat. The error reported by cl is indicative
of the misconfigured environment variables.
Take a look at vcvars32.bat; you should be able to see what's happening,
i.e., follow the logic. It sets 3 variables at the top, VSCommonDir,
MSDevDir, and MSVCDir. These should reflect the path where you have
MSVC installed; if not, change them, start a new shell, run vcvars32.bat
again, and test.
You should not have to manually adjust your path from the command-line
in order to find nmake or cl. Let vcvars32.bat do it for you.
--gilbert
