Hello,

 I've somehow missed the commits 6908e473ff2da566d335f23015b971c7f2118239
and 094e19c68c0c98cfc862bb316868552a7443d145, but trying to use the latest
SOCI version in our code now, I realize that it's a problem to have
soci-config.h and version.h to be generated by cmake for us because we
can't build SOCI any longer simply using our own make/project files as we
always did so far.

 IMHO it never was a problem in practice to specify SOCI_HAVE_BOOST and I
don't really see what do we gain from having it in a generated file instead
of on the command line, but I could live with it if we also had something
like SOCI_HAVE_CONFIG_H that would be tested before including this file as
this would still allow me to compile the sources directly as before. Would
there be any objections to doing this?

 As for version.h, I just don't see what's the benefit of generating it at
all... Could someone (Arnaud?) please explain it or could we perhaps just
revert 094e19c68c0c98cfc862bb316868552a7443d145?

 Thanks in advance,
VZ

Attachment: pgpCsk2_TTL29.pgp
Description: PGP signature

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
soci-devel mailing list
soci-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/soci-devel

Reply via email to