Compiling Celestia puts absolute paths in the exe

[Johan]

Hi all,

If I compile Celestia undeer Linux and move its directory, I get this message :

Code: Select all

$ bin/celestia
kbuildsycoca running...
DCOP Cleaning up dead connections.
Cannot chdir to '/data/users/jee/Celestia_SVN_RH4_KDE/share/celestia', probably due to improper installation
DCOP aborting call from 'anonymous-7034' to 'celestia'


It seems that the binary contains absolute paths like /usr/lib or the path where I compiled it. I see it with this command for example:

Code: Select all

$strings bin/celestia | grep share
/usr/local/share/lua/5.1/lua;/data/users/jee/Celestia_SVN_RH4_KDE/share/celestia;/data/users/jee/Celestia_SVN_RH4_KDE/share/locale


What can I do to have a "portable" Celestia under linux ?

Thanks in advance,

Johan (SpaceBel)

[John Van Vliet]

--- edit ---

[Johan]

Hi, thanks for answering.

I want to compile Celestia on a computer and then give it to users who install it wherever they want, without administrator right. Actually it's like puting it on an usb key.

I found the -dir <sharedir> option for Celestia, but the splashscreen image is not found, there is also the -s option to disable splashscreen. Maybe it's my solution.

[John Van Vliet]

--- edit ---

[selden]

My personal opinion is that there should be no need to invoke administrative privileges to install Celestia. That's just asking for trouble. It's too easy for malware to compromise an installation kit and then compromise whatever system it's installed on. Celestia does not need any special privileges to run and the installation procedure shouldn't either.

[John Van Vliet]

--- edit ---

[selden]

My personal opinion is that there should be no need to invoke administrative privileges to install Celestia

for a rpm or deb you DO need to have root access using su -, sodo,visudo, . pick one .
Now if you do build a Generic .zip file ( with all of the prerequisites in the celestia folder [--with glut ] ) then only getting Cell:\\something-something to work will need root access for SELinux or AppGuard/AppArmor

You should only need root if you write to system directories, which I think is what you're saying. Installing random software binaries with privileges enabled is asking for trouble, even if it's a package someone decided to call Celestia.

Not too long ago, I found packages with that name on many random Web sites. They were pointing to local copies, not to SourceForge. Who knows what was in them. A novice certainly wouldn't.

I think it would be best if all versions of Celestia for all platforms could avoid needing a privileged install of any kind. At least that way when one shows up claiming to need them, it can immediately be identified as being bogus.

But that's probably too much to ask

[John Van Vliet]

--- edit ---

[Johan]

Well I agree with Selden, and moreover I think it's better to distribute a package needing no administrator rights, because imagine someone who is at work and who wants to install Celestia without asking permission to his boss
There is the problem of prerequisites, in my case all people will have the same OS, so the aim is to have a simple way to install, delivering some missing libraries in a local folder if needed.

[Johan]

I lose my menu bar in Celestia under kde, what did I do??

[Johan]

It would be fine if CONFIG_DATA_DIR was read in a file instead off defined at compilation with -DCONFIG_DATA_DIR='"$(PKGDATADIR)"'

[John Van Vliet]

--- edit ---