[sword-devel] Question about CMAKE build proceedures
thulester at gmail.com
Fri Jan 25 08:48:05 MST 2013
Different tools, different philosophies - so it's nice to understand the
thinking behind the tool.
One thing to be said for Cmake builds, is the build information is so
On Thursday, January 24, 2013, Greg Hellings wrote:
> 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.
> > 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?
>> 'cvml', 'sword-devel at crosswire.org');>
>> Instructions to unsubscribe/change your settings at above page
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the sword-devel