new pinentry release with qt4 support?
bernhard at intevation.de
Wed Jul 8 15:39:03 CEST 2009
Am Samstag, 27. Juni 2009 11:18:38 schrieb Marcus Brinkmann:
> Rex Dieter wrote:
> >> Simply go to the qt4 directory and execute moc manually:
> >> moc pinentrydialog.h > pinentrydialog.moc
> >> moc qsecurelineedit.h > qsecurelineedit.moc
> > Eww... that's far from ideal. This will likely trip up most folks
> > building the qt4 frontend, hopefully a better solution will come along
> > soon.
> > *cough* cmake? *cough* :)
> If you can't say it without coughing, it ain't gonna happen :)
> If you know how to improve the configure checks, you know where to send
> patches. Heck, if it's possible to run cmake from configure that could
> even be an option, too. But the i586-mingw32msvc cross-compilation case
> needs to work (that is _our_ requirement). Apart from that, my only idea
> is to remove pinentry-qt(3), which could make writing configure checks
We must keep pinentry-qt3, has KDE35 is still the stable and recommended
version in many distributions.
> It's true that we spoiled the most simple case, but we just don't have the
> resources to cover all the cases, and the help from people who know what
> the qt folks are up to is required here (but they are not interested in
> autoconf :-/).
Qt folks are trying to be nice as well. If you can summarize the problem
they'll sure help it to a solution. Without diving into it too much it looks
like adding a manual run for these two files is not too problematic, is it?
Managing Director - Owner: www.intevation.net (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 198 bytes
Desc: This is a digitally signed message part.
More information about the Gnupg-devel