Free Windows-based compiling for Celestia.

The place to discuss creating, porting and modifying Celestia's source code.
Apollonian
Posts: 52
Joined: 19.10.2004
With us: 14 years 9 months

Post #21by Apollonian » 02.07.2005, 16:19

Bah, I'm getting the same LNK2001 errors. Can anyone help?

<Warning: Amateur at work...>

The *.lib files seem to be binaries... (no help though)

Let me know if you can make any sense of this:

http://msdn.microsoft.com/library/defau ... nk2001.asp

- It seems to be creating the *.lib files just fine. So, I can't imagine that the compiler can't find them unless there is some misreference to the "release" subfolders...

Moving discussion to here:

http://www.celestiaproject.net/forum/viewtopic ... c&start=30

- The makefiles seem to be doing what they are supposed to, except that the linker is giving an error and it can't complete the exe...

faethon
Posts: 4
Joined: 26.12.2005
With us: 13 years 6 months

Post #22by faethon » 27.12.2005, 11:04

Apollonian wrote:Bah, I'm getting the same LNK2001 errors. Can anyone help?

<Warning: Amateur at work...>

The *.lib files seem to be binaries... (no help though)

Let me know if you can make any sense of this:

http://msdn.microsoft.com/library/defau ... nk2001.asp

- It seems to be creating the *.lib files just fine. So, I can't imagine that the compiler can't find them unless there is some misreference to the "release" subfolders...

Moving discussion to here:

http://www.celestiaproject.net/forum/viewtopic ... c&start=30

- The makefiles seem to be doing what they are supposed to, except that the linker is giving an error and it can't complete the exe...


I have exactly the same link problems when trying to build the executable. Has anyone been able to solve these issues?

Avatar
selden
Developer
Posts: 10053
Joined: 04.09.2002
With us: 16 years 10 months
Location: NY, USA

Post #23by selden » 27.12.2005, 12:55

I recompile Celestia frequently under Windows (using MS Visual Studio 2003 Academic) and haven't seen these errors. Have you read and followed the instructions in the stickies at the top of this (Development) forum?
Selden

GlobeMaker
Posts: 216
Joined: 30.10.2005
With us: 13 years 8 months

Post #24by GlobeMaker » 28.12.2005, 14:12

I have the same error messages as georgiuk and faethon on the console:

NMAKE : fatal error U1077: 'link.exe' : return code '0x460'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual C++ Toolkit 2003\
bin\nmake.exe"' : return code '0x2'
Stop.

The file compile.txt has many lines like this:
error LNK2019: unresolved external symbol "__int64 std::_Fpz" (?_Fpz@std@@3_JA) referenced in function "protected: virtual class std::fpos<int> __thiscall std::basic_streambuf<char,stru

I used the SDK and C++ 2003 as instructions say. I added many LIB
and INCLUDE lines to the environment.

Next step : add more LIB and INCLUDE lines to the environment after
I search directories for .h and .lib files . These environmental text lines can be edited to list as many directories as I care to type. Any conflicts with directories having duplicate files will be resolved in order of this list of directories to search. The celvars.bat file now looks like this :

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\Microsoft 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%


Set INCLUDE=C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\include;%INCLUDE%
Set INCLUDE=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\PlatformSDK\include;%INCLUDE%
Set INCLUDE=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\atlmfc\include;%INCLUDE%
Set INCLUDE=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include;%INCLUDE%
Set INCLUDE=c:\CVS2\celestia\inc;%INCLUDE%

Set PATH=C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE;%PATH%
Set PATH=C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\bin;%PATH%
Set PATH=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\PlatformSDK\bin;%PATH%
Set PATH=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\atlmfc\bin;%PATH%
Set PATH=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin;%PATH%


Set LIB=C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\lib;%LIB%
Set LIB=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\PlatformSDK\lib;%LIB%
Set LIB=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\atlmfc\lib;%LIB%
Set LIB=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib;%LIB%
Set LIB=C:\CVS2\celestia\lib;%LIB%

Also, the nmake.exe file was not where the instructions said,
"Move Nmake.exe, cvtres.exe, lib.exe from "Microsoft SDK\bin\Win64"
It was in Microsoft Platform SDK\bin

And should nmake.exe be copied or "moved"?
Your wish is my command line.

Avatar
selden
Developer
Posts: 10053
Joined: 04.09.2002
With us: 16 years 10 months
Location: NY, USA

Post #25by selden » 28.12.2005, 14:35

FWIW, using VS 2003, and the following search path command file, I have no need to move anything, other than copying Celestia's own directories of include files and libraries into the celestia directory.

Compilation procedure:

1. update from CVS
2. open Windows command window in Celestia directory.
3. use cxx-defs.bat to define path, include and library paths
4. use makerelease.bat to build Celestia

contents of cxx-defs.bat:

Code: Select all

Set INCLUDE=C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\include;%INCLUDE%
Set INCLUDE=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\PlatformSDK\include;%INCLUDE%
Set INCLUDE=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\atlmfc\include;%INCLUDE%
Set INCLUDE=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include;%INCLUDE%
Set INCLUDE=G:\Celestia\celestia\inc;%INCLUDE%

Set PATH=C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE;%PATH%
Set PATH=C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\bin;%PATH%
Set PATH=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\PlatformSDK\bin;%PATH%
Set PATH=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\atlmfc\bin;%PATH%
Set PATH=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin;%PATH%


Set LIB=C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\lib;%LIB%
Set LIB=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\PlatformSDK\lib;%LIB%
Set LIB=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\atlmfc\lib;%LIB%
Set LIB=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib;%LIB%
Set LIB=G:\Celestia\celestia\lib;%LIB%
Selden

Avatar
Adirondack M
Posts: 516
Joined: 01.03.2004
With us: 15 years 4 months

Post #26by Adirondack » 29.12.2005, 00:33

Hm,

I also got an error after compiling with makerelease:

Code: Select all

nmake /NOLOGO celestia.mak CFG=Release
link.exe @C:\[...TMP-PATH...]\Temp\nm5E.tmp
LINK : fatal error LNK1181: cannot open input file 'user32.lib'
NMAKE : fatal error U1077: '"[...PATH...]\...Toolkit 2003\bin\nmake.exe"
' : return code '0X2'
Stop.


I am using MS SDK and MS Visual C++ Toolkit 2003 on an XP machine.

My celvars looks like this (I did build a celestia.exe successfully
early in spring with this celvars):

Code: Select all

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

Set INCLUDE=D:\Microsoft SDK\include;%INCLUDE%
Set LIB=D:Microsoft SDK\Lib;%LIB%
Set INCLUDE=D:\Microsoft SDK\include\Win64\mfc;%INCLUDE%
Set LIB=D:\Microsoft SDK\Lib\IA64\mfc;%LIB%


But now there is this error "cannot open input file 'user32.lib'",
though the 'user32.lib' is in the LIBs-settings of celvars (SDK/Lib
and SDK/Lib/IA64).

I have no clue why it does not work anymore. :cry:
I never ever touched the celvars, SDK and Toolkit since the last successfully
compiling in spring 2005.


Adirondack
We all live under the same sky, but we do not have the same horizon. (K. Adenauer)
The horizon of some people is a circle with the radius zero - and they call it their point of view. (A. Einstein)

GlobeMaker
Posts: 216
Joined: 30.10.2005
With us: 13 years 8 months

Post #27by GlobeMaker » 29.12.2005, 01:06

Hello Adirondak,

There is a typographical error in celvars.bat

old
Set LIB=D:Microsoft SDK\Lib;%LIB%
new
Set LIB=D:\Microsoft SDK\Lib;%LIB%
Your wish is my command line.

Avatar
Adirondack M
Posts: 516
Joined: 01.03.2004
With us: 15 years 4 months

Post #28by Adirondack » 29.12.2005, 15:17

GlobeMaker,

you are absolutely right! That was the point!
But I swear, the celvars with this typo has worked a few months ago.
Therefore, I have not suspected the celvars.
Very strange. Though the lacking of the backslash is obviously a fatal
misspelling.

Thank you very, very much. :lol:

Adirondack
We all live under the same sky, but we do not have the same horizon. (K. Adenauer)

The horizon of some people is a circle with the radius zero - and they call it their point of view. (A. Einstein)

GlobeMaker
Posts: 216
Joined: 30.10.2005
With us: 13 years 8 months

Post #29by GlobeMaker » 30.12.2005, 16:47

Here are some notes on my first-time compilation of Celestia on Windows XP.

Note 1
Follow the forum instructions, including second level
improvements posted to the thread. Importantly, the
SDK has 13 big files (25 meg each) to download, and
two small ones. This link was the one that worked

http://www.microsoft.com/msdownload/pla ... k-full.htm

The old description of menus to get the SDK is wrong.
The old links lead me to mistakenly
download a smaller 2 meg "Platform SDK file". And that
blocked progress. That was deleted and the 13
files were loaded with names like PSDK-FULL.13.cab
When the instructions say to "move" files, copy the files.


Note 2
After all the SDK and C++ Toolkit 2003 were in place,
another stumbling block presented itself. Two missing files. They were
called MSVCR70.dll and MSVCR80.dll. I found that in the SDK and
copied it to C:\Program Files\Microsoft Visual C++ Toolkit 2003\bin

Note 3
The compiler failed two more times, calling for odbc32.lib and
odbccp32.lib . These did not exist on my computer. I loaded
an old compiler to get those files. The old compiler is called
Microsoft Visual C++ 6.0 Standard Edition from 1998.
When those files were copied into the
C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib
directory, the compilation succeeded.



Note 4
Here is the environmental file called celvars.bat :
@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 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%

Set INCLUDE=C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\include;%INCLUDE%
Set INCLUDE=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\PlatformSDK\include;%INCLUDE%
Set INCLUDE=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\atlmfc\include;%INCLUDE%
Set INCLUDE=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include;%INCLUDE%
Set INCLUDE=c:\CVS2\celestia\inc;%INCLUDE%

Set PATH=C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE;%PATH%
Set PATH=C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\bin;%PATH%
Set PATH=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\PlatformSDK\bin;%PATH%
Set PATH=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\atlmfc\bin;%PATH%
Set PATH=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin;%PATH%

Set LIB=C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\lib;%LIB%
Set LIB=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\PlatformSDK\lib;%LIB%
Set LIB=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\atlmfc\lib;%LIB%
Set LIB=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib;%LIB%
Set LIB=C:\CVS2\celestia\lib;%LIB%

It compiled Celestia 1.4.0 correctly.
I started the program and the Earth loomed large.
Acceleration was applied, and stars parted before me.
Thanks to Chris, Selden, the doctors, the masters,
the bachelors, the coeds, and the eds of the community!

__________________________________________________


From : faethon
Joined: 26 Dec 2005 Here is faethon's report on his first compilation.
Posts: 4
Posted: Fri Dec 30, 2005 8:23 am Post subject:
Globemaker,
I got it compiled and linked eventually with a fresh install of Visual Studio .NET 2003, which I have access to from work. It looks promising that you got it to work with the free tools available from MS. I guess I got stuck with the odbc libraries you manually copied over. Maybe your info should go into the sticky on building the free windows build environment. Good work!
____________________________________________________
Thank you, faethon. This documentation was brought to you by...
a Master of the Science of Electrical Engineering who is staying current.
Your wish is my command line.

neoniv
Posts: 7
Joined: 31.01.2006
With us: 13 years 5 months

Problems with "unresolved external symbols"??

Post #30by neoniv » 04.02.2006, 21:37

Hello everyone!

I am having the same problems as Koula a few posts back 8O

I am trying to get Celestia compiled on Windows XP Home and
I ran into the same errors with "unresolved external symbols".

ex. (there was many of them)

Code: Select all

cel_engine.lib(trajmanager.obj) : error LNK2001: unresolved external symbol "pub
lic: void __thiscall std::_String_base::_Xlen(void)const " (?_Xlen@_String_base@
std@@QBEXXZ)


I have followed the free MS Visual C++ instructions as carefully
as I could...seems I can get close to a full compile...not all the
way.

I have all the libs, .dll's, and environment set up proper (i believe)

...does anyone have an idea why the above error happens?

Thanks for any help...nice forum!

p.s. I have tried to compile the SourceForge source, pre-FT1.2 and
the CVS checkout version. MS C++ (command line) and DevC++
all get me slightly different errors and problems.

Will this work on XP Home? (just in case that matters)

respect,
neoniv.

GlobeMaker
Posts: 216
Joined: 30.10.2005
With us: 13 years 8 months

Post #31by GlobeMaker » 04.02.2006, 23:23

Hi neoniv, did you delete the object files yet?
Using XP home, in /src/ directory from command line
del *.obj /S
Compile again.
Your wish is my command line.

neoniv
Posts: 7
Joined: 31.01.2006
With us: 13 years 5 months

SUCCESS on XP HOME!! My SDK was not installed proper.

Post #32by neoniv » 10.02.2006, 23:43

Hey all...keep with it if you are still having problems.

IT IS POSSIBLE TO COMPILE with MS C++ 2003 and XP HOME!!

{much relief} :P

After one week of poking and proding I was not able to
compile celestia...I talked with GlobeMaker several times
through email and the phone (THANKS GLOBEMAKER!!)...

I was having issues with Windows Installer...so I reinstalled
my XP Home, followed the steps again, compiled and success.

...this time going through all the steps again I realized I
had not set up the SDK properly (i was not able to run
the setup wizard properly...it needs Internet Explorer to
run properly which was broke before reinstalling XP.)

NOTE: First time I ran setup.exe it opened in Opera NOT I.E.

To solve this you need to open the file:

C:/temp/default.htm (or where ever you unzipped the SDK to)

...in Internet Explorer. If you did not download the SDK-FULL files
then ignore that last comment...

Then follow the instructions for:

III. Installing Microsoft Platform SDK.
which is here:
Free Windows-based compiling for Celestia.

Good luck to others and THANKS to GlobeMaker and
the rest of the forum community...you guys rock!

peace,
neoniv.

georgiouk
Posts: 47
Joined: 02.05.2005
With us: 14 years 2 months
Location: Greece

Post #33by georgiouk » 13.02.2006, 14:20

Hi neoniv.
I have solved my problems with such a strange way that the ones that know
programming will say its wrong but it really works for me just fine!

Well to succesfully compile Celestia I use this path
(the content of celvars.bat):

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\Microsoft Platform SDK\Lib;%LIB%
Set INCLUDE=C:\Program Files\Microsoft Platform SDK\Include\mfc;%INCLUDE%
Set LIB=C:\Program Files\Microsoft Platform SDK\Lib\IA64\mfc;%LIB%

and then when I compile I get these mistakes:

.\Release\celestia.exe : fatal error LNK1120: 8 unresolved externals
NMAKE : fatal error U1077: 'link.exe' : return code '0x460'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual C++ Toolkit 2003\
bin\nmake.exe"' : return code '0x2'
Stop.


So I return to the celvars.bat and change the path into this:

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 INCLUDE=C:\Program Files\Microsoft Platform SDK\Include\mfc;%INCLUDE%
Set LIB=C:\Program Files\Microsoft Platform SDK\Lib\IA64\mfc;%LIB%

And the celestia compiles!

I dont know why but until now that I am trying to translate Celestia all the changes
I make appeared to celestia just fine.

...........................................
K.G.

Rassilon
Posts: 1887
Joined: 29.01.2002
With us: 17 years 5 months
Location: Altair

Post #34by Rassilon » 21.03.2006, 20:33

Has anyone been able to make debugging work using the Toolkit and the SDK?

What exe is used to debug? if its cl.exe I guess its broken in this version if not which one in the bin folder is used for debugging?

Otherwise knowing that chris uses the command line compiler....What in the world does he use for debugging purposes?
I'm trying to teach the cavemen how to play scrabble, its uphill work. The only word they know is Uhh and they dont know how to spell it!

Rassilon
Posts: 1887
Joined: 29.01.2002
With us: 17 years 5 months
Location: Altair

Post #35by Rassilon » 21.03.2006, 22:22

Well im not going to bother with using the m$ debugger anyways....I think Ill inherit a very anal logging system that will track even memory leaks....This would be a better process anyways...

Looking at the celestia code lead me to believe this is what chris uses anyways....
I'm trying to teach the cavemen how to play scrabble, its uphill work. The only word they know is Uhh and they dont know how to spell it!

Andy74 M
Posts: 113
Joined: 21.07.2004
Age: 45
With us: 14 years 11 months
Location: Regensburg, Germany

Post #36by Andy74 » 14.08.2006, 08:36

Hello,

I had downloaded and installed TortoiseCVS as described above.
Then I tried to checkout the Celestia code several times, what led always to the same failure: I couldn't get connected to the CVS-Server.
The error message read "connect to cvs.sourceforge.net:2401 failed: Der Host war bei einem Socketvorgang nicht erreichbar." (in German).
I would translate to English as follows: "connect to cvs.sourceforge.net:2401 failed: host could not be reached during a socket process."
I use WinXP Home, a Pentium D 3GHz CPU and 1 GByte RAM.
Internet access via 1000 kbit/s ADSL.

Has anybody got an idea about that problem?

Thanks

Andy

cartrite
Posts: 1778
Joined: 15.09.2005
With us: 13 years 10 months
Location: Pocono Mountains, Pennsylvania, USA

Post #37by cartrite » 14.08.2006, 09:30

You can take a look at this page.

http://sourceforge.net/cvs/?group_id=21302

or make sure that your cvs root is,

Code: Select all

 :pserver:anonymous@celestia.cvs.sourceforge.net:/cvsroot/celestia


My settings on the module tab in TortoiseCVS are

Code: Select all

CVSROOT :pserver:anonymous@celestia.cvs.sourceforge.net:/cvsroot/celestia
Protocol: Password server [:perver:]
Server: celestia.cvs.sourceforge.net
Repository Folder: /cvsroot/celestia
User name: anonymous
Module: celestia


I think the above settings are populated automaticlly if the CVSROOT is correct

The address changed from cvs.sourceforge.net to celestia.cvs.sourceforge.net

cartrite
Toshiba Satellite P875=S7200 laptop, Intel i5 processor 2.5 ghz 6 gb ram, Graphics Intel(R) HD Graphics 4000 openSUSE Leap42.3
and Tumbleweed

Vincent
Posts: 1356
Joined: 07.01.2005
With us: 14 years 6 months
Location: Nancy, France

Post #38by Vincent » 14.08.2006, 09:33

Andy,
Sourceforge has been updated, so you have to use the new adress :

> CVSROOT :
:pserver:anonymous@celestia.cvs.sourceforge.net:/cvsroot/celestia

> Server :
celestia.cvs.sourceforge.net

It should work now...

PS : It would be a good thing to update the original post with the new adress.
@+
Vincent

Celestia Qt4 SVN / Celestia 1.6.1 + Lua Edu Tools v1.2
GeForce 8600 GT 1024MB / AMD Athlon 64 Dual Core / 4Go DDR2 / XP SP3

Andy74 M
Posts: 113
Joined: 21.07.2004
Age: 45
With us: 14 years 11 months
Location: Regensburg, Germany

Post #39by Andy74 » 14.08.2006, 11:35

cartrite and Vincent,

it works now. Thank you very much for your help. :)

Bye
Andy

Andy74 M
Posts: 113
Joined: 21.07.2004
Age: 45
With us: 14 years 11 months
Location: Regensburg, Germany

Post #40by Andy74 » 20.08.2006, 11:59

Hi.

I tried to compile the recent Celestia CVS source code.
As MS Visual C++ Toolkit 2003 is no longer available for download but was replaced by Visual C++ 2005 Express Edition, I downloaded the latter and installed it.
I followed the instructions in this thread and encountered the following error message (running makerelease.bat):

Code: Select all

NMAKE: fatal error U1077: 'cl.exe' : return code '0x2'
Stop.
NMAKE : fatal error U1077: ' "D:\Microsoft Visual Studio 8\VC\bin\nmake.exe"' : return code '0x2'
Stop.


Maybe the settings in my celvars.bat are not complete, but I can't compare them with the given examples here, because Visual C++ Express Edition has a different folder structure. The content of my celvars.bat is:

Code: Select all

@SET VSINSTALLDIR=D:\Microsoft Visual Studio 8
@SET VCINSTALLDIR=D:\Microsoft Visual Studio 8\VC
@SET FrameworkDir=C:\WINDOWS\Microsoft.NET\Framework
@SET FrameworkVersion=v2.0.50727
@SET FrameworkSDKDir=D:\Microsoft Visual Studio 8\SDK\v2.0
@if "%VSINSTALLDIR%"=="" goto error_no_VSINSTALLDIR
@if "%VCINSTALLDIR%"=="" goto error_no_VCINSTALLDIR

@echo Setting environment for using Microsoft Visual Studio 2005 x86 tools.

@rem
@rem Root of Visual Studio IDE installed files.
@rem
@set DevEnvDir=D:\Microsoft Visual Studio 8\Common7\IDE

@set PATH=D:\Microsoft Visual Studio 8\Common7\IDE;D:\Microsoft Visual Studio 8\VC\BIN;%PATH%
@set PATH=D:\Microsoft Visual Studio 8\Common7\Tools;D:\Microsoft Visual Studio 8\SDK\v2.0\bin;%PATH%
@set PATH=C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;D:\Microsoft Visual Studio 8\VC\VCPackages;%PATH%
@set INCLUDE=D:\Microsoft Visual Studio 8\VC\INCLUDE;%INCLUDE%
@set LIB=D:\Microsoft Visual Studio 8\VC\LIB;D:\Microsoft Visual Studio 8\SDK\v2.0\lib;%LIB%
@set LIBPATH=C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727

@set INCLUDE=C:\Programme\Microsoft SDK\include;%INCLUDE%
@set LIB=C:\Programme\Microsoft SDK\Lib;%LIB%
@set INCLUDE=C:\Programme\Microsoft SDK\include\Win64\mfc;%INCLUDE%
@set INCLUDE=E:\MyCelestia\inc;%INCLUDE%
@set LIB=C:\Programme\Microsoft SDK\Lib\IA64\mfc;E:\MyCelestia\lib;%LIB%

@goto end

:error_no_VSINSTALLDIR
@echo ERROR: VSINSTALLDIR variable is not set.
@goto end

:error_no_VCINSTALLDIR
@echo ERROR: VCINSTALLDIR variable is not set.
@goto end

:end


Does anybody else use Visual C++ Express Edition to compile celestia?
Any help is much appreciated.
Thank you.

Bye
Andy


Return to “Development”

Who is online

Users browsing this forum: 4 guests