[bt-devel] New release date of version 1.0

Brook Humphrey bt-devel@crosswire.org
Sun, 17 Jun 2001 18:20:13 -0700


On Thursday 14 June 2001 04:24 am, you wrote:
> Hi!
>
> We have now a environment variable BT_PATH which is used for the static
> build. The static build should use a script which sets BT_PATH to the
> install location of BibleTime and which calls then the real BibleTime
> executable. $KDEDIRS should be set by the script to the directory where
> BibleTime is tnstalled.
>
> The binary with support for static build should be created similair to
> this:

Ok bibletime worked dynamic and sword works.
Sword is in this one as static.


>
> make -f Makefile.cvs
> CPPFLAGS="-DSTATIC_BUILD" ./configure
> make

Getting ready to compile this is there anything else I should add to the 
line. When I get done I will install redhat or mandrake without kde and try 
it to make sure it works.

>
> I gave it some more testing. I got it working with alls icons, menu
> entries, HTML files etc.
>
> BUT: The save, open etc. file dialogs (the KDE standard one) is NOT working
> because the mimtype database is not available and because dcopserver,
> kdeinit etc. are not running.
>
> I introduced now two new methods CToolClass:getSaveFileName and
> CToolClass::getOpenFileName which class KFileDialog or QFileDialog
> depending on the value of STATIC_BUILD (we use #ifdefs). Testing has wshown
> that this work around is working.
>
> But I don't know if a static build is different in some way because I
> cannot test with a real static build.
>
> Joachim
>
> > > I've been gone for  a few days. The current build works fine with sword
> > > only static but my system was complaining about some libs that are
> > > already installed for the complete static build. I should be able to
> > > work on it a little this week but I won't have much time till sunday to
> > > try and work out the static build problems.
> >
> > What I want to be sure of is that the static build is actually working
> > and usable.
> > Joachim, looks like you'll have to test on your own.
> > IMO this issue is really very important. We may have to move the release
> > date again if it's not working. (I hope this won't be necessary... ;)
> >
> > Martin