On 12 February 2013 01:04, Simon Walter <[email protected]> wrote: > > (I'm doing it wrong.) > > I've read about this on this mailing list as well. Some files have a: > #include "soci-backend.h" > > However once installed, it looks like this: > /usr/local/include/soci/soci-backend.h > /usr/local/include/soci/mysql/soci-mysql.h
Yes, this is because SOCI includes headers with very common names (error.h, version.h), so it's sort of a workaround to hide them, and request users to specify number of include directories pointing deep into these /soci, and /soci/mysql folder directly. > There is no soci-backend.h in /usr/local/include/soci/mysql/. Hence we > see errors when including. Is this simply a difference with the install > dirs and the build dirs? It is indeed. > I honestly thought there was a bug of some sort > and would always edit the headers until I read on this mailing list that > one should use a custom path (ugly IMHO). Excuse me for my ignorance, > but why is it done that way? I can't tell why, but I agree it's a huge annoyance (Debian says it's a bug). Let's assume these issues are ghosts of the past, and we've planned to get rid of them: https://github.com/SOCI/soci/issues/25 (open for discussion there) ATM, I'm pulling SOCI 3.2.0 as major bugfix release, which is due the end of this month. Next, taking off with modifying the source tree layout, install layout and implementing the buried headers SOCI 4.0.0. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
