BCB6 is freely available with a personal license - and such can be used as long as sword is not involved in commercial activity (I do not know whether it still holds or how long it will hold). I believe that the best thing for an OpenSource project is to use free and generally available tools so that anyone can join the project without additional cost to buy tools. But for now what options do we have for BibleCS? Is it Borland or nothing? Should BibleCS be abbandoned in favour of BibleDesktop or BibleStudy?
I'm really pleased to see quite a number of people trying hard BCB6. I do not know about their motives (mine was simply to get a bleeding edge build of Biblecs/tools), but I hope that maybe someone is actually interested in developement.
I can also confirm, that BibleCS builds out of the SVN on BCB6 without problems, and works quite stable (a lot better then the 1.5.8pre3 from the february).
I do also confirm that there are problems with tools built with BCB6. the build files where directly derived from the BCB5 files but unfortunatelly it does not work - a memory corruption accurs (those interested in the details can look back in the sword-devel mailing list). I suspect that some compiler options need to be adjusted as it is said to work fine on BCB5.
Unfortunatelly I have to confirm that sword does not build in recent Cygwin baling out on configure script during Makefile generation.
-------
checking for curl-config... /usr/bin/curl-config
curl found - remote install options available
configure: creating ./config.status
config.status: creating Makefile
config.status: creating lib/Makefile
config.status: creating tests/Makefile
config.status: creating tests/cppunit/Makefile
config.status: creating \
.infig.status: error: cannot find input file: \
-----
Greetings
Christopher.
----- Original Message ----- From: "Chris Little" <[EMAIL PROTECTED]>
To: "SWORD Developers' Collaboration Forum" <[email protected]>
Sent: Tuesday, April 19, 2005 2:44 AM
Subject: Re: [sword-devel] Information for beginning Windows BCB 6 Developers
To clarify, I believe Troy is confirming that BibleCS builds fine using BCB6. I don't think he's making a statement about building the utils, which may still need project work.[...]
Maybe we should take up a collection to buy Troy a copy of BCB6 so we can all move forward and abandon BCB5 as the supported platform. On the other hand, I think I can state accurately that BCB6 is going to be the last supported Borland C++ environment. I think BCBX is well and dead. So it might be best to move on and accept that Borland C++ is entirely dead. :)
And BTW, you CAN also use VC++ to build the utils. Or Cygwin. And probably MinGW. So if something other than BibleCS was your build objective, there are better alternatives to Borland anyway.
_______________________________________________ sword-devel mailing list: [email protected] http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
