Tuesday, June 16, 2009 9:14 PMI am trying to build the WRK 1.2 according to the instructions in the document "Getting Started with WRK.doc" that is supplied with the distribution.
The document however assumes that the user have installed the WRK sources, tools and Debugging Tools using the "WRKInstall.bat" script. The problem is that this script is not included in the distribution?!
So I took one step ahead, assumed that the script will add the x86 tools directory (or the AMD) to the path environment variable. Then I changed directory into the "ntos" directory and entered "nmake x86=" at the command line. But the build failed and a message box titled "cl.exe - Unable To Locate Component" popped up telling me that "This application has failed to start because MSVCR71.dll was not found. Re-installing the application may fix this problem".
I can find the missing dll within the tools directory though. I have no idea how to direct the application to that.
I hope somebody can help me solving this problem.
- Edited by Santosh Kumar Nair Friday, June 26, 2009 6:42 PM fixing thread title bug
Wednesday, June 17, 2009 7:08 PMFirst of all, what distribution did you use?
In any case, do the following:
1. Install WinDbg to some directory WinDbgDir;
2. Install Virtual PC to some directory VPCDir;
3. Xcopy /s WRK-v1.2 directory to some directory WRKDir;
4. In WRKDir create file WRKEnv.bat with the following contents:
IF DEFINED wrkarch goto finish
IF NOT [%1] EQU  SET wrkarch=%1
SET windbgargs=-k com:pipe,port=\\.\pipe\debug,resets=0,reconnect
@title WRK %wrkarch%
5. Open console window, switch to WRKDir and run "WRKEnv.bat" or "WRKEnv.bat x86" or "WRKEnv.bat amd64" (x86 is the default).
6. In the same window, switch to base\ntos\ directory and execute nmake x86= or nmake amd64=.
OPTIONAL BUT USEFUL:
7. In WRKDir create file Build.bat with the following contents:
call WRKEnv.bat %1
nmake -nologo %wrkarch%=
8. In WRKDir create file Clean.bat with the following contects:
call WRKEnv.bat %1
nmake %wrkarch%= clean
9. In WRKDir create file Rebuild.bat with the following comtents:
call clean.bat %1
call build.bat %1
10. In WRKDir create file WRKDebug.bat with the following contents:
call WRKEnv.bat %1
Now you can open console window, switch to WRKDir and run, say, "Build amd64" or "WRKDebug x86".
Please note that once you established the target architecture (x86 or and64) in a console window, you can't change it. To work with different target architecture, open another console window. The chosen target architecture is shown in the console window's title ("WRK x86" or "WRK amd64").
Wednesday, June 17, 2009 9:24 PMI don't understand what do you mean by which distribution I am using. What I know is the version of the WRK I am trying to build. The code came in a zip file, and the only piece of information about building the system refers to a non-existing sort of installation script.
I did the basic steps you described (1-7), and I am still getting the same message box titled "cl.exe - Unable to Locate Component" telling that "This application has failed to start because MSVCR71.dll was not found. Re-installing the application may fix this problem". The problem still persists.
Tuesday, June 23, 2009 10:51 PM
Tuesday, June 23, 2009 11:40 PMBoth of them are there. But for some reason the build process cannot access them and keep giving me the message I posted previously.
Wednesday, June 24, 2009 9:02 PMLet me understand the situation. Please confirm that
1) directory WRKDir\tools\x86\ contains the following files: c1.dll, c1p.dll, c2.dll, cl.exe, cvtres.exe, lib.exe, link.exe, mc.exe, ml.exe, msobj71.dll, mspdb70.dll, mspdb71.dll, msvcp71.dll, msvcr70.dll, msvcr71.dll, nmake.exe, rc.exe, rcdll.dll;
2) path begins with "WRKDir\tools\x86;"
3) you run "nmake x86=" from directory WRKDir\base\ntos\
4) you still get "Unable to Locate Component" error.
Please note that in the above WRKDir means the directory you've copied WRK to, for example, C:\WRK-v1.2
Wednesday, June 24, 2009 9:16 PMFollowing up,
I was mistaken to think that msvcr71.dll was in my tools directory. Having lots of files that have similar names confused me.
I guess the case is closed. But I still would suggest the documentation be updated so that it would not refer to a non-existing script "WRKInstall.bat".
Thanks a lot!