Closed ghost closed 7 years ago
The segfault is related to /usr/lib/klystrack/res not existing. What I do is build with this command: make RES_PATH=.
and then copy the res directory over to where the binary is (the directory itself, rather than just its contents).
Yup, indeed there a line saying this
[WARNING] Can't open bundle '/usr/lib/klystrack/res/Default'
I will make that a fatal error.
By the way, I have no idea what is the correct way to store assets on Linux, so please say if putting them in /usr/lib/ is not good. If there was just an archive with the binary and other files (just like the .zip for Windows) it's obvious but with a .deb package it's less so.
I think that /usr/local
is probably a good place to put klystrack
for installation. you won't have access to /usr/local
without root
privileges so for simple builds (i.e. make all
), I would suggest using a relative path from the Makefile
since the user should have read/write privileges in that location. Otherwise, when installing (i.e. make install
) you should assume root
privileges to install to /usr/local
. At least, this is my opinion...
A quick snippit from TLDP about /usr/local
says the following:
The original idea behind '/usr/local' was to have a separate ('local') '/usr' directory
on every machine besides '/usr', which might be just mounted read-only from
somewhere else. It copies the structure of '/usr'. These days, '/usr/local' is widely
regarded as a good place in which to keep self-compiled or third-party programs.
Hope that helps
That was quite informational. Thanks!
I've tried setting RES_PATH=
when running make
as you mentioned, then making a symlink to from /usr/lib/klystrack
to my klystrack
folder. It seems to work but it is a temporary fix, so I believe until the paths are changed for make all
and make install
you can just leave this open, or create a different issue.
Edit: Actual problem was that I was copying over the themes from the themes directory as opposed to the res directory. Oops haha. ._.
Ah, OK. I was going to suggest you to check the file contents with a hex editor or something, fearing something went broken in the bundling tool.
I am getting some missing file errors when running
make
, they seem all related to athemes
directory.This does not seem to effect the build, but when I run the binary in the
bin.debug
folder I get a core dump.