Re: [boost] Use of third-party libraries

Subject: Re: [boost] Use of third-party libraries
From: Stephen Kelly (hello_at_[hidden])
Date: 2014-07-23 09:19:29

Michael Shepanski wrote:

> On 23/07/2014, at 10:54 PM, Roland Bock <rbock_at_[hidden]> wrote:
> 
>> On 2014-07-23 14:09, Michael Shepanski wrote:
>>> 
>>> 
>>> 
>>> Also I'm thinking that my approach of having separate backend
>>> libraries is not right. The idea had been that a user decides which
>>> backend library to download and build, but that is not going to be
>>> happening a boost context. Everything should be in the "quince"
>>> library, every user downloads it all, and its build script decides
>>> which components to build.
>> Hi Michael,
>> 
>> There's also MySQL and MariaDb and Oracle and TransactSQL and Firebird
>> and BerceleyDB and I don't know how many else, but a lot. To me it does
>> not sound like a good idea to have all backends in one giant library.
> 
> I don't have any strong opinions about this, and I'm happy to go with the
> conventional approach -- as soon as I know what that is.

For a data point, the approach in sqlate is to generate strings from the 
edsl and delegate the query handling to third party drivers (sqlate doesn't 
depend on Qt, but the test does)

 https://github.com/KDAB/sqlate/blob/master/tests/selecttest.cpp

If the interface of your library only creates strings, you can similarly 
allow users of it to use the Qt drivers, your drivers from somewhere 
separate, something else entirely, or whatever comes out of the ISO DB SG.

Thanks,

Steve.