Hi Zebulon303
About one year ago there was a thread talking about this argument that is very complicated.
Personally I'm using WinCVS and Visual Sudio 6.0 on windows XP pro.
The dsw file in the CVS tree was not updated from a long time so compiling from Visual Studio gives endless errors.
Instead Chris uses the mak file that are up to date.
So I was compiling a working copy of the source code using the two pre defined makerelease.bat and makedebug.bat.
But you need some libraries for the linking that are necessary for the image management and that are not included in CVS tree and that you can find in the
index of celetia files. The file is named Celestia-Winlibs.zip. Then you have to place those file (h, lib and dll in the correct folders).
But this is not all.
You will need the LUA.lib that is missing in the Celestia-Winlibs.zip.
Actually I was not able to find these file so since April I was not able to compile in this way.
Actually I have modified and updated the dsw project files manually browsing the mak file so I'am able to compile and run a Celestia version without LUA support.
But is not the end. The really interesting way to use Visual Studio to play with Celestia code is to run the debug version of the program in the interactive debugging mode. So you are able to follow the code execution and understand deeply how the code operates. I've worked a lot to be able to configure the environment
but my knowledge of visual studio is limited and I get a lot of compiling warnings.
I'm not satisfied about my work so I don't want to share it.
Should be much more better if after the next Celestia Official Release (Hopefully 1.3.1 won't be so far) the developement team updates all the file necessary to compile with Visual Studio.
Bye - Paolo