On Tuesday 14 August 2007, Kern Sibbald wrote: > On Monday 13 August 2007 23:50, Dan Langille wrote: > > On 13 Aug 2007 at 20:06, Martin Simmons wrote: > > > >>>>> On Mon, 13 Aug 2007 13:37:28 -0400, Dan Langille said: > > > > > > > > I'm trying to build Bat on FreeBSD. What configure options did you > > > > use? I have: > > > > > > > > --enable-bat > > > > --with-qwt=/usr/lib > > > > Offlist, and I discovered myself, that this needs to be > > /usr/local/lib > > > > > > I have qt4-4.3.0 installed. > > > > > > Note: (equal "qt" "qwt") => nil > > > > Thanks. Fixed. I'm now using qwt, not qt. cheers. > > > > > > Does this error mean anything to anyone? > > > > ==>Entering directory /usr/home/dan/src/bacula-bat/work/bacula- > > 2.2.0/src/qt-console > > make: don't know how to make depend. Stop > > *** Error code 1 > > You apparently don't have qmake on your path or some similar problem. On > my system, it does the following during the ./configure process: > > make[1]: Entering directory `/home/kern/bacula/k/src/qt-console' > /usr/lib/qt4/bin/qmake -unix -o Makefile bat.pro > > Note, I did have problems building initially when I first hadn't loaded > qt4, because have qt3 loaded on my system so that KDE works. The shell > found qmake (version 3) in /usr/bin/qmake, and of course the build failed. > Worse, once I corrected the problem (loaded the Qt4 libaries), the silly > shell had cached the location of qmake, and not remembering off the top of > my head how to rehash, I simply symbolically linked the /usr/bin/qmake (or > what ever the path was) to the qt4 version. > > I think I added notes to the document on this, probably not as explicitly > as above, but at least the steps I had to take.
bat is an amazing tool and well worth the hours it took to work this out.
Thanks to Dirk, Kern and anyone else that has contributed.
I finally worked out compiling bat on my Centos4 system with a couple of
exports to the depkgs-qt compiled locally. Perhaps this will be of use to
someone.
PATH is set as it is to force the Qt4 qmake to be found before the Qt3 qmake
if the qt-devel package is installed.
====================================================
#!/bin/sh
export PATH="/usr/local/depkgs-qt/qt4/bin:$PATH"
export PKG_CONFIG_PATH="/usr/local/depkgs-qt/qt4/lib/pkgconfig"
CFLAGS="-g -O2 -Wall" \
./configure \
......
--enable-bat \
--with-qwt=/usr/local/depkgs-qt/qwt
====================================================
> > Stop in /usr/home/dan/src/bacula-bat/work/bacula-2.2.0.
> > Creating bat Makefile
> > QMAKESPEC has not been set, so configuration cannot be deduced.
> > Error processing project file: /usr/home/dan/src/bacula-
> > bat/work/bacula-2.2.0/src/qt-console/bat.pro
>
> One slightly frustrating aspect of this project is that when I started it
> in January, Qt4 was released, but KDE was still on Qt3, which means that
> most machines with Qt loaded will have Qt3 rather than Qt4. In looking at
> the time lines, I read that KDE 4.x would be released by June 2007, which
> fit quite well with the bat schedule.
>
> The problem is that we are now in August, bat is released, and no major
> distribution is yet running KDE 4. Some distros like OpenSUSE have Qt4
> installed by default, but I believe that is the exception. It *is*
> possible to build bat on OpenSUSE, Fedora 7, CentOS, and Ubuntu -- I have
> tried them all. Some take more or less work to get things straight as they
> have not all worked out the subtle details of switching from Qt3 to Qt4,
> and in a few such as CentOS, the qwt libraries are not available as a
> distro package.
>
> To resolve all these problems, I've provided a depkgs-qt package that has
> both Qt4 and qwt. The instructions (see the package README) show you how
> to use either just qwt or both qt4 and qwt. Bottom line, if you have too
> many problems, just use the code in depkgs-qt.
>
> I don't regret our decision to use Qt4 for bat in the least because for a
> program like bat, it would be a major effort to upgrade from qt3 to qt4,
> but there are these "early adopter" problems.
>
> Best regards,
>
> Kern
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
--
-- Michael
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
