[odb-users] Problem compiling applications when Qt is built
without STL compatibility
Shantanu Tushar Jha
shantanu at kde.org
Sat Feb 1 01:53:55 EST 2014
Thanks for the quick reply! I tested the tarball you linked to, seems to
work fine :)
Also, another appreciation I have for ODB is that the manual at
http://codesynthesis.com/products/odb/doc/manual.xhtml is very good, we
couldn't use other C++ ORMs because their docs were very confusing. Plus
there is support for Qt/sqlite which just works (TM).
On Sat, Feb 1, 2014 at 10:37 AM, Boris Kolpackov <boris at codesynthesis.com>wrote:
> Hi Shantanu Tushar,
> Shantanu Tushar Jha <shantanu at kde.org> writes:
> > We are using ODB for Plasma Media Center in the KDE project.
> That's pretty cool. Let us know if you find any other issues with
> using ODB in projects like this.
> > Follwing advice from a stackoverflow post, we have come up with a
> > patch for libodb-qt which seems to work.
> > Now, for packaging we can either request distros to manually apply this
> > patch to ODB packages, or is it possible for this to be applied upstream?
> Yes, the more portable ODB is the better. I've applied a slightly
> modified version of your patch (used toLatin1() instead of toUtf8()
> and added a comment explaining why we can't use toStdString()):
> I've also packaged libodb-qt with the fix:
> If you could try it and let me know if everything works on your side,
> then I can publish it as a 2.3.1 bug-fix release.
Shantanu Tushar (UTC +0530)
More information about the odb-users