[sword-devel] Builder Linker Problem

[David Trotz (Integrity Online)]

It works now. I did what you said and everything compiles fine now. I did
however have to change TLIB page size to 256, but now it compiles fine.
I must say C++ Builder and VCL seem to be a much more straightforward
approach to programming GUI's. I like it. What was I ever thinking learning
MFC. I took me three months of blood, sweat and tears to get comfortable
with MFC programming. It is almost backwards to everything I learned about
C++. In VCL I was at home in a matter of hours not months. I still have a
lot to learn but at least I don't feel nearly as dazed as I did with MFC. I
can see this is going to be fun :)
Are you only focusing on the current frontend? What are the plans for the
prototype as it stands now? I can see that I would like to implement some
new options under preferences, that would allow the user to control
background colors, font styles, sizes , and color of each type of window
(bibles, commentaries, etc.) Seperating the color and fonts of these texts
can make it easier for some to determine quickly which view is the bible and
which view is a ccommentary. Perhaps create some default color options to
choose from as well, and an apply to all views option could make changing
all views at once a simple task. Do you see this as something you would like
to see?
In Christ,
David Trotz


----- Original Message -----
From: "Troy A. Griffitts" <scribe@crosswire.org>
To: <sword-devel@crosswire.org>
Sent: Wednesday, May 09, 2001 11:49 PM
Subject: Re: [sword-devel] Builder Linker Problem


> These are additions to the engine that we've done recently and hadn't
> gotten added to the bcb project until yesterday.  My guess is that you
> have at least 2 days old code :)
>
> Try updating to the latest.
>
> -Troy.
>
> PS.  Or maybe I forgot to commit my changes yesterday.
>
> OHHHH!!!!!  Sorry, added them to BibleCS, NOT the prototype project.
> This will be a good place for you to learn the project file.
>
> Select View | ProjectManager
> Then expand swordlib.lib, and you'll see all the cpp files that get
> compiled into the sword library.
> Right-click on swordlib.lib and add to the project.  Select the files
> that you need from the errors below.  You should be able to find them
> under sword/src/*
>
> GBFHeadings is under sword/src/modules/filters
> zCom is under sword/src/modules/comments/zcom
> RawLD4 is under sword/src/modules/lexdict/rawld4
> RawStr4 is under sword/src/modules/common
>
> Then right-click on swordlib.lib and select 'make' and it should build
> and add these new files to the lib.
>
> Hope this helps.  I'll add these and commit soon.
>
>
> > [Linker Error] Unresolved external 'GBFHeadings::~GBFHeadings()'
referenced
> > from C:\SWORD\APPS\WINDOZE\CBUILDER5\PROTOTYPE\SWORDLIB.LIB|swmgr
> > [Linker Error] Unresolved external 'GBFHeadings::GBFHeadings()'
referenced
> > from C:\SWORD\APPS\WINDOZE\CBUILDER5\PROTOTYPE\SWORDLIB.LIB|swmgr
> > [Linker Error] Unresolved external 'zCom::~zCom()' referenced from
> > C:\SWORD\APPS\WINDOZE\CBUILDER5\PROTOTYPE\SWORDLIB.LIB|swmgr
> > [Linker Error] Unresolved external 'RawLD4::~RawLD4()' referenced from
> > C:\SWORD\APPS\WINDOZE\CBUILDER5\PROTOTYPE\SWORDLIB.LIB|swmgr
> > [Linker Error] Unresolved external 'RawStr4::~RawStr4()' referenced from
> > C:\SWORD\APPS\WINDOZE\CBUILDER5\PROTOTYPE\SWORDLIB.LIB|swmgr
> > [Linker Error] Unresolved external 'zCom::zCom(const char *, const char
*,
> > const char *, int, SWCompress *, SWDisplay *)' referenced from
> > C:\SWORD\APPS\WINDOZE\CBUILDER5\PROTOTYPE\SWORDLIB.LIB|swmgr
> > [Linker Error] Unresolved external 'RawLD4::RawLD4(const char *, const
char
> > *, const char *, SWDisplay *)' referenced from
> > C:\SWORD\APPS\WINDOZE\CBUILDER5\PROTOTYPE\SWORDLIB.LIB|swmgr
>