[bt-devel] Windows build system

[Jonathan Marsden]

Greg Hellings wrote:

> The IF(WIN32) .... ELSE(WIN32) .... ENDIF(WIN32) structure shouldn't
> be necessary.  Calls to pkg-config are superfluous if the rest of the
> CMake is written properly - which is should be.  It is more or less an
> exact copy of the CLucene.cmake file, which works fine.  The only real
> problem before was that in WIN32, CMake is pretty much not going to
> find where the libraries might have been built, and the file just
> needs to get far enough to define the SWORD_LIBS and SWORD_LIBRARY_DIR
> as unfound so that the user can manually point the CMake gui to the
> proper location and continue.

Surely the project should not be moving in the direction of a build
process (on any platform) that requires manual human intervention and a
GUI?  Building should be automated so that it can be done nightly from
the SVN tree, for example... and so it can happen on a remote headless
build server.

IMO ideally on Windows you would want to have the build process be
capable of going all the way from a source tree to a built and packaged
resulting software product (an installer.exe or installer.msi file) as
the result of a single command (such as "make", or at worst something
marginally more complex, like "./configure && make && make installer").

Am I misunderstanding your suggestion here?

Jonathan