[sane-devel] Re: QuiteInsane

[Michael Herder]

Till Kamppeter, Samstag, 30. November 2002 22:58:
> I forward your mail to Michael Herder and the SANE guys. So I hope
> someone there can help you.

I'm not sure, that I understand this mail :-/ Are you talking about my 
ChangeLog entry "Replaced KPrinter with QPrinter, when linked with KDE libs, 
because KPrinter caused trouble and crashes all the time without an obvious 
reason." ?
Btw, I do not blame KPrinter for this. I will contact Michael Goffioul to 
clarify this.
Just some comments:
1. It should not be necessary to modify configure.in in to link with Qt3.
Just set QTDIR correctly.
2. When you're running KDE3 and want to link with Qt3, then configure with 
"--enable-mt" (KDE3 normally uses the Qt3 lib with thread support). Otherwise 
you will
2.1. link with a qt3 lib *without* thread support (if installed)
or
2.2. you will get an error message, that qt2 wasn't found (misleading).
3. If you want to run QuiteInsane under KDE3, you should also configure
with "disable-qt-styles". Don't use "--enable-kde-app" in this case. Qt3 apps 
can use the same style like KDE3 apps *without* linking to KDE3 libs.

Or shorter:
If you want to run QuiteInsane under KDE3 do:
configure --enable-mt --disable-qt-styles

bb
Michael
 
>     Till
>
> Goffioul Michael wrote:
> > Hi,
> >
> > I had a look at quiteinsane, but the problem is that I can't try it as I
> > don't have any scanner. And the application cannot be run without a
> > device. So if one of you could do the test for me and report any
> > backtrace, it would be nice. I don't know if the crash they talk about
> > happens under KDE-2.2.x and/or KDE-3.x, but I suggest to try it under
> > KDE-3.X, as there won't be any new KDE-2.X version released.
> > To compile quiteinsane with KDE-3.X, you need to:
> > 1) edit configure.in and replace "KDE_USE_QT(2)" with "KDE_USE_QT(3)"
> > 2) run "make -f Makefile.cvs"
> > 3) configure using "--enable-kde-app"
> > 4) replace any occurence of qprinter.h/QPrinter with kprinter.h/KPrinter
> > in the code.
> >
> > At this moment, I cannot do much without any backtrace and being able to
> > run the app.