Hello!
Summary: a backwards incompatible change in signon-qt has entered MeeGo
Trunk, apps using it need to be updated and recompiled.
Details: I just noticed that one of my executables using signon-qt
stopped working after an update to recent MeeGo Trunk: it starts, but
fails to connect to
On Mi, 2010-12-08 at 08:08 +, Patrick Ohly wrote:
The reason is that the signon-qt API was cleaned up. It now provides
SignOn::AuthService::identities(const QListSignOn::IdentityInfo ),
with namespace for IdentityInfo. Same for Error and SessionData.
Error now is passed by value, so use
Em Quarta-feira, 8 de Dezembro de 2010, às 10:09:32, Patrick Ohly escreveu:
Error now is passed by value, so use SignOn::Error, not const
SignOn::Error .
That's the same thing for Qt's signal-slot mechanism. It's actually
recommended that you write T instead of const T and use no spaces around
On 12/08/2010 10:08 AM, ext Patrick Ohly wrote:
Note that the soname of signon-qt wasn't changed, so my executable
continued to run. I would have preferred to get a libsignon-qt.so.1 not
found error. I was expecting this change to happen and knew what to
look for, but others might spend more