Compiling Problem

NIGHTCAST2000 · Post #1by **NIGHTCAST2000** » 11.10.2006, 20:02

Hi to all,
I am a reletive newcommer to Celestia and I have downloaded the latest official version,and I do enjoy it very much.

I had a look at the forum and stumbled upon the development section,and I read wcomer's post on how to compile celestia on windows with great interest,and decided to compile the lastest version from CVS.

I had followed wcomer's instructions and I have the full version of Windows Platform SDK and have moved the various files to their locations
according to the instructions.

The problem I'm having is listed in the command output I've pasted here:

problMicrosoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\STEVEN WARD.MERNIVIA>cd\

C:\>cd Mycelestia

C:\MyCelestia>celvars
Setting environment for using Microsoft Visual C++ 2003 Toolkit.
(If you have another version of Visual Studio or Visual C++ installed and wish
to use its tools from the command line, run vcvars32.bat for that version.)

Thank you for choosing the Visual C++ Toolkit 2003! Get started quickly by
building the code samples included in the "Samples" directory. Each sample
includes a short whitepaper discussing the Visual C++ features, and a batch
file for building the code.

Type "cl /?" for brief documentation on compiler options.

Visit http://msdn.microsoft.com/visualc/using ... fault.aspx for
complete compiler documentation.

C:\MyCelestia>makerelease
'makerelease' is not recognized as an internal or external command,
operable program or batch file.

C:\MyCelestia>cd.

C:\MyCelestia>cd..

C:\>cd TortoiseCVS\celestia

C:\TortoiseCVS\celestia>makerelease

C:\TortoiseCVS\celestia>cd src

C:\TortoiseCVS\celestia\src>nmake /f winbuild.mak CFG=Release

Microsoft (R) Program Maintenance Utility Version 1.50
Copyright (c) Microsoft Corp 1988-94. All rights reserved.

cd celutil
nmake /NOLOGO util.mak MFLAGS=-MD CFG=Release
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
NMAKE : fatal error U1077: 'C:\WINDOWS\system32\cmd.exe' : return code '0x1'
Stop.

C:\TortoiseCVS\celestia\src>cd ..

C:\TortoiseCVS\celestia>copy src\celestia\Release\celestia.exe .
The system cannot find the path specified.
C:\TortoiseCVS\celestia>em

I have pasted my celvars here:

@echo off

Set PATH=C:\Program Files\Microsoft Visual C++ Toolkit 2003\bin;%PATH%
Set INCLUDE=C:\Program Files\Microsoft Visual C++ Toolkit 2003\include;%INCLUDE%
Set LIB=C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib;%LIB%

Set INCLUDE=C:\Program Files\Microsoft Platform SDK\include;%INCLUDE%
Set LIB=C:\Program Files\Microsotf Platform SDK\Lib;%LIB%
Set INCLUDE=C:\Program Files\Microsoft Platform SDK\include\Win64\mfc;%INCLUDE%
Set LIB=C:\Program Files\Microsoft Platform SDK\Lib\IA64\mfc;%LIB%

echo Setting environment for using Microsoft Visual C++ 2003 Toolkit.
echo (If you have another version of Visual Studio or Visual C++ installed and wish
echo to use its tools from the command line, run vcvars32.bat for that version.)
echo.
echo Thank you for choosing the Visual C++ Toolkit 2003! Get started quickly by
echo building the code samples included in the "Samples" directory. Each sample
echo includes a short whitepaper discussing the Visual C++ features, and a batch
echo file for building the code.
echo.
echo Type "cl /?" for brief documentation on compiler options.
echo.
echo Visit http://msdn.microsoft.com/visualc/using ... fault.aspx for
echo complete compiler documentation.

I hope the information I have provided will help solve my problem.

Regards,
nightcast2000[/quote][/code]

cartrite · Post #2by **cartrite** » 11.10.2006, 22:56

Set PATH=C:\Program Files\Microsoft Visual C++ Toolkit 2003\bin;%PATH%

I dont see a path to the SDK bin. That may be it. My folder names are different so only use this as a guide.

Code: Select all

Set PATH=H:\Microsoft Visual C++ Toolkit 2003\bin;H:\Microsoft-SDK\Bin\win64;%PATH%

Edit Also, Make sure you have Word Wrap off if your using Notepad to edit this. Having it on may cause problems.

cartrite · Post #3by **cartrite** » 11.10.2006, 23:22

It's been ages now that I set this up but I think I had problems with celvars having too many SET commands. So my working copy has only 3. Only use this as a guide. Some of my my folder names are probally different. Microsoft-SDK for example.

Code: Select all

@echo off 

Set PATH=H:\Microsoft Visual C++ Toolkit 2003\bin;H:\Microsoft-SDK\Bin\win64;%PATH% 
Set INCLUDE=H:\Microsoft Visual C++ Toolkit 2003\include;H:\Microsoft-SDK\Include;H:\Microsoft-SDK\Include\mfc;%INCLUDE% 
Set LIB=H:\Microsoft Visual C++ Toolkit 2003\lib;H:\Microsoft-SDK\Lib\IA64\mfc;H:\Microsoft-SDK\Lib\;%LIB%

Edit Also, Make sure you have Word Wrap off if your using Notepad to edit this. Having it on may cause problems.

cartrite

NIGHTCAST2000 · Post #4by **NIGHTCAST2000** » 12.10.2006, 10:49

Hi,
I have followed cartrite's instructions and have altered my celvars
accordingly.I ran command prompt again and I got this output:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\STEVEN WARD.MERNIVIA>cd\

C:\>cd MyCelestia

C:\MyCelestia>celvars
Setting environment for using Microsoft Visual C++ 2003 Toolkit.
(If you have another version of Visual Studio or Visual C++ installed and wish
to use its tools from the command line, run vcvars32.bat for that version.)

Thank you for choosing the Visual C++ Toolkit 2003! Get started quickly by
building the code samples included in the "Samples" directory. Each sample
includes a short whitepaper discussing the Visual C++ features, and a batch
file for building the code.

Type "cl /?" for brief documentation on compiler options.

Visit http://msdn.microsoft.com/visualc/using ... fault.aspx for
complete compiler documentation.

C:\MyCelestia>cd..

C:\>cd TortoiseCVS\celestia

C:\TortoiseCVS\celestia>makerelease

C:\TortoiseCVS\celestia>cd src

C:\TortoiseCVS\celestia\src>nmake /f winbuild.mak CFG=Release
'nmake' is not recognized as an internal or external command,
operable program or batch file.

C:\TortoiseCVS\celestia\src>cd ..

C:\TortoiseCVS\celestia>copy src\celestia\Release\celestia.exe .
The system cannot find the path specified.
C:\TortoiseCVS\celestia>

I have put my altered celvars here:

@echo off

Set PATH=C:\Microsoft Visual C++ Toolkit 2003\bin;C:\Microsoft SDK\Bin\win64;%PATH%
Set INCLUDE=C:\Microsoft Visual C++ Toolkiit 2003\include;C:\Microsoft SDK\Include;C:\Microsoft SDK\Include\mfc;%INCLUDE%
Set LIB=C:\Microsoft Visual C++ Toolkit 2003\lib;C:\Microsoft SDK\Lib\IA64\mfc;C:\Microsoft SDK\Lib\;%LIB%

echo Setting environment for using Microsoft Visual C++ 2003 Toolkit.
echo (If you have another version of Visual Studio or Visual C++ installed and wish
echo to use its tools from the command line, run vcvars32.bat for that version.)
echo.
echo Thank you for choosing the Visual C++ Toolkit 2003! Get started quickly by
echo building the code samples included in the "Samples" directory. Each sample
echo includes a short whitepaper discussing the Visual C++ features, and a batch
echo file for building the code.
echo.
echo Type "cl /?" for brief documentation on compiler options.
echo.
echo Visit http://msdn.microsoft.com/visualc/using ... fault.aspx for
echo complete compiler documentation.

So I don't know where I'm going wrong here,so I had better tell you where the main files are.

My makerelease file is in C:\TortoiseCVS\celestia,
My celvars file is in C:\MyCelestia,
Both of my Microsoft Visual C++ Toolkit 2003 and Microsoft SDK are in
C:\Program Files.

I'll also let you know that word-wrap in Notepad is definetly off.

Any help would be greatly apprieciated.

Regards,
nightcast2000

cartrite · Post #5by **cartrite** » 12.10.2006, 11:50

Got Me. Everything looks right. Could you paste your celvars inside the code buttons? That way I could copy it to a txt file and see if there are any typos.

Edit: Never mind. See below. There are missing "Program Files" in all your paths.

cartrite · Post #6by **cartrite** » 12.10.2006, 11:57

NIGHTCAST2000

I have put my altered celvars here:

@echo off

Set PATH=C:\Microsoft Visual C++ Toolkit 2003\bin;C:\Microsoft SDK\Bin\win64;%PATH%
Set INCLUDE=C:\Microsoft Visual C++ Toolkiit 2003\include;C:\Microsoft SDK\Include;C:\Microsoft SDK\Include\mfc;%INCLUDE%
Set LIB=C:\Microsoft Visual C++ Toolkit 2003\lib;C:\Microsoft SDK\Lib\IA64\mfc;C:\Microsoft SDK\Lib\;%LIB%

Missing Program Files.

Edit
Your original celvars looks like it doesn't have any problems. I tried to split up the set commands and celvars still works. I also took out the path to SDK's bin and that still worked. So it seems that those changes I suggested were not necessary. SORRY. I can't remember what I was doing wrong back when I set this up but I think I may have been ommitting the "%LIB%" "%INCLUDE%" at the end of the extra lines. You have them in your original.

The only other thing that I can think of is that there may be a Microsoft folder in Program Files that both the Microsoft Visual C++ Toolkit 2003 and Microsoft SDKare in. In that case the path may be

Code: Select all

C:\Program Files\Microsoft\Microsoft Visual C++ Toolkit 2003\bin

and

Code: Select all

C:\Program Files\Microsoft\Microsoft Visual C++ Toolkiit 2003\include

...........

I would open the folder Microsoft Visual C++ Toolkit 2003 and verify that it is where you think it is.
/Edit

Edit2
I was running the altered celvars on a celestia folder that I had just built so I didn't see the impact of removing the SDK bin or having extra Set commands would be. They were not needed to invoke nmake but were needed to build the program. The first error I got was a missing dll.
msvcr80.dll.
I can't remember if that came with the SDK or I put it there manually. All I know is that missing dll was in H:\Microsoft-SDK\Bin\win64 and was needed.
Anyhow, Don't discard that altered celvars. You may experience other problems after you get the build process started. Welcome to the insane world of building source code.

/Edit2

cartrite

cartrite · Post #7by **cartrite** » 13.10.2006, 04:08

Here are a couple other things you can try in case your still having problems. Make sure your logged in as administrator. I beleive that only administrator's can change system variables. To be sure that your variables are set correctly, after running celvars, type in "set" and hit enter. You should see a lot of output that will include your current paths for PATH, INCLUDE, LIB. You could also run the set command before you run celvars and see if celvars changed anything. If celvars is changing your variables, then you got a different problem.

NIGHTCAST2000 · Post #8by **NIGHTCAST2000** » 13.10.2006, 09:05

Hi Cartrite,
Thank you very much for the advice,I will try that one.I am running Windows XP Professional with SP2 with all the latest updates.
I do log into my own account to compile Celestia,but I'm sure I made sure that my own account has administrive priviges,so I thought that wouldn't matter too much.

I will give it a go anyway,

Regards,
nightcast2000

cartrite · Post #9by **cartrite** » 13.10.2006, 12:31

So I guess the missing "Program Files" didn't work?

I do log into my own account to compile Celestia,but I'm sure I made sure that my own account has administrive priviges,so I thought that wouldn't matter too much.

Yes your right. As long as your logged in with administrive priviges you should be alright. Try that stuff with the set command though, at least then you'll know where you stand..Mabey there was some other problem all along.
cartrite

cartrite · Post #10by **cartrite** » 13.10.2006, 13:02

About the SDK\Bin, I reread wcomer's instructions. there was this section

IV. Installing miscellaneous utilities.

1) Move Nmake.exe, cvtres.exe, lib.exe from "Microsoft SDK\bin\Win64\" to "Microsoft Visual C++ Toolkit 2003\bin\"
2) Move RC.exe, RcDll.Dll from "Microsoft SDK\bin\" to "Microsoft Visual C++ Toolkit 2003\bin\"
3) Download http://download.microsoft.com/download/ ... make15.exe (50 kB)
4) Unzip nmake15.exe
5) Put nmake.err in the folder "Microsoft Visual C++ Toolkit\bin".
6) Discard the rest of the nmake15.exe files.

I set this up long after that was written. There may be a couple extra files that are needed now. That's why you may need the SDK\Bin\win64 in your PATH. I know I do. But I may have missed one too.

Edit

NIGHTCAST2000 wrote:

'C:\Program' is not recognized as an internal or external command

Here it looks as if a space is being encountered and it's not seeing the whole folder name as a folder.

I'll also let you know that word-wrap in Notepad is definetly off

What encoding are you using when you save the file celvars.bat? Mine is set to ANSI.

/Edit

cartrite

NIGHTCAST2000 · Post #11by **NIGHTCAST2000** » 13.10.2006, 20:01

Hi cartrite,
I have read your recent posts have carried out the instructions
you have suggested,here is the output I got from command prompt.

Code: Select all

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\STEVEN WARD.MERNIVIA>cd\

C:\>cd MyCelestia

C:\MyCelestia>set
ALLUSERSPROFILE=C:\Documents and Settings\All Users.WINDOWS
APPDATA=C:\Documents and Settings\STEVEN WARD.MERNIVIA\Application Data
Basemake=C:\Program Files\Microsoft Platform SDK\Include\BKOffice.Mak
Bkoffice=C:\Program Files\Microsoft Platform SDK\.
CLIENTNAME=Console
CommonProgramFiles=C:\Program Files\Common Files
COMPUTERNAME=MERNIVIA
ComSpec=C:\WINDOWS\system32\cmd.exe
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
HOMEPATH=\Documents and Settings\STEVEN WARD.MERNIVIA
INCLUDE=C:\Program Files\Microsoft Platform SDK\Include\.
INETSDK=C:\Program Files\Microsoft Platform SDK\.
LIB=C:\Program Files\Microsoft Platform SDK\Lib\.
LOGONSERVER=\\MERNIVIA
MSSdk=C:\Program Files\Microsoft Platform SDK\.
Mstools=C:\Program Files\Microsoft Platform SDK\.
NUMBER_OF_PROCESSORS=1
OS=Windows_NT
Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Mi
crosoft Platform SDK\Bin\.;C:\Program Files\Microsoft Platform SDK\Bin\WinNT\.;C
:\Program Files\Microsoft Platform SDK\Bin\.;C:\Program Files\Microsoft Platform
 SDK\Bin\WinNT\.
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 6 Model 8 Stepping 1, AuthenticAMD
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=0801
ProgramFiles=C:\Program Files
PROMPT=$P$G
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:\WINDOWS
TEMP=C:\DOCUME~1\STEVEN~1.MER\LOCALS~1\Temp
TMP=C:\DOCUME~1\STEVEN~1.MER\LOCALS~1\Temp
USERDOMAIN=MERNIVIA
USERNAME=STEVEN WARD
USERPROFILE=C:\Documents and Settings\STEVEN WARD.MERNIVIA
VCToolkitInstallDir=C:\Program Files\Microsoft Visual C++ Toolkit 2003\
windir=C:\WINDOWS

C:\MyCelestia>celvars
Setting environment for using Microsoft Visual C++ 2003 Toolkit.
(If you have another version of Visual Studio or Visual C++ installed and wish
to use its tools from the command line, run vcvars32.bat for that version.)

Thank you for choosing the Visual C++ Toolkit 2003!  Get started quickly by
building the code samples included in the "Samples" directory.  Each sample
includes a short whitepaper discussing the Visual C++ features, and a batch
file for building the code.

Type "cl /?" for brief documentation on compiler options.

Visit http://msdn.microsoft.com/visualc/using/documentation/default.aspx for
complete compiler documentation.

C:\MyCelestia>set
ALLUSERSPROFILE=C:\Documents and Settings\All Users.WINDOWS
APPDATA=C:\Documents and Settings\STEVEN WARD.MERNIVIA\Application Data
Basemake=C:\Program Files\Microsoft Platform SDK\Include\BKOffice.Mak
Bkoffice=C:\Program Files\Microsoft Platform SDK\.
CLIENTNAME=Console
CommonProgramFiles=C:\Program Files\Common Files
COMPUTERNAME=MERNIVIA
ComSpec=C:\WINDOWS\system32\cmd.exe
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
HOMEPATH=\Documents and Settings\STEVEN WARD.MERNIVIA
INCLUDE=C:\Program Files\Microsoft SDK\include\Win64\mfc;C:\Program Files\Micros
oft SDK\include;C:\Microsoft Visual C++ Toolkit 2003\include;C:\Microsoft SDK\In
clude;\mfc;C:\Program Files\Microsoft Platform SDK\Include\.
INETSDK=C:\Program Files\Microsoft Platform SDK\.
LIB=C:\Program Files\Microsoft SDK\Lib\IA64\mfc;C:\Program Files\Microsoft SDK\L
ib;C:\Microsoft Visual C++ Toolkit 2003\lib;C:\Microsoft SDK\Lib\IA64\mfc;C:\Mic
rosoft SDK\Lib\;C:\Program Files\Microsoft Platform SDK\Lib\.
LOGONSERVER=\\MERNIVIA
MSSdk=C:\Program Files\Microsoft Platform SDK\.
Mstools=C:\Program Files\Microsoft Platform SDK\.
NUMBER_OF_PROCESSORS=1
OS=Windows_NT
Path=C:\Microsoft Visual C++ Toolkit 2003\bin;C:\Microsoft SDK\Bin\win64;C:\WIND
OWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft Plat
form SDK\Bin\.;C:\Program Files\Microsoft Platform SDK\Bin\WinNT\.;C:\Program Fi
les\Microsoft Platform SDK\Bin\.;C:\Program Files\Microsoft Platform SDK\Bin\Win
NT\.
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 6 Model 8 Stepping 1, AuthenticAMD
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=0801
ProgramFiles=C:\Program Files
PROMPT=$P$G
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:\WINDOWS
TEMP=C:\DOCUME~1\STEVEN~1.MER\LOCALS~1\Temp
TMP=C:\DOCUME~1\STEVEN~1.MER\LOCALS~1\Temp
USERDOMAIN=MERNIVIA
USERNAME=STEVEN WARD
USERPROFILE=C:\Documents and Settings\STEVEN WARD.MERNIVIA
VCToolkitInstallDir=C:\Program Files\Microsoft Visual C++ Toolkit 2003\
windir=C:\WINDOWS

C:\MyCelestia>cd..

C:\>cd TortoiseCVS\celestia

C:\TortoiseCVS\celestia>makerelease

C:\TortoiseCVS\celestia>cd src

C:\TortoiseCVS\celestia\src>nmake /f winbuild.mak CFG=Release
'nmake' is not recognized as an internal or external command,
operable program or batch file.

C:\TortoiseCVS\celestia\src>cd ..

C:\TortoiseCVS\celestia>copy src\celestia\Release\celestia.exe .
The system cannot find the path specified.
C:\TortoiseCVS\celestia>

My latest celvars is here.

[/code]@echo off

Set PATH=C:\Microsoft Visual C++ Toolkit 2003\bin;C:\Microsoft SDK\Bin\win64;%PATH%
Set INCLUDE=C:\Microsoft Visual C++ Toolkit 2003\include;C:\Microsoft SDK\Include;\mfc;%INCLUDE%
Set LIB=C:\Microsoft Visual C++ Toolkit 2003\lib;C:\Microsoft SDK\Lib\IA64\mfc;C:\Microsoft SDK\Lib\;%LIB%

Set INCLUDE=C:\Program Files\Microsoft SDK\include;%INCLUDE%
Set LIB=C:\Program Files\Microsoft SDK\Lib;%LIB%
Set INCLUDE=C:\Program Files\Microsoft SDK\include\Win64\mfc;%INCLUDE%
Set LIB=C:\Program Files\Microsoft SDK\Lib\IA64\mfc;%LIB%

echo Setting environment for using Microsoft Visual C++ 2003 Toolkit.
echo (If you have another version of Visual Studio or Visual C++ installed and wish
echo to use its tools from the command line, run vcvars32.bat for that version.)
echo.
echo Thank you for choosing the Visual C++ Toolkit 2003! Get started quickly by
echo building the code samples included in the "Samples" directory. Each sample
echo includes a short whitepaper discussing the Visual C++ features, and a batch
echo file for building the code.
echo.
echo Type "cl /?" for brief documentation on compiler options.
echo.
echo Visit http://msdn.microsoft.com/visualc/using ... fault.aspx for
echo complete compiler documentation.

I did a little experiment when I noticed the makerelease was complaning that it couldn't find nmake.exe and nmake.err.I cut&pasted both files into the C:\TortoiseCVS\celestia\src folder,here is the output I got.

Code: Select all
Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\STEVEN WARD.MERNIVIA>cd\ C:\>cd MyCelestia C:\MyCelestia>set ALLUSERSPROFILE=C:\Documents and Settings\All Users.WINDOWS APPDATA=C:\Documents and Settings\STEVEN WARD.MERNIVIA\Application Data Basemake=C:\Program Files\Microsoft Platform SDK\Include\BKOffice.Mak Bkoffice=C:\Program Files\Microsoft Platform SDK\. CLIENTNAME=Console CommonProgramFiles=C:\Program Files\Common Files COMPUTERNAME=MERNIVIA ComSpec=C:\WINDOWS\system32\cmd.exe FP_NO_HOST_CHECK=NO HOMEDRIVE=C: HOMEPATH=\Documents and Settings\STEVEN WARD.MERNIVIA INCLUDE=C:\Program Files\Microsoft Platform SDK\Include\. INETSDK=C:\Program Files\Microsoft Platform SDK\. LIB=C:\Program Files\Microsoft Platform SDK\Lib\. LOGONSERVER=\\MERNIVIA MSSdk=C:\Program Files\Microsoft Platform SDK\. Mstools=C:\Program Files\Microsoft Platform SDK\. NUMBER_OF_PROCESSORS=1 OS=Windows_NT Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Mi crosoft Platform SDK\Bin\.;C:\Program Files\Microsoft Platform SDK\Bin\WinNT\.;C :\Program Files\Microsoft Platform SDK\Bin\.;C:\Program Files\Microsoft Platform SDK\Bin\WinNT\. PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH PROCESSOR_ARCHITECTURE=x86 PROCESSOR_IDENTIFIER=x86 Family 6 Model 8 Stepping 1, AuthenticAMD PROCESSOR_LEVEL=6 PROCESSOR_REVISION=0801 ProgramFiles=C:\Program Files PROMPT=$P$G SESSIONNAME=Console SystemDrive=C: SystemRoot=C:\WINDOWS TEMP=C:\DOCUME~1\STEVEN~1.MER\LOCALS~1\Temp TMP=C:\DOCUME~1\STEVEN~1.MER\LOCALS~1\Temp USERDOMAIN=MERNIVIA USERNAME=STEVEN WARD USERPROFILE=C:\Documents and Settings\STEVEN WARD.MERNIVIA VCToolkitInstallDir=C:\Program Files\Microsoft Visual C++ Toolkit 2003\ windir=C:\WINDOWS C:\MyCelestia>celvars Setting environment for using Microsoft Visual C++ 2003 Toolkit. (If you have another version of Visual Studio or Visual C++ installed and wish to use its tools from the command line, run vcvars32.bat for that version.) Thank you for choosing the Visual C++ Toolkit 2003! Get started quickly by building the code samples included in the "Samples" directory. Each sample includes a short whitepaper discussing the Visual C++ features, and a batch file for building the code. Type "cl /?" for brief documentation on compiler options. Visit http://msdn.microsoft.com/visualc/using/documentation/default.aspx for complete compiler documentation. C:\MyCelestia>set ALLUSERSPROFILE=C:\Documents and Settings\All Users.WINDOWS APPDATA=C:\Documents and Settings\STEVEN WARD.MERNIVIA\Application Data Basemake=C:\Program Files\Microsoft Platform SDK\Include\BKOffice.Mak Bkoffice=C:\Program Files\Microsoft Platform SDK\. CLIENTNAME=Console CommonProgramFiles=C:\Program Files\Common Files COMPUTERNAME=MERNIVIA ComSpec=C:\WINDOWS\system32\cmd.exe FP_NO_HOST_CHECK=NO HOMEDRIVE=C: HOMEPATH=\Documents and Settings\STEVEN WARD.MERNIVIA INCLUDE=C:\Program Files\Microsoft SDK\include\Win64\mfc;C:\Program Files\Micros oft SDK\include;C:\Microsoft Visual C++ Toolkit 2003\include;C:\Microsoft SDK\In clude;\mfc;C:\Program Files\Microsoft Platform SDK\Include\. INETSDK=C:\Program Files\Microsoft Platform SDK\. LIB=C:\Program Files\Microsoft SDK\Lib\IA64\mfc;C:\Program Files\Microsoft SDK\L ib;C:\Microsoft Visual C++ Toolkit 2003\lib;C:\Microsoft SDK\Lib\IA64\mfc;C:\Mic rosoft SDK\Lib\;C:\Program Files\Microsoft Platform SDK\Lib\. LOGONSERVER=\\MERNIVIA MSSdk=C:\Program Files\Microsoft Platform SDK\. Mstools=C:\Program Files\Microsoft Platform SDK\. NUMBER_OF_PROCESSORS=1 OS=Windows_NT Path=C:\Microsoft Visual C++ Toolkit 2003\bin;C:\Microsoft SDK\Bin\win64;C:\WIND OWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft Plat form SDK\Bin\.;C:\Program Files\Microsoft Platform SDK\Bin\WinNT\.;C:\Program Fi les\Microsoft Platform SDK\Bin\.;C:\Program Files\Microsoft Platform SDK\Bin\Win NT\. PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH PROCESSOR_ARCHITECTURE=x86 PROCESSOR_IDENTIFIER=x86 Family 6 Model 8 Stepping 1, AuthenticAMD PROCESSOR_LEVEL=6 PROCESSOR_REVISION=0801 ProgramFiles=C:\Program Files PROMPT=$P$G SESSIONNAME=Console SystemDrive=C: SystemRoot=C:\WINDOWS TEMP=C:\DOCUME~1\STEVEN~1.MER\LOCALS~1\Temp TMP=C:\DOCUME~1\STEVEN~1.MER\LOCALS~1\Temp USERDOMAIN=MERNIVIA USERNAME=STEVEN WARD USERPROFILE=C:\Documents and Settings\STEVEN WARD.MERNIVIA VCToolkitInstallDir=C:\Program Files\Microsoft Visual C++ Toolkit 2003\ windir=C:\WINDOWS C:\MyCelestia>cd.. C:\>cd TortoiseCVS\celestia C:\TortoiseCVS\celestia>makerelease C:\TortoiseCVS\celestia>cd src C:\TortoiseCVS\celestia\src>nmake /f winbuild.mak CFG=Release Microsoft (R) Program Maintenance Utility Version 1.50 Copyright (c) Microsoft Corp 1988-94. All rights reserved. cd celutil nmake /NOLOGO util.mak MFLAGS=-MD CFG=Release util.mak(45) : fatal error U1088: invalid separator '::' on inference rule Stop. NMAKE : fatal error U1077: 'C:\WINDOWS\system32\cmd.exe' : return code '0x2' Stop. C:\TortoiseCVS\celestia\src>cd .. C:\TortoiseCVS\celestia>copy src\celestia\Release\celestia.exe . The system cannot find the path specified. C:\TortoiseCVS\celestia>

I like to thank you very much for helping me on this and I'll look forward to be hearing from you soon.
Regards,
nightcast2000

cartrite · Post #12by **cartrite** » 13.10.2006, 20:36

After a prolonged quick look, it seems that your environment variables are already set before you run celvars. That may be giving windows headaches. Try running makerelease without running celvars. I'll keep looking and mabey I'll see something else.

NIGHTCAST2000 · Post #13by **NIGHTCAST2000** » 13.10.2006, 21:12

Hi cartrite,
I carried out what you suggested and went straight to makerelease and got this output:

Code: Select all

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\STEVEN WARD.MERNIVIA>cd\

C:\>cd TortoiseCVS\celestia

C:\TortoiseCVS\celestia>makerelease

C:\TortoiseCVS\celestia>cd src

C:\TortoiseCVS\celestia\src>nmake /f winbuild.mak CFG=Release

Microsoft (R) Program Maintenance Utility   Version 1.50
Copyright (c) Microsoft Corp 1988-94. All rights reserved.

        cd celutil
        nmake /NOLOGO util.mak MFLAGS=-MD CFG=Release
util.mak(45) : fatal error U1088: invalid separator '::' on inference rule
Stop.
NMAKE : fatal error U1077: 'C:\WINDOWS\system32\cmd.exe' : return code '0x2'
Stop.

C:\TortoiseCVS\celestia\src>cd ..

C:\TortoiseCVS\celestia>copy src\celestia\Release\celestia.exe .
The system cannot find the path specified.
C:\TortoiseCVS\celestia>

I have kept the configuration as I have posted recently(i.e Nmake.exe and
nmake.err are still in the C:\TortoiseCVS\celestia\src)

I hope that helps,

Regards,
nightcast2000

cartrite · Post #14by **cartrite** » 13.10.2006, 21:22

Another thing I noticed is that your path seems to be out of order with respect to the order my working copy produces. If there are 2 different files in the search path with the same name, Windows will use the one it finds first. I think. If it does that it may use the wrong file.
Output from the set command before I run celvars.

Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\NV
IDIA Corporation\NVIDIA DDS Utilities;C:\Program Files\Common Files\GTK\2.0\bin;
C:\Program Files\GnuWin32\bin;;H:ProgramsHEG\HEG_Win\bin;H:\Programs\HEG\HEG_Win
\bin

After I run celvars

Path=H:\Microsoft Visual C++ Toolkit 2003\bin;H:\Microsoft-SDK\Bin\win64;C:\WIND
OWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\NVIDIA Corpora
tion\NVIDIA DDS Utilities;C:\Program Files\Common Files\GTK\2.0\bin;C:\Program F
iles\GnuWin32\bin;;H:ProgramsHEG\HEG_Win\bin;H:\Programs\HEG\HEG_Win\bin

INCLUDE=H:\Microsoft Visual C++ Toolkit 2003\include;H:\Microsoft-SDK\Include;H:
\Microsoft-SDK\Include\mfc;
LIB=H:\Microsoft Visual C++ Toolkit 2003\lib;H:\Microsoft-SDK\Lib\IA64\mfc;H:\Mi
crosoft-SDK\Lib\;

I don't even have a path for INCLUDE or LIB before I run celvars.

Try to copy and paste the following into a text file and save it as celvars.bat

Code: Select all

@echo off 

SORRY BOGUS CODE WAS PLACED HERE.

If that don't work, navigate to C:\Program Files\Microsoft Visual C++ Toolkit 2003\ and copy vcvars32.bat and paste it on your desktop. Right lick on it and chose edit. Erase everything you see. Position the cursor at the beginning of the file and paste the code above. Hit save not save as. Then right click and rename it to celvars.bat and try running that.

This should have been my first question. Are you using a 64 bit version of XP?

I just seen your post that you posted while I was writing this. . I would take them out.

EDIT
I'm sorry that code above is bogus. Try this.

Code: Select all

@echo off

Set PATH=C:\Program Files\Microsoft Visual C++ Toolkit 2003\bin;C:\Program Files\Microsoft SDK\Bin\win64;%PATH%
Set INCLUDE=C:\Program Files\Microsoft Visual C++ Toolkit 2003\include;C:\Program Files\Microsoft SDK\Include;C:\Program Files\Microsoft SDK\Include\mfc;%INCLUDE%
Set LIB=C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib;C:\Program Files\Microsoft SDK\Lib\IA64\mfc;C:\Program Files\Microsoft SDK\Lib\;%LIB%

Check for typos. I wrote that by hand to make it work for you and I'm a lousy typist.

/EDIT

cartrite

abramson · Post #15by **abramson** » 13.10.2006, 21:52

Hi, Nightcast. Not knowing much about this, but being able to succesfully compile using the free MS utilities, I want to contribute the following. This is the screen output in my system. Observe that the version of the MS Program Maintenance Utility is 7, much greater than the 1.5 in your system. Is it possible that this affects anything?

Code: Select all

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

c:\Program Files\Astro\celestia cvs\celestia>makerelease

c:\Program Files\Astro\celestia cvs\celestia>cd src

C:\Program Files\Astro\celestia cvs\celestia\src>nmake /f winbuild.mak CFG=Release

Microsoft (R) Program Maintenance Utility   Version 7.00.8882
Copyright (C) Microsoft Corp 1988-2000. All rights reserved.

        cd celutil
        nmake /NOLOGO util.mak MFLAGS=-MD CFG=Release
'.\Release\cel_utils.lib' is up-to-date

And these are my relevant environment variables:

Code: Select all

INCLUDE=C:\Program Files\Sci\Microsoft Visual C++ Toolkit 2003\include;c:\Program Files\Sci\Microsoft Platform SDK\Include\;c:\Program Files\Sci\Microsoft Platform SDK\Include\mfc\

LIB=C:\Program Files\Sci\Microsoft Visual C++ Toolkit 2003\lib;c:\Program Files\Sci\Microsoft Platform SDK\Lib\;c:\Program Files\Sci\Microsoft Platform SDK\Lib\IA64\mfc\

Path=C:\Program Files\Text\Miktex\miktex\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Sci\Microsoft Visual C++ Toolkit 2003\bin;c:\Program Files\Sci\Microsoft Platform SDK\Bin\win64\;C:\Program Files\Image\Nvidia DDs Utilities

Finally, I have discovered that I need to edit the file celestia cvs\celestia\src\celestia\res\celestia.rc, and add the command #include "commctrl.h" after the including of resource.h, to avoid having errors about undefined keywords (DTS_RIGHT_ALIGN and such).

Guillermo

Using:
Windows Server 2003 SP1 SDK
Visual C++ Toolkit 2003 version 1.01
XP Home SP2

NIGHTCAST2000 · Post #16by **NIGHTCAST2000** » 13.10.2006, 21:53

Hi carteite,
I've done what you asked and went to command prompt
and cd'ed to the desktop and ran the celvars.

The output was interesting,because when I ran it,the prompt cursor went back to Desktop.

By the way,I'm running Windows XP Professional 32-bit edition.

Regards,
nightcast2000

cartrite · Post #17by **cartrite** » 13.10.2006, 22:00

Look at that post agin. I've edited it. You know if you get tired of trying all this there is a setup that will install the cvs code for 10/04/2006 found here.
http://www.celestiaproject.net/forum/viewtopic ... 8798#78798
cartrite

cartrite · Post #18by **cartrite** » 13.10.2006, 22:11

abramson wrote

Observe that the version of the MS Program Maintenance Utility is 7, much greater than the 1.5 in your system. Is it possible that this affects anything?

Your very observant. I have version 7 too. That may be the problem.

cartrite · Post #19by **cartrite** » 13.10.2006, 22:20

NIGHTCAST2000 wrote:Hi carteite,
I've done what you asked and went to command prompt
and cd'ed to the desktop and ran the celvars.

The output was interesting,because when I ran it,the prompt cursor went back to Desktop.

By the way,I'm running Windows XP Professional 32-bit edition.

Regards,
nightcast2000

I run celvars from the copy of celestia I'm building. Same directory as makerelease.

Sometimes you have to type cd /d C:\Where ever you ant to go

cartrite

NIGHTCAST2000 · Post #20by **NIGHTCAST2000** » 13.10.2006, 22:27

Hi guys,
Where can I get Ms Program Maintenance Utiliy 7 from?
Is it from Microsoft SDK Sp1?

Regards,
nightcast2000