genfile commands would still not terminate properly
or would end up de-synced with the host in one way
or another.
the GEN_FILE sub-protocol has been updated to
address these issues by having the direction of the
genfile data defined in NEW_CMD so this client will
now know if the command uploads to the host or
downloads from the host when it is defined instead
of trying to determine that at runtime.
updated all documentation related to the GEN_FILE
sub-protocol to reflect these changes.
I learned the Qt binaries directory can end up in a non-standard
directory seperate from the Qt libaries and plugins and this kind of
setup would cause the script to fail to copy all needed files. To fix
this, i hard coded the standard directory:
'/usr/lib/x86_64-linux-gnu/qt5/bin' into the script instead of having
it call qtpaths.
Ended users that have even further customized setups will need modify
the build script themselves to make sure all references to $qt_dir
points to the correct directory for their dev setup.
Found issues with missing library files while testing on a clean system running
Ubuntu 19.04 that doesn't have the Qt library development packages installed.
However, even with libqxcb.so and libQt5XcbQpa.so added to install directory,
the client still would not start complaining about mixed Qt library versions. I
then finally decided to build the client on the debian official Qt5.7.1 package,
added libQt5DBus.so, libGL.so, libpcre16.so, all plugins in xcbglintegrations
and that worked.
The build script will now get the Qt bin directory via 'qtpaths' if not given.
Moved the LICENSE.md file to the root directory so github can now read it.
