On Fri, 2010-10-15 at 13:12 +0200, Patrick Ohly wrote: > On Fri, 2010-10-15 at 11:40 +0100, Alberto Mardegan wrote: > > > The connect() also looks right: > > > > > > connect(m_service, SIGNAL(identities(const > > > QList<SignOn::IdentityInfo>& )), > > > this, SLOT(identities(const QList<SignOn::IdentityInfo>& > > > ))); > > > > Note the namespace, it has been added recently. > > Looks like you are using the headers from a more recent version than the > > binaries. > > Yeah, that's it. The example code was recent (with namespace), the > development files and libs were old. Sorry, I forgot that Qt basically > deals with strings in its signal/slot mechanism.
BTW, did you bump the .so version while making that change? It breaks apps compiled against the old API. Currently I have: # ls -l /usr/lib/libsignon-qt.so* lrwxrwxrwx 1 root root 21 Oct 15 08:32 /usr/lib/libsignon-qt.so -> libsignon-qt.so.1.0.0 lrwxrwxrwx 1 root root 21 Oct 15 08:32 /usr/lib/libsignon-qt.so.1 -> libsignon-qt.so.1.0.0 lrwxrwxrwx 1 root root 21 Oct 15 08:32 /usr/lib/libsignon-qt.so.1.0 -> libsignon-qt.so.1.0.0 -rwxr-xr-x 1 root root 172700 Oct 14 15:59 /usr/lib/libsignon-qt.so.1.0.0 Of course this all depends on whether the current API is considered experimental. The old one is currently in MeeGo 1.1. If it stays there, then I definitely would expect MeeGo 1.2 to have a libsignon-qt with a different soname. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
