On 12/09/10 00:59, Denis Arnaud wrote: > 2010/9/12 Mateusz Loskot <[email protected] <mailto:[email protected]>> > > > 1. A small thing: usually (for other projects using CMake), there > is no > > "build" directory, as it is the one we create to build temporary > objects > > with CMake and makefiles. So, we could maybe rename that directory? > > Yes, indeed. Are you referring to the setting in root CMakeLists.txt: > > > In pristine Boost (http://svn.boost.org/svn/boost/trunk), for instance, > the build tools are located in a tools/build sub-directory. Hence, there > is no "build" directory directly under the root directory. It is the > same in the CMake-enabled Boost > (git://gitorious.org/~zeuner/boost/zeuners-boost-cmake.git > <git://gitorious.org/%7Ezeuner/boost/zeuners-boost-cmake.git>). > To be clear, the usual way to build a project with CMake (at least, from > what I saw until now) is something like: > cd <myproject root directory> > mkdir build > cd build > cmake .. > make > cd .. > # Clean everything > rm -rf build
I see your point. Once the CMake configuration is ready, the build directory with VS projects, etc. will just go and the problem will be solved. BTW, I build this way: git pull <URL> soci-src mkdir build cd build cmake ../soci-src Certainly, no difference to your approach. Except, in my case there is no clash with currently existing build directory. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
