Non-default paths and instructions....

by Michael S. Kaplan, published on 2006/03/26 03:00 -05:00, original URI: http://blogs.msdn.com/b/michkap/archive/2006/03/26/561016.aspx


Leandro Becker wrote to me via the contact link:

Hi

When building the CRT 7.1 following your blog instructions, after some minutes compiling I´ve got the following error:

# *** These are the compiler switches for the XDLL model (MSVCPRTD.LIB):
#
# CL = -c -nologo -Zelp8 -W3 -WX -GFy -DWIN32 -GB -Gi- -GS -Zc:wchar_t -Zc:forScope \
# -DWIN32_LEAN_AND_MEAN -DNOSERVICE -Fdbuild\intel\MSLUP71D.pdb \
# -D_MBCS -D_MB_MAP_DIRECT -D_CRTBLD -DWINHEAP -D_RTC -D_MT -D_DLL -DCRTDLL2
#
# ML = -c -nologo -coff -Cx -Zm -DQUIET -D?QUIET -Di386 -D_WIN32 -DWIN32 \
# -D_MBCS -D_MB_MAP_DIRECT -D_CRTBLD -DWINHEAP -D_RTC -D_MT -D_DLL -DCRTDLL2

=-=-=-=-= Doing CRTL Source build (Libraries) =-=-=-=-=
NMAKE : warning U4004: too many rules for target 'build\intel'
NMAKE : fatal error U1073: don't know how to make '"C:\Program Files\Microsoft Visual Studio .NET 2003\VC7\PlatformSDK\include\winver.h"'
Stop.

***
*** BUILD ABORTED -- ErrorLevel is non-zero!
***

C:\Arquivos de programas\Microsoft Visual Studio .NET 2003\Vc7\crt\src>

Do you know some issue like this ?

As soon as I saw the email I knew what the problem was (you might see the problem as well!).

And within five minutes of the first mail I got a second one from Leandro, who also saw what the problem was:

Sorry, I thing I´ve found the problem. I´ve copied the VCTOOLS from your post that is C:\Program Files path in the error, but my Windows is PT-BR, so the correct folder is C:\Arquivos de Programas.

Sorry :-(

No need to be sorry, Leandro!

What I had been working on (and would have even finished before that second mail if Leandro had been neither as smart or as quick!) was a small paragraph that I added to the 6.0, 7.0, 7.1, and 8.0 versions of the instructions (with the red emphasis included in each!):

In all instructions below, the assumption is a default install path and an en-US copy of Windows; if either is not the case, make sure you replace paths such as C:\Program Files\Microsoft Visual Studio 2003 with the appropriate install location.

Because this problem can occur any time there is a change due to:

I had initially started changing all paths in the instruction for the first item, when I realized the second and third items made it more important to just let the person who knows where everything is installed make the changes here, as needed.

Thanks for the heads-up, Leandro!


# Björn on 26 Mar 2006 7:23 AM:

I havn't looked at the instructions but why not use the VSINSTALLDIR/VCINSTALLDIR environment variables instead of the hardcoded path?

# Serge Wautier on 26 Mar 2006 8:22 AM:

There is some irony in the fact that a procedure eventually aimed at allowing better world-readiness requires patching culture-dependent hard coded information ;-)

# Ted on 26 Mar 2006 9:16 AM:

Yes, however, you could argue that carefully reading step 2 would kinda give it away as to what the path in step 4 should be set to. :)

# Michael S. Kaplan on 26 Mar 2006 8:43 PM:

No doubt, Ted. But additional clues never hurt....

Björn -- Good point, I have never really used the environment variables myself, but are they updated to handle all of these cases automatically?

# Björn on 27 Mar 2006 8:43 PM:

Yup, they are set during setup to the right locations.

go to newer or older post, or back to index or month or day