Celestia Forums

Trying to compile celestia for some time now and get the following error
fatal error C1083: Cannot open source file: '.\octree.cpp': No such file or directory

Searched and found some octree.cpp on the internet but it gives a tons of errors that would take very long to solve.

Where can I find octree.cpp that is able to compile with celestia WITHOUT additional errors !
Could someone who has compiled celestia 1.5Prex succesfully please post a link to a working octree.cpp for celestia.

with kind regards

Double posts about the same issue

http://www.celestiaproject.net/forum/viewtopic.php?t=11190

are never a good idea. Also if you want any help you ALWAYS need to quote:

your OS,
your compiler, version etc.
where you got the sources from
where you got the project files or the makefiles from

We all read out the code directly from CVS. I compile Celestia under various OS's including Windows (VS++ .Net 2003) almost daily. I don't experience the slightest problems both for Windows and Linux.

Under Windows, your error may be e.g. provoked if you forget to make octree.cpp known to your compiler...This then would be unrelated to the actual readability of that file.

Bye Fridger

I have found an octree.cpp and have then made octree.cpp known to my compiler by adding it as a existing item in Visual C++.

But that generated tons of errors AFTER adding it in Visual C++.
Found the octree.cpp here:
http://celestia.teyssier.org/source-doc ... ource.html



Here are the stuff I'm working with:

Microsoft Windows Vista
Visual C++ 2005 Express edition with 2003 R2 SDK linked together
source files from CVS
and extra librairies from the "Free Windows-based compiling of Celestia" topic.

I can't use visual C++ 2003 because it isn't compatible with Windows Vista.

duds26 wrote:I have found an octree.cpp and have then made octree.cpp known to my compiler by adding it as a new item in Visual C++.

But that generated tons of errors AFTER adding it in Visual C++.
Found the octree.cpp here:
http://celestia.teyssier.org/source-doc ... ource.html



Here are the stuff I'm working with:

Microsoft Windows Vista
Visual C++ 2005 Express edition with SDK linked together
source files from CVS
and extra librairies from the "Free Windows-based compiling of Celestia" topic.

I can't use visual C++ 2003 because it isn't compatible with Windows Vista.

You should read the FULL Celestia code out from CVS!

It's so easy, why do you do such error prone manipulations???

What a strange method to copy individual source files from different websites! If you continue doing this you are definitely on your own This octree.cpp file on Christophe's site is for documentation only with line numbers and all that! It's not for compiling.

Is this the first complex program you are compiling?

You should add octree.cpp as an EXISTING item to the compiler.

Also you MUST use Chris NEW set of libs that he published some time ago. Watch the directory structure!

How about Lua-5.1, SPICE and gettext (internationalization)??

Bye Fridger

This is the first complex program that I'm compiling and I'm completely new to this!

I have with Tortoise CVS checked out the full code from CVS ->122MB
I have added octree.cpp as an existing item, MY fault, sorry

The only thing why I copyd individual source files from different websites is that it isn't in the Celestia code

What's about how about Lua-5.1, SPICE and gettext? (<- I'm not asking this question to do funny or annoying)

duds26 wrote:This is the first complex program that I'm compiling and I'm completely new to this!

I have with Tortoise CVS checked out the full code from CVS ->122MB
I have added octree.cpp as an EXISTING item.

The only thing why I copyd individual source files from different websites is that it isn't in the Celestia code

What's about how about Lua-5.1, SPICE and gettext? (<- I'm not asking this question to do funny or annoying)

Oh I forgot: you ONLY need octree.h for compiling but NOT octree.cpp. It is superfluous, meanwhile. Take it out again. That's also why it is NOT in the CVS code (anymore).

But you may have to add other existing files to the compiler if you keep getting errors. I don't know from when is your project file or your .mak Makefile! A number of new files have been introduced recently.

Well if you want to compile Celestia with Lua-5.1 support or with SPICE or with internationalization, you got to add the respective libs and headers, as well as activate the respective macros -D.... Probably it's best if you do a minimum compilation first (without these). If this works you may contemplate how to expand. You may read off the required command line arguments in the attached *.mak files. They are also up-to-date as to the required files. Just inspect them (e.g. engine.mak in src/celengine) with an editor.

Bye Fridger

All the files are the newest (just updated before making this post)
And I'm trying to do the minimal compilation.


This is the output from build in Visual C++ 2005 Express Edition:
2>------ Build started: Project: Celestia, Configuration: Debug Win32 ------
1>Compiling...
1>octree.cpp
1>c1xx : fatal error C1083: Cannot open source file: '.\octree.cpp': No such file or directory
1>Build log was saved at "file://c:\Users\****\CVS&SVN\CVS repositories\celestia\src\celengine\Debug\BuildLog.htm"
1>celengine - 1 error(s), 0 warning(s)
2>Linking...
2>LINK : fatal error LNK1104: cannot open file 'cel_engine.lib'
2>Build log was saved at "file://c:\Users\****\CVS&SVN\CVS repositories\celestia\src\celestia\Debug\BuildLog.htm"
2>Celestia - 1 error(s), 0 warning(s)
========== Build: 0 succeeded, 2 failed, 4 up-to-date, 0 skipped ==========

(I know from another post that the second error is caused by the first one so it's basically one error)

So it's safe to delete the include <octree.cpp> in the files but I don't know where it is located or is this thing just a matter of development process and will be solved by the devs in a couple of days?

anyway, thanks for helping me t00fri
And I'm also trying to learn C++ so this is working on two ends of the developing spectrum: looking into very complicated code and starting to build simple applications.

When I try to make a new project in Visual C++ 2005 Ex...Ed... It says project creation failed every time and that's because I'm not registerd, will do that another day.

duds26 wrote:All the files are the newest (just updated before making this post)


This is the output from build in Visual C++ 2005 Express Edition:
2>------ Build started: Project: Celestia, Configuration: Debug Win32 ------
1>Compiling...
1>octree.cpp
1>c1xx : fatal error C1083: Cannot open source file: '.\octree.cpp': No such file or directory
1>Build log was saved at "file://c:\Users\****\CVS&SVN\CVS repositories\celestia\src\celengine\Debug\BuildLog.htm"
1>celengine - 1 error(s), 0 warning(s)
2>Linking...
2>LINK : fatal error LNK1104: cannot open file 'cel_engine.lib'
2>Build log was saved at "file://c:\Users\****\CVS&SVN\CVS repositories\celestia\src\celestia\Debug\BuildLog.htm"
2>Celestia - 1 error(s), 0 warning(s)
========== Build: 0 succeeded, 2 failed, 4 up-to-date, 0 skipped ==========

(I know from another post that the second error is caused by the first one so it's basically one error)

So it's safe to delete the include <octree.cpp> in the files but I don't know where it is located or is this thing just a matter of development process and will be solved by the devs in a couple of days?

Then you did not REMOVE it from the compiler. I don't know precisely the GUI of your VS++ 2005 express. I guess you right-click on the file octree.cpp in the solution/project listing and then hit remove.

Note: removing/deleting a file from the harddisk is NOT the same as deleting it from the solution/project!!!
You got to delete it from the solution/project. Otherwise the project file wants to open octree.cpp and does NOT find it. ==> error

Sorry, but I don't have the time to get you step by step through the compilation. There are probably more problems showing up the farther you get

Good luck,
Bye Fridger

IT HAS WORKED
now only adding LIBC.lib and it will work don't worry I can do this by myself.



1>------ Build started: Project: celengine, Configuration: Debug Win32 ------
2>------ Build started: Project: Celestia, Configuration: Debug Win32 ------
1>Creating library...
1>Build log was saved at "file://c:\Users\Peter\CVS&SVN\CVS repositories\celestia\src\celengine\Debug\BuildLog.htm"
1>celengine - 0 error(s), 0 warning(s)
2>Linking...
2>LINK : fatal error LNK1104: cannot open file 'LIBC.lib'
2>Build log was saved at "file://c:\Users\Peter\CVS&SVN\CVS repositories\celestia\src\celestia\Debug\BuildLog.htm"
2>Celestia - 1 error(s), 0 warning(s)
========== Build: 1 succeeded, 1 failed, 4 up-to-date, 0 skipped ==========



(will post a picture of the Visual C++ 2005 Exp.. interface soon)

duds26 wrote:Never had octree.cpp on my hard disk in the first place, that is the problem actually
It seems to be that the code has changed but not yet stable so creating this error.

I mean removing the references to the octree.cpp file in the other project files: the header files, the source files... themselves
Talking about changing the source!!

(will post a picture of the Visual C++ 2005 Exp.. interface soon)

No you are making some kind of mistake. The code is perfectly stable. As I wrote earlier, I am compiling it practically daily since YEARS ! You probably used an OLD project file from somewhere, where octree.cpp was still registered. I cannot tell for sure, since I only have little information about what you ACTUALLY did (including the gory details! ).

You can make a cross-check by not compiling with the GUI but rather using batch compiling via 'nmake /f makerelease.bat'. But you should read the docs first, how to do this! You need to activate nmake. It's ALL described in the manual in detail. I never understand why people are not FIRST reading carefully in the compiler docs how to compile, instead of spending weeks of their time with trial and error

If you get an error (instead of a usage message) after typing on the CMD console in the Celestia directory 'nmake /?' then you are doing things wrongly...

The trick is that Chris ALWAYS uses batch compiling, hence the *.mak Makefiles in CVS are always up-to-date.

Bye Fridger

Removed the bugger and it worked!!!!!

now only add LIBC.lib, don't worry I can do that on my own.
(if it is in the extra libraries)

(I'm not very fast in language: understanding language, due to a mental disorder)

thanks for helping me t00tri, you don't know how happy I am!

duds26 wrote:Removed the bugger and it worked!!!!!

now only add LIBC.lib, don't worry I can do that on my own.
(if it is in the extra libraries)

(I'm not very fast in language: understanding language, due to a mental disorder)

thanks for helping me t00tri, you don't know how happy I am!

CONGRATULATIONS!!! It's always a good feeling if a long and tedious battle was won

Bye Fridger