[bt-devel] Re: trouble building with custom KDEDIR

[fred]

Tim Brodie wrote:

> I initially went this route, and after a while gave up.  There was
> just too many dependant packages that had to be upgraded in the rh
> 6.2 world to make it work right.  I was getting weird problems
> happening during execution that nobody else seemed to experience.
> (I'm hoping that it's just a development environment set of issues,
> and that Fred will be able to get rid of most of the problems via
> a proper binary distribution to enable us to run on rh6.2.)

I am not experimenting with verious comlpiles, that is Brook.
Coding in C is beyond me just now, so I am sticking to documentation.
Fred Saalbach

>
>
> I moved to Mandrake 8.0 on my development platform, and never looked
> back.  I could move my focus from fixing environmental problems to
> working on the project.  In fact, I've decided that (for my day-job)
> my front-office workstation distribution will be Mandrake 8.0, while
> my back-office server version remains rh6.2 with kernel 2.2.16-3 due
> largely to my development experiences joining this project.
>
> I'm currently working hard at gaining C++ skills during the current
> code freeze before we start forward on v1.1.
> Steve Oualline/_Practical C++ Programming_/O'Reilly has been of
> great help to me.  I never really understood the merits of C++
> from a development perspective; it seemed more a tomatoe/tomatuh
> issue to me.  But Oualline really has explained well the real
> advantages to C++ that has gave me really motivation to master
> the language.
>
> I have a list of package upgrades I did on rh6.2 to make BibleTime
> *appear* to work (at home), but wasn't able to eliminate the
> niggley problems (example: intermittent segment violations that
> don't occur with the same source on my Mandrake box.
>
> I know moving to another distribution can be pretty painful, but
> I found it well worth it.
>
> Hope this helps...
>
> Tim
>
> PS: The KDE prefix in rh is /usr; qt can be installed anywhere but
> liked /usr/local/qt just fine.  Doing a 'make distclean' will get
> rid of all caches and ensure when you do a './configure' will pick
> up sources you spec with env vars 'KDEDIR' 'QTDIR'.
>
> ----- Original Message -----
> From: <mg.pub@gmx.net>
> To: <bt-devel@crosswire.org>
> Sent: Friday, June 08, 2001 7:53 AM
> Subject: Re: [bt-devel] Re: trouble building with custom KDEDIR
>
> > Hi Mark,
> >
> > try using
> >
> > rm config.cache
> >
> configure --prefix=/usr/local/kde2.1.1/ --with-qt-dir=/home/mark/sw/qt-2.2.4
> >
> > this tells configure which paths to use.
> >
> > Martin
> >
> > >
> > > Hi all,
> > >
> > > I'm having a little trouble building the BibleTime software from CVS.
> > > I'm running RH 6.2 with RPM KDE 2.0.1 installed, but also use a source
> > > build KDE 2.1.1 distribution.  The configure doesn't seem to be finding
> > > my KDE source build which is located in /usr/local/kde2.1.1/. I made
> > > sure that KDEDIR is set properly, but it still seems to be picking up
> > > the RPM version in /usr. Any hints or suggestions on how I can get it to
> > > find KDE would be helpfull. Btw, I'm also using a source built QT 2.2.4
> > > in /home/mark/sw/qt-2.2.4, and the configure seems to pick that up just
> > > fine.
> > >
> > > Thanks!
> > > Mark
> > >
> > >
> >
> > --
> > Machen Sie Ihr Hobby zu Geld bei unserem Partner 1&1!
> > http://profiseller.de/info/index.php3?ac=OM.PS.PS003K00596T0409a
> >
> > --
> > GMX - Die Kommunikationsplattform im Internet.
> > http://www.gmx.net