Why in the main .so files?
main$ tree
.
|-- cgame.so
|-- game.so
|-- ui.so
-- vm
-- ui.qvm
|-- cgame.qvm
|-- game.qvm
why should they? without them works too!
main directory
main directory
Re: main directory
*.so files offer more performance and allow debugging via a debugger. Downside is that they are platform specific. qvms on the other hand are platform independent, and are therefore the preferred method of distributing releases. We use the *.so files for dev work though.
Re: main directory
Ishq wrote:*.so files offer more performance and allow debugging via a debugger. Downside is that they are platform specific. qvms on the other hand are platform independent, and are therefore the preferred method of distributing releases. We use the *.so files for dev work though.
I want to raise game for your Linux distribution and game files I want to put in a separate package. I want to place the binaries in /usr/lib/Unvanquished for 32-bit. and /usr/lib64/Unvanquished for 64-bit. system and game files in /usr/share/Unvanquished. that would run the game to make reference ln -s /usr/share/Unvanquished /usr/lib${LIBDIRSUFFIX}/Unvanquished/main, and *. so files interfere. Tried to use +set fs_libpath and +set fs_basepath, did not help.
Re: main directory
For an example of how to set up packages, check out the debian directory and our debian packages.
Re: main directory
Ishq wrote:For an example of how to set up packages, check out the debian directory and our debian packages.
Thank you, I will watch!