On 2014-07-25 09:49, Gavin Lambert wrote:
On 25/07/2014 18:53, Michael Shepanski wrote:
Assuming there is no backend for the database I am interested in, I might want to have quince core in order to develop that backend. I therefore think that quince core should always be built.
In that case, sooner or later you're going to have to tweak quince's jam file, to make the building of your backend contingent on the presence of some third-party library (fron MySQL or Oracle or whatever).
You're assuming that all backends must be built as part of the quince tree.
What if I wanted to write a backend private to a particular application and never intended to be published (perhaps it's some proprietary data format rather than a "real" database)?
If the core were always built, it could be used with a custom backend that quince's jam file knows nothing about. (Provided that the core itself doesn't have to be modified to add a new backend -- but I would hope that's true as it's part of standard coding principles.)
My thoughts exactly :-)