Page 1 of 1

CVS compile fails for me since Oct 20

Posted: 04.11.2006, 11:47
by Andy74
Hi.

Since a couple of weeks I've been compiling Celestia for myself and I quite enjoy it - i think it's the real Celestia feeling, being up to date with the development!
According to wcomer's instructions in the respective sticky topic on top of this forum I'm using Tortoise CVS (without any problems), MS Visual C++ Toolkit 2003 and the Microsoft Platform SDK.
At October 20 (about two weeks ago) I successfully compiled the CVS Celestia version (with CVS updated before) for the last time.
Any further compile at later dates failed.
The output of makerelease follows:

Code: Select all

   cd celutil
   nmake /NOLOGO util.mak MFLAGS=-MD CFG=Release
'.\Release\cel_utils.lib' is up-to-date
   cd ..
   cd celmath
   nmake /NOLOGO math.mak MFLAGS=-MD CFG=Release
'.\Release\cel_math.lib' is up-to-date
   cd ..
   cd cel3ds
   nmake /NOLOGO 3ds.mak MFLAGS=-MD CFG=Release
'.\Release\cel_3ds.lib' is up-to-date
   cd ..
   cd celtxf
   nmake /NOLOGO txf.mak MFLAGS=-MD CFG=Release
'.\Release\cel_txf.lib' is up-to-date
   cd ..
   cd celengine
   nmake /NOLOGO engine.mak MFLAGS=-MD CFG=Release SPICE=
'.\Release\cel_engine.lib' is up-to-date
   cd ..
   cd celestia
   nmake /NOLOGO celestia.mak MFLAGS=-MD CFG=Release SPICE=
   link.exe @C:\DOKUME~1\Andreas\LOKALE~1\Temp\nmCE.tmp
cel_engine.lib(simulation.obj) : error LNK2019: unresolved external symbol "public: class Selection __thiscall Universe::find(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &,class Selection *,int,bool)" (?find@Universe@@QAE?AVSelection@@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAV2@H_N@Z) referenced in function "public: class Selection __thiscall Simulation::findObject(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >,bool)" (?findObject@Simulation@@QAE?AVSelection@@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@_N@Z)
cel_engine.lib(simulation.obj) : error LNK2019: unresolved external symbol "public: class Selection __thiscall Universe::findPath(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &,class Selection *,int,bool)" (?findPath@Universe@@QAE?AVSelection@@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAV2@H_N@Z) referenced in function "public: class Selection __thiscall Simulation::findObjectFromPath(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >,bool)" (?findObjectFromPath@Simulation@@QAE?AVSelection@@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@_N@Z)
.\Release\celestia.exe : fatal error LNK1120: 2 unresolved externals

My system configuration:
DualCore Intel Pentium D 830, 3033 MHz
Memory 1022 MB
nVIDIA GeForce 6700 XL, memory 128 MB, ForceWare 81.82, OpenGL 2.0.1
Windows XP Home
Celestia CVS (last update today (11/04/2006) about 11:15 AM GMT)

Any help is very much appreciated - I miss the REAL Celestia feeling (and the latest bug fixes).:wink:
Thank you!

Bye
Andy

Posted: 04.11.2006, 11:57
by Vincent
You might try to make a clean release :

Code: Select all

> makerelease clean
... and then :

Code: Select all

> makerelease

re

Posted: 04.11.2006, 22:50
by John Van Vliet
i have had a simalure prob but with gcc 4.1 and it involves lua ( ie. the current version) not being found but hay this is a cvs build after all

Posted: 05.11.2006, 09:49
by Andy74
Vincent wrote:You might try to make a clean release :

Code: Select all

> makerelease clean
... and then :

Code: Select all

> makerelease

Dear Vincent,

thank you very much for this suggestion. Now everything works fine for me again.:D
Is it generally recommended to run

Code: Select all

makerelease clean
before running

Code: Select all

makerelease
or does this depend on certain conditions?
Just curious ...

Thanks again
Andy

Posted: 05.11.2006, 10:56
by Vincent
Andy74 wrote:Dear Vincent,

thank you very much for this suggestion. Now everything works fine for me again. :D
You're welcome Andy.

Andy74 wrote:Is it generally recommended to run

Code: Select all

makerelease clean
before running

Code: Select all

makerelease
or does this depend on certain conditions?

Well, I personnally make a clean release after a major update, to delete the .obj files that were built during the previous compilation.
Or, at least, when I get the kind of error you have reported... :wink:

Posted: 06.11.2006, 11:14
by Andy74
Well, I personnally make a clean release after a major update, to delete the .obj files that were built during the previous compilation.
Or, at least, when I get the kind of error you have reported... :wink:

Thank you for another helpful answer, Vincent. :)
Cheers
Andy