Celestia 1.3.1 is available

[Guest]

I have the same problem. I'll try to check CVS, but just to let you know.

For all of you which are here, merry xmas from Holland as well

Though it seems that the source tarball is hosed:

Code: Select all

gmake[5]: *** No rule to make target `eclipsefinderdlg.cpp', needed by `eclipsefinderdlg.o'.  Stop.


Looks like some cpp code files didn't make it in src/celestia/kde. I can ofcourse copy them from 1.3.0... Or i should check CVS

[Christophe]

You can get another tarball here. It's the one I used to build the Mandrake RPM, so I know it is complete.

You can also get a daily snapshot here. In addition to 1.3.1 it includes an updated handbook (1.3.1 vs 1.3.0) and a new location page in the configuration dialog.

[David]

Chris,

It seems, there are two versions of 1.3.1

One posted in forum with 11799 Kb

http://prdownloads.sourceforge.net/cele ... -1.3.1.exe

Another posted in Homepage with 11853 Kb

http://prdownloads.sourceforge.net/cele ... .3.1-1.exe

Can I suppose that version in Homepage is the last with some corrections?

Congratulations for the big work !
David

[Harry]

It seems, there are two versions of 1.3.1

The only difference is the inclusion of lua-sripting in 1.3.1-1

Harald

[alvarezp]

Thanks, I'll try that.

You can also get a daily snapshot here. In addition to 1.3.1 it includes an updated handbook (1.3.1 vs 1.3.0) and a new location page in the configuration dialog.

Just after I posted as Guest , I tried the celestia-cvs.tatest tarball, and couldn't find the file either.

[Kelledin]

You can get another tarball here. It's the one I used to build the Mandrake RPM, so I know it is complete.

Confirmed. Cristophe's alternative tarball has the file; the "official" release tarball does not. FYI, a lot of other cpp files are missing from the same directory in the official tarball (but not Cristophe's). I just copied the files from Christophe's tarball to the "official" release tree, and it all seems to work well on my EV56 (at least, as well as one might expect with a decrepit, partially supported Radeon 7500. ).

Clearly the official tarball slipped out with some brokenness. How feasible is it to package a new "official" tarball? Should the version number be updated for this or something?

[selden]

EV56??

You have it running on an Alpha?? o_O

[danielj]

What is a lua-scripting?

It seems, there are two versions of 1.3.1

The only difference is the inclusion of lua-sripting in 1.3.1-1

Harald

[Harry]

What is a lua-scripting?

Celestia now supports a second scripting language, Lua. While normal scripts (with suffix .cel) can only execute a fixed list of commands, Lua (suffix .celx) is a complete programming language with variables, loops and if-then-else.

You can get some example-scripts on my webpage:
http://www.h-schmidt.net/celestia/

I am still waiting for some feedback, so I don't know if the scripts are working correctly on other systems, if you try them, please tell me how about any problems.

If it doesn't work:
- On windows you need celestia 1.3.1-1, celestia 1.3.1 won't work. If you already have 1.3.1, you can download the zipped .exe on my site - this is the only file that has changed.
- If scripts don't start when double-clicked or loaded directly from a webpage, try using File->Open in celestia instead.

Harald

[Kelledin]

EV56??

You have it running on an Alpha?? o_O

Yup, I am the proud owner of an old half-gutted rust-bucket of an Aspen Systems Durango II (PC164LX+600MHz EV56). It's no speed demon by today's standards tho.

I guess it's kind of a pleasant surprise that celestia is Alpha-ready, eh? And you discovered that right at the beginning of the year when the Alpha platform gets put to sleep.

[cycojesus]

You can get another tarball here. It's the one I used to build the Mandrake RPM, so I know it is complete.

You can also get a daily snapshot here. In addition to 1.3.1 it includes an updated handbook (1.3.1 vs 1.3.0) and a new location page in the configuration dialog.

I can't download >11MB tarballs everyday (56k...) so could anyone make a patch ?
This would be a great idea for releases too...

[Tech Sgt. Chen]

Well,
Here I am a day late and a Dollar short again. I had been trying to download the new version of celestia, but to no avail.
There seems to be a link or server malfunction with the address:
http://prdownloads.sourceforge.net/cele ... .3.1-1.exe

I was however, successful in my New Celestia download at the address:
http://www.celestiaproject.net/celestia/files/ ... .3.1-1.exe

My website is finally back on-line including my Celestia pages. It can be seen here: http://chthonia.net

HAPPY NEW YEAR to all of you and Thanks to Chris and everyone else involved with the newest Celestia release!

[cycojesus]

The CVS snapshot of yesterday is broken too...

[Christophe]

The CVS snapshot of yesterday is broken too... :evil:

What's wrong with it?

[Guest]

The CVS snapshot of yesterday is broken too...

What's wrong with it?

missing all the .cpp in src/celestia/kde
can't compile...

[Anomyous]

You can get another tarball here. It's the one I used to build the Mandrake RPM, so I know it is complete.

You can also get a daily snapshot here. In addition to 1.3.1 it includes an updated handbook (1.3.1 vs 1.3.0) and a new location page in the configuration dialog.

I noticed, all tarballs on the sourceforge servers are incomplete.
Maybe someone with access to sf.net should correct that.

[Christophe]

You can get another tarball here. It's the one I used to build the Mandrake RPM, so I know it is complete.

You can also get a daily snapshot here. In addition to 1.3.1 it includes an updated handbook (1.3.1 vs 1.3.0) and a new location page in the configuration dialog.

I noticed, all tarballs on the sourceforge servers are incomplete.
Maybe someone with access to sf.net should correct that.

Yes there is a problem with the tarball I host on my site. If configure is not run with --with-kde, the cpp files in the kde directory are not included, and I don't have KDE installed on my server.

So either the build process can be fixed to include all files whatever the configure options, or I'll have to install KDE on the server. For now, the safer way is to use CVS directly.