historyReadRawModified has an extra diagnostics argument since SDK v1.4
UAF now compatible with SDK v1.4
Merge pull request #14 from WimPessemier/compatibility_with_sdk_1.4

Compatibility with sdk 1.4
handle command line options (new macro), handle libxml2 (wasnt strictly needed with old stack), and cleanup/add some logging
added a macro to handle command line options, and make the SDK v1.4 required from now on
%include opcua_config.h so we can access the definitions also in the SWIG wrappers
remove the preprocessor instructions: the SDK v1.4 is now mandatory
xmlparser does not need to be linked
the LibXml2 and OpenSSL libraries are now always linked
LibXml2 must be found by cmake
moved from UaDemoServer to uaservercpp
added info that the custom SDK building options must be used for building the UAF too
Merge pull request #15 from WimPessemier/compatibility_with_sdk_1.4

Compatibility with sdk 1.4: some bugfixes: (py)UAF compiles now with the SDK v1.4, and basic examples seem to work in Linux.
added a generated file
store and check the path to the UaServerCPP demo server
copy the demoserver.py file to the unittests/pyuaf directory
added python software to command the demo server
the new unittests (compatible with UaServerCPP of the SDKv1.4 instead of UaDemoServer of the SDKv1.3) will be put in this directory
demoserver can't easily be started/stopped in Windows, so we remove our DemoServerRunner software, and require the demo server to be run manually
If no starting points of relative paths can be resolved, previously an unexpected error was raised.
However this should only result in a ReadResult/WriteResult/... with a bad overallStatus. It should
not immidiately result in a bad "client-side" error (corresponding to an exception in PyUAF), because
the problem may well be on the server side.