Problem about compiling ...

[Fightspit]

I have a problem to compile the CVS and I find the cause which come from a file (ressource.h) where IDC_STATIC is not define.
More info here:
http://www.celestiaproject.net/forum/viewtopic ... c&start=57

[selden]

While some people like to try to use Visual Studio's IDE to build Celestia, that's not what Chris does. As a result, many of the files on SourceForge that would be used by the IDE are incomplete and do not work. Chris does not have the time to try to maintain them. (Personally I think it probably would be appropriate to delete them from SourceForge so people aren't mislead.)

If you want to produce the same version of Celestia that is included in its Windows distribution kit, you have to use the script makerelease.bat. That script does not use resource.h and does not need IDC_STATIC.

Sorry.

[Fightspit]

If you want to produce the same version of Celestia that is included in its Windows distribution kit, you have to use the script makerelease.bat. That script does not use resource.h and does not need IDC_STATIC.

Well, unfortunately, I used makerelease.bat to compile because I am under Windows XP (with the command prompt) and the problem that I described in the previous post, is not vanish ...

I can add the IDC_STATIC in the ressource.h but I want to know what it is the number I should add.

Code: Select all

//{{NO_DEPENDENCIES}}
// Microsoft Visual C++ generated include file.
// Used by celestia.rc
//
#define VERSION_STRING                  "1.5.0"
#define IDR_MENU1                       101
#define IDD_ABOUT                       102
#define IDC_STATIC                      ???  <- number ?
#define IDI_CELESTIA_ICON               103
#define IDD_FINDOBJECT                  104
...


[t00fri]

While some people like to try to use Visual Studio's IDE to build Celestia, that's not what Chris does. As a result, many of the files on SourceForge that would be used by the IDE are incomplete and do not work.

Correct, but after a quick look into the online help of the respective IDE's, it should be obvious how to complement what is missing!

The Visual Studio 6 workspace (*.dsw) and project (*.dsp) files in CVS are fine to serve as a basis, except they are not maintained to be complete as to newly added files. However, adding new ones to the building file pool is very straightforward...I never had the slightest problems, taking the old *.dsw, *.dsp files as a start. Also deleting superfluous files from the building file set is trivial within the IDE. Of course, in this case, they are not deleted from people's hard disks...

Chris does not have the time to try to maintain them.

Despite his announced full-time committment to Celestia?

(Personally I think it probably would be appropriate to delete them from SourceForge so people aren't mislead.)

Since Chris is apparently in the process of converting the Win32 building to the FREE Microsoft VS++ 2005 Express compiler, we should soon or later have an appropriate working set of respective makefiles in CVS.

Instead of those outdated *.dsw, *.dsp files, many of us (including myself, of course) could since long have supplied their perfectly updated & maintained VS7 project files, for example. Chris has never asked for them...so nothing happened. Similarly, the required 'winlibs' set by Chris included partly very old libraries. I understand that he has updated them just now, after my respective mail in the dev list. Unlike the 'winlibs' set, I am using my own, self-compiled and most recent libs since quite a while for Windows building.


Bye Fridger

[Fightspit]

Also, I use the command prompt not the default one (cmd.exe) but provide by VisualStudio as below:




This command prompt can set all the environnement for VisualStudio and I can use for compiling.