On 6 December 2012 16:06, Philipp Kraus <[email protected]> wrote: > > Why don't you use on the include and the library the path value? At the > moment it is different. IMHO should be on both flags the path value or it > should be the full path to the files.
This is how CMake handles these paths. It is not imposed by SOCI configuration. So, you may want to find out asking CMake folks. In fact, despite I knew how it works, I wasn't sure about the rationale myself and I asked on CMake mailing list. Here [1] is the answer I received: "For libraries cmake needs to know the absolute path if possible to setup proper dependencies in target_link_libraries and to make sure that the linker links against exactly that library and not some library with the same name that happens to be in a directory further in the front of the linker commandline. For include directories things are different, since the mechanism for those is different. In particular the pre-processor does not allow include files to be listed on the commandline. Instead you give it a couple of directories where to search. Dependencies of this are generated by CMake parsing the source files." [1] http://www.cmake.org/pipermail/cmake/2012-December/052913.html If you feel you need more details, please post your questions to CMake list. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
