[sword-devel] Compiling Sword - Linker error

David Trotz Jr sword-devel@crosswire.org
Tue, 22 May 2001 14:25:53 -0400 (EDT)

I am glad you got it to compile using the Standard Edition. That at least say's that it is possible, now we just have to keep it that way. Which shouldn't be too hard. The Object Chart that comes with Borland C++ builder clearly shows which components are only available with the Standard Edition. It would be nice if you could put together a list of steps together that are required to make it compile using the standard edition and maybe Troy will place it in the root directory of BibleCS. Then new comers aren't lost trying to get the program to compile, and they can focus on the program itself. Do you think this is something you would like to do? Also Troy would you be willing to place it on the CVS?
As far as the Install Manager is concerned, I don't know much about it so I guess Troy or someone else can comment on that.
In Christ,

------Original Message------
From: Scott & Karen Newton <sknewton@ihug.co.nz>
To: sword-devel@crosswire.org
Sent: May 19, 2001 9:19:05 PM GMT
Subject: Re: [sword-devel] Compiling Sword - Linker error

Hello David

>     You can safely remove the nmfast50.lib from the libraries that are
> linked. To do so go to Project->Edit Option Source, do a search for the word
> nmfast50.lib and delete the reference to the library. The may be two or more
> locations so be sure to remove all of them, and be sure to leave space
> between the remaining library names when you delete the library name. Now
> save the file and close the page. Compile the program and let me know what
> happens.

It unfortunately wasn't quite as simple as that. I have
got it to compile though. nmfast50 wasn't the only
library :-(( In the end I set Components->Install
Packages->Build with Runtime Packages and
Project->Options->Packages->Build with Runtime Packages
to be vcl50, vcldb50 (not sure this is needed?) and
vclx50 and that seemed to
do the trick.
The only runtime packages you have in standard are
vcl50;vcldb50;vcljpg50;vclsmp50;vclx50. Vcl50 is all the
standard stuff, vclx50 I think is needed because of the
TDDEServerItems Lookup and Search and the TDDEServerConv
Bible (mainfrm.h). Swordlib will compile with just

I also tried compiling the Install Manager. As it
includes things like NMFTP.hpp I couldn't get it to
compile. If you want to enable this to be compiled under
the standard edition then you will probably need to
switch to something like the Indy components
(http://www.nevrona.com/Indy) - they are free
(BSD/Mozilla type license) and are
going to be included in Delphi 6, Kylix and most likely
C++ Builder 6 as well.

I haven't tried compiling anything else.

Hope this all makes sense. I'm fairly new to C++


FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup