Aside from the fact that BibleCS wouldn't build with Borland C++ Compiler 5.5 because of lack of VCL, as I mentioned in my previous reply, that Makefile isn't functional. I don't have any idea what it's doing in that directory.

As a purely philosophical answer to why make isn't working, it requires GNU Make. GNU Make would actually be able to interpret the makefile correctly. To build from CVS using GNU tools, you also need to run autoconf & automake (then configure, then make). GNU tools such as mingw and cygwin should work for building Sword and diatheke. (I know cygwin will work, but haven't tested mingw myself.) But you still can't build BibleCS (same reason as above applies).

--Chris

Lynn Allan wrote:

Inquiring (newbie) minds want to know:
* Is there a procedure documented somewhat to rebuild BibleCS (win32) using
the Borland CBuilder 5.5 command line compiler?

As part of getting up to speed with the sword-api, I've attempted to rebuild
BibleCs (win32) with CBuilder. No doubt there is operator error on my part,
but I'm baffled how to even get started. Using:
{root}\apps\windoze\CBuilder5\BibleCS\Makefile
the CBuilder make process pretty much immediately fails due to missing
include ${root}/Makefile.cfg

My impression is that there is a linux oriented .sh script that is supposed
to generate the Makefile.cfg. Was this left out of CVS? Is a win-32
developer wannabe supposed to have gnu or cygwin tools installed, and be
capable of generating {root}/Makefile.cfg?


_______________________________________________ sword-devel mailing list [EMAIL PROTECTED] http://www.crosswire.org/mailman/listinfo/sword-devel


_______________________________________________
sword-devel mailing list
[EMAIL PROTECTED]
http://www.crosswire.org/mailman/listinfo/sword-devel

Reply via email to