Celestia Forums

Hi everyone
I'm trying to install Celestia on my Linux machine. I'm running Kubuntu 17.10 and I have installed all of the dependencies listed in the readme (I've also tried building from source, but was unable to do so; however, let's get to that later, I want to try and get the package file working first).

So, I downloaded the Celestia 1.5.1 autopackage file and ran it. This was the output:


As promised, Celestia shows up in my application menu but when I try to run it, nothing happens. It clearly hasn't installed correctly, because it couldn't find certain dependencies. However, I have *already installed* all dependencies listed on Github. Is there something else I'm missing? I also tried installing libgtk-3-dev and libgnome-vfs2.0-cil-dev just in case that's what it wanted (I'm not even sure if those are the right packages) but to no avail.

I'd really appreciate any help with this! I'm happy to try building from source again if necessary, but will need help with that too.

Celestia is not in Ubuntu repos any more as it was removed from Debian.

To build from sources clone git repository https://github.com/CelestiaProject/Celestia and follow instructions in README file (duplicated below).

Currently only QT5 based backend is available. To build it you need QT5
developer libraries.

On Debian based systems the following packages should be installed:
* qtbase5-dev-tools
* qtbase5-dev
* libqt5opengl5-dev
* qtchooser
* libglu1-mesa-dev
* libpng-dev
* libjpeg-dev
* libtheora-dev
* Either one of liblua5.3-dev, liblua5.2-dev or liblua5.1-dev

Optional packages are libeigen3-dev and libglew-dev.

Then do the following actions in Celestia's source directory:
mkdir build && cd build
qmake -qt=5 PREFIX=/opt/celestia -o Makefile ../celestia.pro
make

You can speedup build passing option -jN to make where N is a number of
your CPU cores.

Thanks for your response.

I'm not sure what you mean about the Ubuntu repos - I was not trying to install Celestia via them! I just downloaded the autopackage file celestia-1.5.1.x86.package from the download page on the Celestia website: https://celestia.space/download.html
If this autopackage script has dependencies on packages that are no longer available in the Ubuntu repos, that should be documented so that Debian and Ubuntu users (which I imagine are the majority of Linux users) know they can't use it. But I thought the autopackage file was standalone.

Moving on to building from source -
I have already followed the steps above from the README, however there are no instructions on what to do AFTER building from source - how do I actually run the thing? I ask this because I was not able to find an executable file anywhere, which makes me think it didn't build properly.
Not sure if this means anything but if I run make a second time after having installed per the instructions above, I get this error:


I don't really know how this is working however as I'm not familiar with using make without following up with make install.

Hi dbaker,

Could you provide more lines of build failure?

Regarding autopackage - sownload page clearly states that you should have gtk2 installed.

After make the usual step is sudo make install. You binary will be istalled to /opt/celestia/bin/Celestia_QT

I installed gtk 2 using sudo apt install gtk2.0. Is that the correct package? Because the autopackage still fails. See my original post for the output when I run it.

After make the usual step is sudo make install

That's what I would have thought, but that instruction is not in the readme which made me think this was some special case where I shouldn't use it. I didn't want to try in case I messed something up! (It strikes me as strange to give step by step instructions on what dependencies to install, etc right up to the second last command to run, and leave out the actual installation step. If it's ok to do so, I might PR an update to the readme)

In any case, I just tried running sudo make install in the build directory and this was the output:



I've provided the entire output above, just in case, but I searched the output in a text editor and found one error, which I've pasted below:

make install so obvious for me

I've pushed an update, please do "git pull" and rebuild.

Thank you, got it working

glad to here you got it working

I was about to point you to my linux only fork

https://github.com/JohnVV/MyCelestiaBuild

qt5 and lua 5.1 build and supports SPICE

JohnVV, your fork is outdated, it does not provide any new feature. If you want to develop something new join the team.

It's been a while. Hi to all. Some may remember me, many others are new to me. Done some reading here. Mostly build issues with linux though.

I stumbled on this forum yesterday while I was looking for a reason why celestialmatters was down. A while back I tried building my old copies of celestia on my current linux systems and ran into too many issues. Anyhow I tried building the master found here and had problems with lua. It would build up to celx,cpp. Then I'd get errors with undefined symbols, using classes out of scope, etc. I got JohnVV's version to work this morning. Had 1 minor problem though. Building spiceorbit.cpp would fail until I copied the include files from cspice into the celephem folder.

I just got the master to build also but I had to edit celestia.pro to only use lua 5.1. I'm using openSUSE leap42.3 and tumbleweed. Still cant get any build on 42.3 but tumbleweed has both versions built. HOORA. Could not get a build with qt-creator yet though. I built both versions with a terminal running qmake-qt5, make manually. The gcc version reports to be gcc 8.2.1. I got many warnings on both versions. Mostly they had to do with Eigen.

Been doing some reading about porting apps to 64 bit. Correct me if I'm wrong but a 64 bit compiler does create 64 bit apps. But the main issues are arrays, pointer, and math done on them. So the compiler creates code that causes bugs or incorrect results in a 64 bit register. So that would seem to be a major undertaking correct.

Anyhow, have a good one

cartrite

Hi cartrite!

It would be nice if you provide failure logs as I don't use any Suse flavours neither Pirogronian does.

I just switched over to Leap42.3. This system has a few issues. For one it doesn't let me have 2 versions of lua dev files. I have lua 5.1 and 5.2 installed. There are header files for lua 5.2 in user/include. There are also header files for 5.1 in usr/local/include. There are 5.1 and 5.2 .so libs in usr/lib64. There is also a .a lib for 5.1 in usr/local/lib. I did build lua 5.3 and I did try that in usr/local but I got similar errors about scope. Only a lot more.

What I did to the celestia.pro file to get things working on tumbleweed was
Tumbleweed had lua 5.3.5 installed. On that system I was able to also install 5.1 along with the dev package. But it would not compile using lua 5.3. It would not compile using 5.1 either until I added that last line above. John's version used 5.1 by default so I didn't have this issue. That was with finding spice headers. But this version also has a spice issue. I installed cspice in /usr/local and it still fails the spice test in the configuration. I was able to build this with qt5 creator on tumbleweed. The only issue was the desktop file. It tried to execute celestia. I needed to edit the desktop file to execute Celestia_QT.

cartrite

FYI:

celestia for openSUSE

stable (1.6.1 · gtk)
repository: https://build.opensuse.org/package/show/home:munix9/celestia
download: https://software.opensuse.org/download.html?project=home:munix9&package=celestia
download: https://software.opensuse.org/download.html?project=home:munix9&package=celestia-data

unstable (1.7.0+git · qt5)
repository: https://build.opensuse.org/package/show/home:munix9:unstable/celestia
download: https://software.opensuse.org/download.html?proje ... nix9:unstable&package=celestia
download: https://software.opensuse.org/download.html?proje ... unstable&package=celestia-data

chandra

Hi cartrite!
Thanks for info, I've pushed fixes for review.

Hi chandra!
Thanks for useful links, I remember that guy proposed some changes, at least I've integrated them.

OK, This is interesting. I applied your changes and it builds fine. With qt creator it still sends a message that it found lua53. But the compiler output for every file built showed a DLUA 0x050100. So it looks like 5.1 was used. Also, the Spice test passed in config tests. On Leap 42.3, which is what I just used, I have lua 5.2 and 5.1 installed. I uninstalled 5.3. I only had develop files for 5.1 though. Not sure how that message echoed lua53 though.

I'm gonna switch to Tumbleweed and check what happens there. That has develop files for lua 5.1 and 5.3.

cartrite

Added after 1 hour 41 minutes:
Ok. Tumbleweed did not fair so well with the changes. At first it stopped compiling on one of the files you changed spicerotations.cpp. Here is the terminal output.
I tried to run it again with the original file and it still exited with an error. Dont think it was the same error but.....
When I removed spice from usr/local it did start failing the spice test again but the compilation stopped for not finding the header file used in main.cpp. Anyhow I tried the original files from master and this is the output I was getting with using lua5.3.


Tumbleweed does use a newer compiler gcc8.2. So........ More strict It did build with lua5.1. But now I don't think it had spice support.

cartrite

Added after 1 hour 46 minutes:
Sorry, I screwed up. There is another file called scriptrotation in the celephem folder. I populated a file with the fix for spicerotation and called it scriptrotation.
Unpredictable results.
Anyhow I applied the fixes with the right file names and it built fine. What surprised me was it used lua 5.3 and worked this time. So these fixes seem good on 2 of openSUSE's systems. I built it first on a terminal but just to see how qtcreator would work I built it again. It worked. I wanted to add a screenshot. Notice the bottom left and right. The number of issues and warnings Sorry the warnings on the right had disappeared. There were over 3000. There are 33130 issues though. gcc 8.2.
Most were about issuses with Eigen. On Leap 42.3 which uses a gcc 4.8 compiler there were about 15 warnings. Maybe more but it had 15 through most of the run.



So it looks like these fixes work on this boat.

cartrite

Added after 4 minutes 29 seconds:
I'll need to brush up on Spice operations, put this though some trials to see if everything is working right.

Have a good one .
cartrite

Hi cartrite,

Have you tried to install eigen3 devel package from opensuse repos? I believe you'll have much less number of warnings. I compile using gcc 8 and have just a few warnings in Celestia code.

Correct. Almost no warnings. Is there still a reason to have a thirdparty/Eigen?

cartrite

For windows/os x users. We actually moving away of keeping 3rd party code inside our repo, we'll use git submodules instead.

I installed glew-devel but what package provides fmt?

https://software.opensuse.org/search?q=fmt

https://build.opensuse.org/package/show/home:munix9/fmt

https://software.opensuse.org/download.html?project=home:munix9&package=fmt

chandra