Celestia Forums

Trying to get Celestia up and running in a VC++ environment. I've loaded the project files successfully, but when I come to build it favorites.cpp spits out 158 linker warnings, and then finally dies with:

BSCMAKE: error BK1506 : cannot open file '.\Release\imagecapture.sbr': No such file or directory

Also, when clean building, it throws a load of errors along the lines of:

E:\Celestia\Celestia Source\celestia-1.2.4\src\celestia\winmain.cpp(0) : fatal error C1033: cannot open program database 'e:\celestia\celestia source\celestia-1.2.4\src\celestia\release\vc60.idb

Now at some point in the past this DID work, I'm sure. However the files it's looking for aren't in the release dir.

Anyone know what's going on? :O/

*bump*

Surely someone must have had this? I haven't changed any of the code, and whichever way I slice it it invariable runs into problem linking files which don't exist in the /release or /debug directory.

Hi i have a simmiler problem , So i am giving up for right now and concentrating on learning c++ better.

I believe it might be a short coming of the VC enviroment...I think chris writes his software entirely under linux though I may be wrong....Try a search on this site I think chris answered this somewhere before....

I sorted this a long while ago :O)

I converted my .dsw files from Linux line returns to Windows line returns, but somewhere in the process one of them corrupted, which threw my build process in the bin. I redid the conversion, and they work now.

I downloaded the source from: http://prdownloads.sourceforge.net/cele ... 2.4.tar.gz

and so now I have the source in d:\temp\celestia-1.2.4

I opened up d:\temp\celestia-1.2.4\src\Celestia.dsw in textpad and saved it with the PC line feeds instead of the UNIX ones.

Then I open up Visual C++ 6.0 Enterprise Edition and click File/Open Workspace and select d:\temp\celestia-1.2.4\src\Celestia.dsw

Then for each *.dsp file:

D:\temp\celestia-1.2.4\src\celestia\Celestia.dsp
D:\temp\celestia-1.2.4\src\cel3ds\cel3ds.dsp
D:\temp\celestia-1.2.4\src\celengine\celengine.dsp
D:\temp\celestia-1.2.4\src\celmath\celmath.dsp
D:\temp\celestia-1.2.4\src\celtxf\celtxf.dsp
D:\temp\celestia-1.2.4\src\celutil\celutil.dsp

I get the following message:

"This makefile was not generated by Developer Studio

Continuing will create a new Developer Studio project to wrap this makefile. You will be prompted to save after the new project has been created.

Do you wish to continue?"


Saying no doesn't seem to work. Saying yes asks me to save the *.dsp file as a different name( ie. celutil1.dsp). I do this for each file.

Now the correct workspace tree is along the left, but each project has a number 1 after it:

cel3ds1 files
celengine1 files
etc...


I made sure that under Tools/Options/Directories I have the libpng,libjpeg, and libz directories under both include paths and library paths

Now if I go up to the Build menu, it says: Build celestia1.exe.

If I select this I get the following error:

NMAKE : fatal error U1073: don't know how to make '..\celutil\Debug\cel_utils.lib'

Can anyone help me? Thanks.

The Visual Studio project file is often out of date, because I never use VS to build Celestia. Instead, I build from the command line. Just go to root Celestia directory and run either makerelease.bat or makedebug.bat and everything should just work. If you really want to use VS, there will be a bit of work involved getting Celestia to build--just save yourself the trouble, and use the command line.

--Chris

I tried to run makerelease.bat and I got the following error:

../../inc/libjpeg\jmorecfg.h(13) : fatal error C1083: Cannot open include file:
'apptypes.h': No such file or directory

I downloaded the libraries from the graphapp website. Is there a better place to get these libraries?

Also, since I have my source in d:\temp\celestia-1.2.4\src, I created a directory d:\temp\celestia-1.2.4\inc and put the liibraries in ther so I have \inc\libjpeg, inc\libpng and inc\libz. I hope that is correct.

Okay, I downloaded libpng, libjpeg, and libz from their respective websites and hopefully set them up correctly. Now when I try makedebug, I get a whole lot of these messages:

... identifier was truncated to '255' characters in the debug information

and I end up with:

vertexlist.cpp
vertexprog.cpp
vsop87.cpp
NMAKE : fatal error U1077: 'cl.exe' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"D:\Program Files\Microsoft Visual Studio\VC98\bin\N
MAKE.EXE"' : return code '0x2'
Stop.




If I try makerelease.bat, I get:

cd ..
cd celengine
nmake /NOLOGO engine.mak CFG=Release
cl.exe @C:\DOCUME~1\BLUEMO~1\LOCALS~1\Temp\nma00348.
texture.cpp
../../inc/libjpeg\jmorecfg.h(161) : error C2371: 'INT32' : redefinition; different basic types
D:\Program Files\Microsoft Visual Studio\VC98\include\basetsd.h(33) : see declaration of 'INT32'
../../inc/libjpeg\jmorecfg.h(215) : warning C4005: 'FAR' : macro redefinition
D:\Program Files\Microsoft Visual Studio\VC98\include\windef.h(135) : see previous definition of 'FAR'
NMAKE : fatal error U1077: 'cl.exe' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"D:\Program Files\Microsoft Visual Studio\VC98\bin\N
MAKE.EXE"' : return code '0x2'
Stop.

Not sure exactly what's wrong . . . perhaps you have the wrong versions of the libraries? Try these:

http://www.celestiaproject.net/celestia/files/winlibs-new.zip

This archive contains all the libraries necessary for building Celestia.

--Chris

If you are new to the command-line tools for Windows development, you might not know about setting up your environment variables.

In the Visual Studio directory tree somewhere, there is the VCVARS.BAT file. You need to run this to get the command-line tools to work correctly. Sorry I am not more specific; I'm not running Windows at the moment.

The .bat files in the celestia-1.2.4 release that I downloaded do not set this up for you (and I don't necessarily think that they should). You could add a line at the top of the .bat file that looks something like this:



Hope that this helps...

--watersb