Up to now it was only intended to build shared libraries.
But you are right that there might be reasons to link statically.
In that case you can distribute your pvserver (as binary) without the need to install something else.
Attention: There is one exception. You must install "rlsvgcat" to some place where it is found via $PATH if you are useing SVG graphics.
Since pvsid, pvsmt and rllib libraries only use standard c and posix calls there will be no further external dependencies.
You could even add "QMAKE_LFLAGS += -static-libgcc" to the PRO file of your pvserver.
If you build your pvserver for 32 bit it will also run on 64 bit linux.
Thus you should be able to distribute your pvserver with a simple archive which is extracted somewhere. The directory will not matter. It will run on any linux distribution based on x86 either 32 or 64 bit.
I would suggest to include rlsvgcat within that archive.