On 2014-07-23 14:09, Michael Shepanski wrote:
On 23/07/2014 9:31 PM, Andrey Semashev wrote:
The library build scripts should perform auto-detection checks at build time. I have something like this in Boost.Log, although I test whether the compiler supports SSE/AVX and whether Message Compiler is available. But the approach should be similar - you attempt to compile a test application and set up build macros or select the actual sources to build from.
You can also take a look at Boost.IOStreams which detect if bzip2 and zlib are available. Boost.Thread also contains some auto-detection checks, I think.
Thanks Andrey.
It seems I'll have to lift my Boost.Build skills quite a bit. Fair enough.
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. Just my 2ct. Regards, Roland