I have found it usually necessary. It is heavily encouraged in CMake, and enforced in SWORD's scripts for just that reason, to do a build from outside of the main source directory in an entirely enclosed environment.
To be truthful, when building with the autofoo toolchain I usually found the same difficulty and got in the habit of building that from a subdirectory as well. In general, you shouldn't need to blow away the directory and start again unless the CMake files have changed or you want to use different options in the build process. As the maintainer of the CMake toolchain, I find myself doing it frequently, but most of the time it shouldn't be necessary. I have made quite a few changes over the past few months, though, to accommodate a number of enhancements, usually related to the bindings. --Greg On Thu, Jan 24, 2013 at 10:20 PM, Andrew Thule <thules...@gmail.com> wrote: > I'm still fairly new to using CMAKE (but liking it). I'm finally starting > to feel comfortable with its use, but still have questions .. so if this is > a newbie question, sorry. > > Using traditional "./configure; make; make install' I could simply grab a > more recent copy (of sword) via svn and make && make install. > > However, I'm finding with CMAKE I have to completely blow away my cmake > build directory before I "cmake -DSWORD_BINDINGS="Perl Python" ../sword". > If I don't, I seem to get never ending compiler/build loops. > > Is it generally necessary to start with a fresh cmake build directory > before make && make install? > > ~A > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page >
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
