Added new cmake variable SHARED_LIBRARY. By default is on.
When it is off QCA library, plugins, tools, examples and unittests
will be built as static. Also if is used static Qt plugins will be
built as static. Tested with Qt4.
QCA_LIB_SUFFIX intended to replace workaround
3 major version. For building for Qt5 can be used
-DQCA_LIB_SUFFIX=qt5 for example. Result will be
named libqca2-qt5.so.2.0.3 library for Linux.
Also this suffix will be applied for qca2 pkg config file,
qcatool2 binary and qcatool2 manpage.
I hope that is a good way to resolve the building conflict
against qt4 and qt5.
1. Merge the .h into the .cpp
2. Update the qmake buildsystem to match
3. Add CMake support
4. Update the certificates, which had expired. Once
again, I'm using the test certs from http://openvalidation.org.
svn path=/trunk/kdesupport/qca/; revision=594720
to put the keys/certs back in. With that, it stops
asserting. Then it just fails to compare the messages.
If you encrypt the same data, with the same certs,
twice, you don't get the same result each time.
So I added the decrypt part, including re-use, and
checked that if you encrypt the same data twice, then
each decrypt produces the same result, and that result
is exactly what you started with. The test now passes.
svn path=/trunk/kdesupport/qca/; revision=529009
Message Syntax SecureMessage.
At the moment, it assert()s in the repeated use
of a SecureMessage. Until that is sorted out, it
can't be added to the full test suite.
svn path=/trunk/kdesupport/qca/; revision=528990
