Re: QT compile problems.
Aide == Aide Florent [EMAIL PROTECTED] writes: Aide Hi, translations. By making the french translation up to date you will get more/all the english strings into french. Aide I looked into the fr.po file but everything is correctly Aide translated... Maybe the po file needs to be regenerated to Aide reflect the new strings ? Florent, if you want to help on translation for 1.3.0cvs, please contact [EMAIL PROTECTED], who is in charge of docs and interface translation for now. Maybe he can use some help, but I bet that he is waiting for the first prerelease before updating fr.po. JMarc
Re: QT compile problems.
Aide == Aide Florent [EMAIL PROTECTED] writes: Aide Hi, translations. By making the french translation up to date you will get more/all the english strings into french. Aide I looked into the fr.po file but everything is correctly Aide translated... Maybe the po file needs to be regenerated to Aide reflect the new strings ? Florent, if you want to help on translation for 1.3.0cvs, please contact [EMAIL PROTECTED], who is in charge of docs and interface translation for now. Maybe he can use some help, but I bet that he is waiting for the first prerelease before updating fr.po. JMarc
Re: QT compile problems.
> "Aide" == Aide Florent <[EMAIL PROTECTED]> writes: Aide> Hi, >> translations. By making the french translation up to date you will >> get more/all the english strings into french. Aide> I looked into the fr.po file but everything is correctly Aide> translated... Maybe the po file needs to be regenerated to Aide> reflect the "new" strings ? Florent, if you want to help on translation for 1.3.0cvs, please contact [EMAIL PROTECTED], who is in charge of docs and interface translation for now. Maybe he can use some help, but I bet that he is waiting for the first prerelease before updating fr.po. JMarc
Re: QT compile problems.
Aide Florent [EMAIL PROTECTED] writes: | Hi, | | translations. By making the french translation up to date you will get | more/all the english strings into french. | | I looked into the fr.po file but everything is correctly translated... | Maybe the po file needs to be regenerated to reflect the new strings ? fuzzy: #: src/frontends/qt2/QDocumentDialog.C:276 #, fuzzy msgid Papersize and Orientation msgstr Orientation #: ../src/frontends/qt2/ui/PaperModuleBase.ui:84 #, fuzzy msgid Paper size msgstr Taille : #: ../src/frontends/xforms/forms/form_document.fd:170 #, fuzzy msgid Use Class Defaults|#C msgstr Valeurs par Défaut de la Classe|#f fuzzy means that the translation is suspect and that the entries must be checked and verified (by removing the fuzzy mark) by an translator. -- Lgb
Re: QT compile problems.
On Mon, 9 Dec 2002 15:50:46 +0100 Andre Poenitz [EMAIL PROTECTED] wrote: On Mon, Dec 09, 2002 at 11:39:15AM -0300, John Coppens wrote: I'm not sure I'm capable of modifying the code and getting it to work. But maybe it wouldn't be bad to warn people of the state it's in, instead of giving the option in the configure script. Well, one usually starts of with giving an option in the configure script and work out the problems that emerge... Maybe - just a hint - add a comment at the end of the 'configure' run, in the table where the final config is shown (Front-end:Gnome), add a warning there... This is one of the few places most people do read, I think ;-) About the rest. I'll have a real good look at the problem first. I don't use Gnome or KDE either (I'm running IceWM at the moment). But I do generally like way GTK+ does things. Cheers, John
Re: QT compile problems.
Aide Florent [EMAIL PROTECTED] writes: | Hi, | | translations. By making the french translation up to date you will get | more/all the english strings into french. | | I looked into the fr.po file but everything is correctly translated... | Maybe the po file needs to be regenerated to reflect the new strings ? fuzzy: #: src/frontends/qt2/QDocumentDialog.C:276 #, fuzzy msgid Papersize and Orientation msgstr Orientation #: ../src/frontends/qt2/ui/PaperModuleBase.ui:84 #, fuzzy msgid Paper size msgstr Taille : #: ../src/frontends/xforms/forms/form_document.fd:170 #, fuzzy msgid Use Class Defaults|#C msgstr Valeurs par Défaut de la Classe|#f fuzzy means that the translation is suspect and that the entries must be checked and verified (by removing the fuzzy mark) by an translator. -- Lgb
Re: QT compile problems.
On Mon, 9 Dec 2002 15:50:46 +0100 Andre Poenitz [EMAIL PROTECTED] wrote: On Mon, Dec 09, 2002 at 11:39:15AM -0300, John Coppens wrote: I'm not sure I'm capable of modifying the code and getting it to work. But maybe it wouldn't be bad to warn people of the state it's in, instead of giving the option in the configure script. Well, one usually starts of with giving an option in the configure script and work out the problems that emerge... Maybe - just a hint - add a comment at the end of the 'configure' run, in the table where the final config is shown (Front-end:Gnome), add a warning there... This is one of the few places most people do read, I think ;-) About the rest. I'll have a real good look at the problem first. I don't use Gnome or KDE either (I'm running IceWM at the moment). But I do generally like way GTK+ does things. Cheers, John
Re: QT compile problems.
Aide Florent <[EMAIL PROTECTED]> writes: | Hi, | | > translations. By making the french translation up to date you will get | > more/all the english strings into french. | | I looked into the fr.po file but everything is correctly translated... | Maybe the po file needs to be regenerated to reflect the "new" strings ? fuzzy: #: src/frontends/qt2/QDocumentDialog.C:276 #, fuzzy msgid "Papersize and Orientation" msgstr "Orientation" #: ../src/frontends/qt2/ui/PaperModuleBase.ui:84 #, fuzzy msgid "Paper size" msgstr "Taille :" #: ../src/frontends/xforms/forms/form_document.fd:170 #, fuzzy msgid "Use Class Defaults|#C" msgstr "Valeurs par Défaut de la Classe|#f" fuzzy means that the translation is suspect and that the entries must be checked and verified (by removing the fuzzy mark) by an translator. -- Lgb
Re: QT compile problems.
On Mon, 9 Dec 2002 15:50:46 +0100 Andre Poenitz <[EMAIL PROTECTED]> wrote: > On Mon, Dec 09, 2002 at 11:39:15AM -0300, John Coppens wrote: > > I'm not sure I'm capable of modifying the code and getting it to work. > > But maybe it wouldn't be bad to warn people of the state it's in, > > instead of giving the option in the configure script. > > Well, one usually starts of with giving an option in the configure script > and work out the problems that emerge... > Maybe - just a hint - add a comment at the end of the 'configure' run, in the table where the final config is shown (Front-end:Gnome), add a warning there... This is one of the few places most people do read, I think ;-) About the rest. I'll have a real good look at the problem first. I don't use Gnome or KDE either (I'm running IceWM at the moment). But I do generally like way GTK+ does things. Cheers, John
Re: QT compile problems.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Do spill ... here it is: http://hector.homeip.net/lyx-130cvs1.png you can see the document parameter dialog, obviously there are many portions which remain in English whereas some others are obviously (too mee) French... There are many menus where this problem arises. Can I help here ? Thanks. Florent AIDE -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE98/RfQe8gCED8yYERAq39AKCCwJCD4Uf2CB5WHDDaSNBjtgTZFACfY7l/ mdtUZKeKUbpmZMJTI5fr55A= =IwAV -END PGP SIGNATURE-
Re: QT compile problems.
Aide Florent [EMAIL PROTECTED] writes: | Do spill ... | | here it is: | | http://hector.homeip.net/lyx-130cvs1.png | | you can see the document parameter dialog, obviously there are many portions | which remain in English whereas some others are obviously (too mee) French... | | There are many menus where this problem arises. | | Can I help here ? Yes, you probably can. Most of these issues is because of missing translations. By making the french translation up to date you will get more/all the english strings into french. -- Lgb
Re: QT compile problems.
Hi, translations. By making the french translation up to date you will get more/all the english strings into french. I looked into the fr.po file but everything is correctly translated... Maybe the po file needs to be regenerated to reflect the new strings ? Florent.
Re: QT compile problems.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Do spill ... here it is: http://hector.homeip.net/lyx-130cvs1.png you can see the document parameter dialog, obviously there are many portions which remain in English whereas some others are obviously (too mee) French... There are many menus where this problem arises. Can I help here ? Thanks. Florent AIDE -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE98/RfQe8gCED8yYERAq39AKCCwJCD4Uf2CB5WHDDaSNBjtgTZFACfY7l/ mdtUZKeKUbpmZMJTI5fr55A= =IwAV -END PGP SIGNATURE-
Re: QT compile problems.
Aide Florent [EMAIL PROTECTED] writes: | Do spill ... | | here it is: | | http://hector.homeip.net/lyx-130cvs1.png | | you can see the document parameter dialog, obviously there are many portions | which remain in English whereas some others are obviously (too mee) French... | | There are many menus where this problem arises. | | Can I help here ? Yes, you probably can. Most of these issues is because of missing translations. By making the french translation up to date you will get more/all the english strings into french. -- Lgb
Re: QT compile problems.
Hi, translations. By making the french translation up to date you will get more/all the english strings into french. I looked into the fr.po file but everything is correctly translated... Maybe the po file needs to be regenerated to reflect the new strings ? Florent.
Re: QT compile problems.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Do spill ... here it is: http://hector.homeip.net/lyx-130cvs1.png you can see the document parameter dialog, obviously there are many portions which remain in English whereas some others are obviously (too mee) French... There are many menus where this problem arises. Can I help here ? Thanks. Florent AIDE -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE98/RfQe8gCED8yYERAq39AKCCwJCD4Uf2CB5WHDDaSNBjtgTZFACfY7l/ mdtUZKeKUbpmZMJTI5fr55A= =IwAV -END PGP SIGNATURE-
Re: QT compile problems.
Aide Florent <[EMAIL PROTECTED]> writes: | > Do spill ... | | here it is: | | http://hector.homeip.net/lyx-130cvs1.png | | you can see the document parameter dialog, obviously there are many portions | which remain in English whereas some others are obviously (too mee) French... | | There are many menus where this problem arises. | | Can I help here ? Yes, you probably can. Most of these issues is because of missing translations. By making the french translation up to date you will get more/all the english strings into french. -- Lgb
Re: QT compile problems.
Hi, > translations. By making the french translation up to date you will get > more/all the english strings into french. I looked into the fr.po file but everything is correctly translated... Maybe the po file needs to be regenerated to reflect the "new" strings ? Florent.
Re: QT compile problems.
On Sat, 7 Dec 2002 03:34:27 + John Levon [EMAIL PROTECTED] wrote: I do not understand how this can happen. Are you sure that you do a make distclean after fiddling with the configuration ? That was it. I only did a 'make clean'. I did mention that before somewhere, I believe. I appreciate your help, John. I've also learned a few things from the other comments. LyX is now working fine with Qt2. Later, I'll have a go compiling it with Qt3... And maybe gnome. I'm doing all this, because I find I have some glitches with the use of the xforms version. Thanks, John regards john -- Yeah, I woke up in the day accidentally once, the moon was on fire for some reason and I couldn't see very well and all the bandwidth disappeared, it was very scary :( - Orion
Re: QT compile problems.
On Sat, Dec 07, 2002 at 12:25:03PM -0300, John Coppens wrote: I appreciate your help, John. I've also learned a few things from the other comments. LyX is now working fine with Qt2. Later, I'll have a go compiling it with Qt3... And maybe gnome. I'm doing all this, because I find I have some glitches with the use of the xforms version. Gnome is barely started and doesn't compile or work. What glitches ? We may or may not know about them regards john -- There's only millions that lose their jobs and homes and sometimes accents There's only millions that die in their bloody wars, it's alright It's only their lives and the lives of their next of kin that they are losing It's only their lives and the lives of their next of kin that they are losing. - Stereolab
Re: QT compile problems.
On Sat, 7 Dec 2002 18:38:52 + John Levon [EMAIL PROTECTED] wrote: On Sat, Dec 07, 2002 at 12:25:03PM -0300, John Coppens wrote: I appreciate your help, John. I've also learned a few things from the other comments. LyX is now working fine with Qt2. Later, I'll have a go compiling it with Qt3... And maybe gnome. I'm doing all this, because I find I have some glitches with the use of the xforms version. Gnome is barely started and doesn't compile or work. What glitches ? We may or may not know about them Just annoyances. Like if you select a a wrong menu, and want to get to the menuitem to the right or left, it's very difficult to activate it. One has to close the previous menu first. Then, sometimes, a submenu that was selected stays open, even when another submenu is selected. Irregularly menu items don't repaint, and part of the GUI remains unrefreshed (sometimes transparent), until I switch desktops. This happens in the previous case - when submenus don't close correctly. As I said - it's mainly small nagging things. I thought changing the GUI would solve that. I'm quite happy with the inner workings of LyX though. Thanks John
Re: QT compile problems.
On Sat, 7 Dec 2002 03:34:27 + John Levon [EMAIL PROTECTED] wrote: I do not understand how this can happen. Are you sure that you do a make distclean after fiddling with the configuration ? That was it. I only did a 'make clean'. I did mention that before somewhere, I believe. I appreciate your help, John. I've also learned a few things from the other comments. LyX is now working fine with Qt2. Later, I'll have a go compiling it with Qt3... And maybe gnome. I'm doing all this, because I find I have some glitches with the use of the xforms version. Thanks, John regards john -- Yeah, I woke up in the day accidentally once, the moon was on fire for some reason and I couldn't see very well and all the bandwidth disappeared, it was very scary :( - Orion
Re: QT compile problems.
On Sat, Dec 07, 2002 at 12:25:03PM -0300, John Coppens wrote: I appreciate your help, John. I've also learned a few things from the other comments. LyX is now working fine with Qt2. Later, I'll have a go compiling it with Qt3... And maybe gnome. I'm doing all this, because I find I have some glitches with the use of the xforms version. Gnome is barely started and doesn't compile or work. What glitches ? We may or may not know about them regards john -- There's only millions that lose their jobs and homes and sometimes accents There's only millions that die in their bloody wars, it's alright It's only their lives and the lives of their next of kin that they are losing It's only their lives and the lives of their next of kin that they are losing. - Stereolab
Re: QT compile problems.
On Sat, 7 Dec 2002 18:38:52 + John Levon [EMAIL PROTECTED] wrote: On Sat, Dec 07, 2002 at 12:25:03PM -0300, John Coppens wrote: I appreciate your help, John. I've also learned a few things from the other comments. LyX is now working fine with Qt2. Later, I'll have a go compiling it with Qt3... And maybe gnome. I'm doing all this, because I find I have some glitches with the use of the xforms version. Gnome is barely started and doesn't compile or work. What glitches ? We may or may not know about them Just annoyances. Like if you select a a wrong menu, and want to get to the menuitem to the right or left, it's very difficult to activate it. One has to close the previous menu first. Then, sometimes, a submenu that was selected stays open, even when another submenu is selected. Irregularly menu items don't repaint, and part of the GUI remains unrefreshed (sometimes transparent), until I switch desktops. This happens in the previous case - when submenus don't close correctly. As I said - it's mainly small nagging things. I thought changing the GUI would solve that. I'm quite happy with the inner workings of LyX though. Thanks John
Re: QT compile problems.
On Sat, 7 Dec 2002 03:34:27 +
John Levon <[EMAIL PROTECTED]> wrote:
>
> I do not understand how this can happen. Are you sure that you do a
> "make distclean" after fiddling with the configuration ?
That was it. I only did a 'make clean'. I did mention that before somewhere,
I believe.
I appreciate your help, John. I've also learned a few things from the other
comments. LyX is now working fine with Qt2. Later, I'll have a go compiling
it with Qt3... And maybe gnome. I'm doing all this, because I find I have
some glitches with the use of the xforms version.
Thanks,
John
>
> regards
> john
>
> --
> "Yeah, I woke up in the day accidentally once, the moon was on fire for some
> reason and I couldn't see very well and all the bandwidth disappeared, it was
> very scary :("
> - Orion
Re: QT compile problems.
On Sat, Dec 07, 2002 at 12:25:03PM -0300, John Coppens wrote: > I appreciate your help, John. I've also learned a few things from the other > comments. LyX is now working fine with Qt2. Later, I'll have a go compiling > it with Qt3... And maybe gnome. I'm doing all this, because I find I have > some glitches with the use of the xforms version. Gnome is barely started and doesn't compile or work. What glitches ? We may or may not know about them regards john -- "There's only millions that lose their jobs and homes and sometimes accents There's only millions that die in their bloody wars, it's alright It's only their lives and the lives of their next of kin that they are losing It's only their lives and the lives of their next of kin that they are losing." - Stereolab
Re: QT compile problems.
On Sat, 7 Dec 2002 18:38:52 + John Levon <[EMAIL PROTECTED]> wrote: > On Sat, Dec 07, 2002 at 12:25:03PM -0300, John Coppens wrote: > > > I appreciate your help, John. I've also learned a few things from the other > > comments. LyX is now working fine with Qt2. Later, I'll have a go compiling > > it with Qt3... And maybe gnome. I'm doing all this, because I find I have > > some glitches with the use of the xforms version. > > Gnome is barely started and doesn't compile or work. > > What glitches ? We may or may not know about them > Just annoyances. Like if you select a a wrong menu, and want to get to the menuitem to the right or left, it's very difficult to activate it. One has to close the previous menu first. Then, sometimes, a submenu that was selected stays open, even when another submenu is selected. Irregularly menu items don't repaint, and part of the GUI remains unrefreshed (sometimes transparent), until I switch desktops. This happens in the previous case - when submenus don't close correctly. As I said - it's mainly small nagging things. I thought changing the GUI would solve that. I'm quite happy with the inner workings of LyX though. Thanks John
Re: QT compile problems.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello all, ...is the qt frontend even usable with qt3? I use Lyx 1.3.0cvs on a Slackware 9.0current with qt 3.1 and KDE 3.1rc4 ;) and it works ;) There are still a fiews bugs which forced me to keep my Lyx 1.2.1 installed : the new page after paragraph as no effect and the dialog to open the document preambule does not do anything. But hey this is fresh from cvs, not a release ;) On a side note I would like to say I really enjoy the Qt front End ;) It is really wonderfull to be able to work with the mouse wheel everywhere, and to see TrueType fonts on the screen If someone on the list wants some screen shots I can put then on my website, let me know. Cheers to all. Florent AIDE -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE98LQAQe8gCED8yYERAl2JAKC6R+gtVDKIqF2tGR1cHTOeaV5bKwCeMTMm juKpE8jXhcdjsdeKOnvM/dI= =zcLe -END PGP SIGNATURE-
Re: QT compile problems.
On Fri, Dec 06, 2002 at 03:28:16PM +0100, Aide Florent wrote: There are still a fiews bugs which forced me to keep my Lyx 1.2.1 installed : the new page after paragraph as no effect You know you are duty bound as a tester to report these bugs ... I haven't seen this report before and the dialog to open the document preambule does not do anything. this we know. You can edit the preamble via the document dialog regards john -- Yeah, I woke up in the day accidentally once, the moon was on fire for some reason and I couldn't see very well and all the bandwidth disappeared, it was very scary :( - Orion
Re: QT compile problems.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello again, You know you are duty bound as a tester to report these bugs ... I haven't seen this report before This I did not know but I clearly felt ;) I just compiled lyx yesterday ... and found out this bug at 23h30 localtime (France) so I posted today in the lyx-users list (yes I know inside another thread) if you feel I could contribute another way please tell it to me ;) I could post to the devel list or edit some bugzilla entry ? Well, there also seem to be some quirks with internationalization at the moment ... regards john Cheers, Florent PS: I loved Lyx before but I love it even more now that I have a good GUI to work with ;) THANKS A LOT to all the wonderfull devs who work on it. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE98M3wQe8gCED8yYERAoc3AJ9psw4J4jxlaVtiSaGqy0GKFKsw7QCgrLaA 5n3F/geOPSEo4oys/vDxUj0= =KcTa -END PGP SIGNATURE-
Re: QT compile problems.
On Fri, Dec 06, 2002 at 05:18:56PM +0100, Aide Florent wrote: and found out this bug at 23h30 localtime (France) so I posted today in the lyx-users list (yes I know inside another thread) heh OK that's fine :) I could post to the devel list or edit some bugzilla entry ? For things you are sure are bugs, the devel list of bugzilla is more likely to be noticed by me, yes Well, there also seem to be some quirks with internationalization at the moment ... Do spill ... regards john -- Yeah, I woke up in the day accidentally once, the moon was on fire for some reason and I couldn't see very well and all the bandwidth disappeared, it was very scary :( - Orion
Re: QT compile problems.
On Fri, Dec 06, 2002 at 02:15:11AM -0300, John Coppens wrote:
/usr/lib/qt-2.3.1/include/qt.h
/usr/lib/qt-3.0.4/include/qt.h
Don't ask me WHY. This is a Slackware Distro, and it's installed
that way.
where is the actual Qt library itself ? Directly in /usr/lib ? If so,
you need to set $QTDIR to /usr/lib/qt-2.3.1, so we find the 2.3.1
headers, assuming that the link is set to point to qt2
Ok. I forgot to mention there's a symlink (qt) in the same place that
points to one of both.
And which is it set to.
FRONTEND_LDFLAGS=\$(QT_LDFLAGS)
FRONTEND_INCLUDES=-I\${srcdir}/qt2 \$(QT_INCLUDES)
Ok - but even when LyX detects 3.0.4, the qt2 bits of above _are_ included.
Is that correct?
Yes, but this is just the name of the directory in the lyx source and
has absolutely nothing to do with qt 2 vs. qt 3
=Note: there is no libqt2... just libqt - should there be a link?
No, this is just probing for a suitably named library.
qt_cv_dir=/usr/lib/qt-2.3.1
qt_cv_includes=/usr/lib/qt-2.3.1/include
qt_cv_libname=-lqt
qt_cv_libraries=/usr/lib/qt-2.3.1/lib
qt_cv_path_moc=/usr/lib/qt-2.3.1/bin/moc
qt_cv_path_moc2=NONE
qt_cv_path_uic=/usr/lib/qt-2.3.1/bin/uic
This should work fine *assuming* your symlink in /usr/lib is pointing to
qt 2.
QAboutDialogBase.C: In method `QAboutDialogBase::QAboutDialogBase(QWidget * = 0,
const char * = 0, bool = FALSE, unsigned int = 0)':
QAboutDialogBase.C:36: implicit declaration of function `int trUtf8(...)'
QAboutDialogBase.C:36: no matching function for call to
`QAboutDialogBase::setCaption (int)'
/usr/lib/qt-2.3.1/include/qwidget.h:264: candidates are: void
QWidget::setCaption(const QString )
I do not understand how this can happen. Are you sure that you do a
make distclean after fiddling with the configuration ?
regards
john
--
Yeah, I woke up in the day accidentally once, the moon was on fire for some
reason and I couldn't see very well and all the bandwidth disappeared, it was
very scary :(
- Orion
Re: QT compile problems.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello all, ...is the qt frontend even usable with qt3? I use Lyx 1.3.0cvs on a Slackware 9.0current with qt 3.1 and KDE 3.1rc4 ;) and it works ;) There are still a fiews bugs which forced me to keep my Lyx 1.2.1 installed : the new page after paragraph as no effect and the dialog to open the document preambule does not do anything. But hey this is fresh from cvs, not a release ;) On a side note I would like to say I really enjoy the Qt front End ;) It is really wonderfull to be able to work with the mouse wheel everywhere, and to see TrueType fonts on the screen If someone on the list wants some screen shots I can put then on my website, let me know. Cheers to all. Florent AIDE -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE98LQAQe8gCED8yYERAl2JAKC6R+gtVDKIqF2tGR1cHTOeaV5bKwCeMTMm juKpE8jXhcdjsdeKOnvM/dI= =zcLe -END PGP SIGNATURE-
Re: QT compile problems.
On Fri, Dec 06, 2002 at 03:28:16PM +0100, Aide Florent wrote: There are still a fiews bugs which forced me to keep my Lyx 1.2.1 installed : the new page after paragraph as no effect You know you are duty bound as a tester to report these bugs ... I haven't seen this report before and the dialog to open the document preambule does not do anything. this we know. You can edit the preamble via the document dialog regards john -- Yeah, I woke up in the day accidentally once, the moon was on fire for some reason and I couldn't see very well and all the bandwidth disappeared, it was very scary :( - Orion
Re: QT compile problems.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello again, You know you are duty bound as a tester to report these bugs ... I haven't seen this report before This I did not know but I clearly felt ;) I just compiled lyx yesterday ... and found out this bug at 23h30 localtime (France) so I posted today in the lyx-users list (yes I know inside another thread) if you feel I could contribute another way please tell it to me ;) I could post to the devel list or edit some bugzilla entry ? Well, there also seem to be some quirks with internationalization at the moment ... regards john Cheers, Florent PS: I loved Lyx before but I love it even more now that I have a good GUI to work with ;) THANKS A LOT to all the wonderfull devs who work on it. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE98M3wQe8gCED8yYERAoc3AJ9psw4J4jxlaVtiSaGqy0GKFKsw7QCgrLaA 5n3F/geOPSEo4oys/vDxUj0= =KcTa -END PGP SIGNATURE-
Re: QT compile problems.
On Fri, Dec 06, 2002 at 05:18:56PM +0100, Aide Florent wrote: and found out this bug at 23h30 localtime (France) so I posted today in the lyx-users list (yes I know inside another thread) heh OK that's fine :) I could post to the devel list or edit some bugzilla entry ? For things you are sure are bugs, the devel list of bugzilla is more likely to be noticed by me, yes Well, there also seem to be some quirks with internationalization at the moment ... Do spill ... regards john -- Yeah, I woke up in the day accidentally once, the moon was on fire for some reason and I couldn't see very well and all the bandwidth disappeared, it was very scary :( - Orion
Re: QT compile problems.
On Fri, Dec 06, 2002 at 02:15:11AM -0300, John Coppens wrote:
/usr/lib/qt-2.3.1/include/qt.h
/usr/lib/qt-3.0.4/include/qt.h
Don't ask me WHY. This is a Slackware Distro, and it's installed
that way.
where is the actual Qt library itself ? Directly in /usr/lib ? If so,
you need to set $QTDIR to /usr/lib/qt-2.3.1, so we find the 2.3.1
headers, assuming that the link is set to point to qt2
Ok. I forgot to mention there's a symlink (qt) in the same place that
points to one of both.
And which is it set to.
FRONTEND_LDFLAGS=\$(QT_LDFLAGS)
FRONTEND_INCLUDES=-I\${srcdir}/qt2 \$(QT_INCLUDES)
Ok - but even when LyX detects 3.0.4, the qt2 bits of above _are_ included.
Is that correct?
Yes, but this is just the name of the directory in the lyx source and
has absolutely nothing to do with qt 2 vs. qt 3
=Note: there is no libqt2... just libqt - should there be a link?
No, this is just probing for a suitably named library.
qt_cv_dir=/usr/lib/qt-2.3.1
qt_cv_includes=/usr/lib/qt-2.3.1/include
qt_cv_libname=-lqt
qt_cv_libraries=/usr/lib/qt-2.3.1/lib
qt_cv_path_moc=/usr/lib/qt-2.3.1/bin/moc
qt_cv_path_moc2=NONE
qt_cv_path_uic=/usr/lib/qt-2.3.1/bin/uic
This should work fine *assuming* your symlink in /usr/lib is pointing to
qt 2.
QAboutDialogBase.C: In method `QAboutDialogBase::QAboutDialogBase(QWidget * = 0,
const char * = 0, bool = FALSE, unsigned int = 0)':
QAboutDialogBase.C:36: implicit declaration of function `int trUtf8(...)'
QAboutDialogBase.C:36: no matching function for call to
`QAboutDialogBase::setCaption (int)'
/usr/lib/qt-2.3.1/include/qwidget.h:264: candidates are: void
QWidget::setCaption(const QString )
I do not understand how this can happen. Are you sure that you do a
make distclean after fiddling with the configuration ?
regards
john
--
Yeah, I woke up in the day accidentally once, the moon was on fire for some
reason and I couldn't see very well and all the bandwidth disappeared, it was
very scary :(
- Orion
Re: QT compile problems.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello all, > ...is the qt frontend even usable with qt3? I use Lyx 1.3.0cvs on a Slackware 9.0current with qt 3.1 and KDE 3.1rc4 ;) and it works ;) There are still a fiews bugs which forced me to keep my Lyx 1.2.1 installed : the new page after paragraph as no effect and the dialog to open the document preambule does not do anything. But hey this is fresh from cvs, not a release ;) On a side note I would like to say I really enjoy the Qt front End ;) It is really wonderfull to be able to work with the mouse wheel everywhere, and to see TrueType fonts on the screen If someone on the list wants some screen shots I can put then on my website, let me know. Cheers to all. Florent AIDE -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE98LQAQe8gCED8yYERAl2JAKC6R+gtVDKIqF2tGR1cHTOeaV5bKwCeMTMm juKpE8jXhcdjsdeKOnvM/dI= =zcLe -END PGP SIGNATURE-
Re: QT compile problems.
On Fri, Dec 06, 2002 at 03:28:16PM +0100, Aide Florent wrote:
> There are still a fiews bugs which forced me to keep my Lyx 1.2.1 installed :
> the new page after paragraph as no effect
You know you are duty bound as a tester to report these bugs ... I
haven't seen this report before
and the dialog to open the document preambule does not do anything.
this we know. You can edit the preamble via the document dialog
regards
john
--
"Yeah, I woke up in the day accidentally once, the moon was on fire for some
reason and I couldn't see very well and all the bandwidth disappeared, it was
very scary :("
- Orion
Re: QT compile problems.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello again, > You know you are duty bound as a tester to report these bugs ... I > haven't seen this report before This I did not know but I clearly felt ;) I just compiled lyx yesterday ... and found out this bug at 23h30 localtime (France) so I posted today in the lyx-users list (yes I know inside another thread) if you feel I could contribute another way please tell it to me ;) I could post to the devel list or edit some bugzilla entry ? Well, there also seem to be some quirks with internationalization at the moment ... > regards > john Cheers, Florent PS: I loved Lyx before but I love it even more now that I have a good GUI to work with ;) THANKS A LOT to all the wonderfull devs who work on it. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE98M3wQe8gCED8yYERAoc3AJ9psw4J4jxlaVtiSaGqy0GKFKsw7QCgrLaA 5n3F/geOPSEo4oys/vDxUj0= =KcTa -END PGP SIGNATURE-
Re: QT compile problems.
On Fri, Dec 06, 2002 at 05:18:56PM +0100, Aide Florent wrote:
> and found out this bug at 23h30 localtime (France)
> so I posted today in the lyx-users list (yes I know inside another thread)
heh OK that's fine :)
> I could post to the devel list or edit some bugzilla entry ?
For things you are sure are bugs, the devel list of bugzilla is more
likely to be noticed by me, yes
> Well, there also seem to be some quirks with internationalization at the
> moment ...
Do spill ...
regards
john
--
"Yeah, I woke up in the day accidentally once, the moon was on fire for some
reason and I couldn't see very well and all the bandwidth disappeared, it was
very scary :("
- Orion
Re: QT compile problems.
On Fri, Dec 06, 2002 at 02:15:11AM -0300, John Coppens wrote:
> /usr/lib/qt-2.3.1/include/qt.h
> /usr/lib/qt-3.0.4/include/qt.h
>
> Don't ask me WHY. This is a Slackware Distro, and it's installed
> that way.
where is the actual Qt library itself ? Directly in /usr/lib ? If so,
you need to set $QTDIR to /usr/lib/qt-2.3.1, so we find the 2.3.1
headers, assuming that the link is set to point to qt2
> Ok. I forgot to mention there's a symlink (qt) in the same place that
> points to one of both.
And which is it set to.
> > > FRONTEND_LDFLAGS="\$(QT_LDFLAGS)"
> > > FRONTEND_INCLUDES="-I\${srcdir}/qt2 \$(QT_INCLUDES)"
> >
> Ok - but even when LyX detects 3.0.4, the qt2 bits of above _are_ included.
> Is that correct?
Yes, but this is just the name of the directory in the lyx source and
has absolutely nothing to do with qt 2 vs. qt 3
> =Note: there is no libqt2... just libqt - should there be a link?
No, this is just probing for a suitably named library.
> qt_cv_dir=/usr/lib/qt-2.3.1
> qt_cv_includes=/usr/lib/qt-2.3.1/include
> qt_cv_libname=-lqt
> qt_cv_libraries=/usr/lib/qt-2.3.1/lib
> qt_cv_path_moc=/usr/lib/qt-2.3.1/bin/moc
> qt_cv_path_moc2=NONE
> qt_cv_path_uic=/usr/lib/qt-2.3.1/bin/uic
This should work fine *assuming* your symlink in /usr/lib is pointing to
qt 2.
> QAboutDialogBase.C: In method `QAboutDialogBase::QAboutDialogBase(QWidget * = 0,
>const char * = 0, bool = FALSE, unsigned int = 0)':
> QAboutDialogBase.C:36: implicit declaration of function `int trUtf8(...)'
> QAboutDialogBase.C:36: no matching function for call to
>`QAboutDialogBase::setCaption (int)'
> /usr/lib/qt-2.3.1/include/qwidget.h:264: candidates are: void
>QWidget::setCaption(const QString &)
I do not understand how this can happen. Are you sure that you do a
"make distclean" after fiddling with the configuration ?
regards
john
--
"Yeah, I woke up in the day accidentally once, the moon was on fire for some
reason and I couldn't see very well and all the bandwidth disappeared, it was
very scary :("
- Orion
Re: QT compile problems.
On Thu, Dec 05, 2002 at 01:02:45AM -0300, John Coppens wrote: I'm trying to compile LyX CVS with the --with-frontend=qt option. Configure goes quite well, but compilation fails at the end with a long list of messages about missing references. Now, configure reports Qt3, which really is installed. And I've noticed that LyX actually explicitly links to qt2... I'm guessing this is the cause if the problem. (I have both Qt's installed). You have a) passed the wrong $QTDIR or set the wrong $QTDIR b) used a compiler version that doesn't match the one Qt was compiled with regards john -- Trolls like content too. - Bob Abooey, /.
Re: QT compile problems.
Thanks John... QTDIR is pointing to the 3.0.4 version, which is logical, because its the latest. But LyX internally has quite a few hardwired links to the qt2 directories. I now defined QTDIR to point to 2.3.1, reconfigured (deleted config.log first), and in the final link, LyX still tries to access the 3.0.4 directory... I did a make clean, and then I get these errors: g++ -DHAVE_CONFIG_H -I. -I. -I../../../../src -I../../../../src -I../../../../src/frontends -I../../../../src/frontends/qt2 -I./qt2 -I/usr/lib/qt-2.3.1/include -I../../../../boost -I../../../../src/frontends/controllers -isystem /usr/X11R6/include -DQT_CLEAN_NAMESPACE -DQT_GENUINE_STR -DQT_NO_TRANSLATION -g -O -Wno-non-template-friend -ftemplate-depth-30 -W -Wall -c QAboutDialogBase.C -Wp,-MD,.deps/QAboutDialogBase.TPlo QAboutDialogBase.C: In method `QAboutDialogBase::QAboutDialogBase(QWidget * = 0, const char * = 0, bool = FALSE, unsigned int = 0)': QAboutDialogBase.C:36: implicit declaration of function `int trUtf8(...)' QAboutDialogBase.C:36: no matching function for call to `QAboutDialogBase::setCaption (int)' /usr/lib/qt-2.3.1/include/qwidget.h:264: candidates are: void QWidget::setCaption(const QString ) QAboutDialogBase.C:49: no matching function for call to `QLabel::setText (int)' /usr/lib/qt-2.3.1/include/qlabel.h:100: candidates are: void QLabel::setText(const QString ) And so on Does it have to be an explicit version of Qt? John On Thu, 5 Dec 2002 12:46:07 + John Levon [EMAIL PROTECTED] wrote: On Thu, Dec 05, 2002 at 01:02:45AM -0300, John Coppens wrote: I'm trying to compile LyX CVS with the --with-frontend=qt option. Configure goes quite well, but compilation fails at the end with a long list of messages about missing references. Now, configure reports Qt3, which really is installed. And I've noticed that LyX actually explicitly links to qt2... I'm guessing this is the cause if the problem. (I have both Qt's installed). You have a) passed the wrong $QTDIR or set the wrong $QTDIR b) used a compiler version that doesn't match the one Qt was compiled with regards john -- Trolls like content too. - Bob Abooey, /.
Re: QT compile problems.
On Thu, Dec 05, 2002 at 03:09:20PM -0300, John Coppens wrote: QTDIR is pointing to the 3.0.4 version, which is logical, because its the latest. But LyX internally has quite a few hardwired links to the qt2 directories. There are no hardwired links at all. Where are the Qt 3.0.4 headers on your system ? You must make sure that it finds the same library version and headers version. Check config.log for the qt bits g++ -DHAVE_CONFIG_H -I. -I. -I../../../../src -I../../../../src -I../../../../src/frontends -I../../../../src/frontends/qt2 -I./qt2 -I/usr/lib/qt-2.3.1/include -I../../../../boost -I../../../../src/frontends/controllers -isystem /usr/X11R6/include -DQT_CLEAN_NAMESPACE -DQT_GENUINE_STR -DQT_NO_TRANSLATION -g -O -Wno-non-template-friend -ftemplate-depth-30 -W -Wall -c QAboutDialogBase.C -Wp,-MD,.deps/QAboutDialogBase.TPlo QAboutDialogBase.C: In method `QAboutDialogBase::QAboutDialogBase(QWidget * = 0, const char * = 0, bool = FALSE, unsigned int = 0)': QAboutDialogBase.C:36: implicit declaration of function `int trUtf8(...)' QAboutDialogBase.C:36: no matching function for call to `QAboutDialogBase::setCaption (int)' /usr/lib/qt-2.3.1/include/qwidget.h:264: candidates are: void QWidget::setCaption(const QString ) QAboutDialogBase.C:49: no matching function for call to `QLabel::setText (int)' /usr/lib/qt-2.3.1/include/qlabel.h:100: candidates are: void QLabel::setText(const QString ) And so on Something has got badly confused. Btw, deleting config.log makes no difference, maybe you are thinking of config.cache Does it have to be an explicit version of Qt? No. regards john
Re: QT compile problems.
On Thu, 5 Dec 2002 18:33:30 +
John Levon [EMAIL PROTECTED] wrote:
On Thu, Dec 05, 2002 at 03:09:20PM -0300, John Coppens wrote:
QTDIR is pointing to the 3.0.4 version, which is logical, because its
the latest. But LyX internally has quite a few hardwired links to the
qt2 directories.
There are no hardwired links at all.
Where are the Qt 3.0.4 headers on your system ?
You must make sure that it finds the same library version and headers
version. Check config.log for the qt bits
Both 3.0.4 and 2.3.1 are under /usr/lib.
Why, if no qt isn't hardcoded, is this in configure.ac:
qt)
QT_DO_IT_ALL
FRONTEND=qt2
FRONTEND_GUILIB=qt2/*.lo qt2/ui/*.lo qt2/moc/*.lo qt2/ui/moc/*.lo
FRONTEND_LDFLAGS=\$(QT_LDFLAGS)
FRONTEND_INCLUDES=-I\${srcdir}/qt2 \$(QT_INCLUDES)
FRONTEND_LIBS=\$(QT_LIB)
FRONTEND_INFO=Qt version: ${QT_VERSION}\n
This always gets activated - even if $QTDIR is pointing to 3.0.4, and
if LyX correctly detects this version of Qt? (of course not the .ac,
but the actual configure and makefiles do use these options)
Sorry if I'm wrong - I'm surely no software guru...
John
Re: QT compile problems.
On Thu, 5 Dec 2002, John Coppens wrote:
On Thu, 5 Dec 2002 18:33:30 +
John Levon [EMAIL PROTECTED] wrote:
On Thu, Dec 05, 2002 at 03:09:20PM -0300, John Coppens wrote:
QTDIR is pointing to the 3.0.4 version, which is logical, because its
the latest. But LyX internally has quite a few hardwired links to the
qt2 directories.
There are no hardwired links at all.
Where are the Qt 3.0.4 headers on your system ?
You must make sure that it finds the same library version and headers
version. Check config.log for the qt bits
Both 3.0.4 and 2.3.1 are under /usr/lib.
Why, if no qt isn't hardcoded, is this in configure.ac:
qt)
QT_DO_IT_ALL
FRONTEND=qt2
FRONTEND_GUILIB=qt2/*.lo qt2/ui/*.lo qt2/moc/*.lo qt2/ui/moc/*.lo
FRONTEND_LDFLAGS=\$(QT_LDFLAGS)
FRONTEND_INCLUDES=-I\${srcdir}/qt2 \$(QT_INCLUDES)
FRONTEND_LIBS=\$(QT_LIB)
FRONTEND_INFO=Qt version: ${QT_VERSION}\n
These qt2 bits are references into the LyX source, not your system...
This always gets activated - even if $QTDIR is pointing to 3.0.4, and
if LyX correctly detects this version of Qt? (of course not the .ac,
but the actual configure and makefiles do use these options)
...is the qt frontend even usable with qt3?
- Bruce
Re: QT compile problems.
On Thu, Dec 05, 2002 at 05:37:59PM -0700, Bruce Sass wrote: ...is the qt frontend even usable with qt3? Yes (in fact it works a little bit better) john -- Yeah, I woke up in the day accidentally once, the moon was on fire for some reason and I couldn't see very well and all the bandwidth disappeared, it was very scary :( - Orion
Re: QT compile problems.
Hi John.
I didn't notice the first time around this reply was turned down
by the lyx mail server (happened before):
On Thu, 5 Dec 2002 22:17:38 +
John Levon [EMAIL PROTECTED] wrote:
On Thu, Dec 05, 2002 at 07:11:57PM -0300, John Coppens wrote:
Where are the Qt 3.0.4 headers on your system ?
Please answer this, or I can't help you.
Both 3.0.4 and 2.3.1 are under /usr/lib.
Sorry.. But that's really _it_:
/usr/lib/qt-2.3.1/include/qt.h
/usr/lib/qt-3.0.4/include/qt.h
Don't ask me WHY. This is a Slackware Distro, and it's installed
that way.
How do you expect us to guess which one you want then ?
Ok. I forgot to mention there's a symlink (qt) in the same place that
points to one of both.
FRONTEND_LDFLAGS=\$(QT_LDFLAGS)
FRONTEND_INCLUDES=-I\${srcdir}/qt2 \$(QT_INCLUDES)
This is src/frontends/qt2/ in the LyX source.
All the variables are set at configure time.
Ok - but even when LyX detects 3.0.4, the qt2 bits of above _are_ included.
Is that correct?
You still haven't posted the relevant bits from config.log either ...
regards
john
--
Yeah, I woke up in the day accidentally once, the moon was on fire for some
reason and I couldn't see very well and all the bandwidth disappeared, it was
very scary :(
- Orion
-Parts from the config.log (This is with $QTDIR=2.3.1/symlink to 2.3.1)
configure:13884: result: /usr/lib/qt-2.3.1/bin/uic
configure:13899: checking for Qt library name
configure:13944: g++ -o conftest -g -O -Wno-non-template-friend -ftemplate-depth
-30 -W -Wall -I/usr/lib/qt-2.3.1/include -L/usr/lib/qt-2.3.1/lib -lqt3 -isystem
/usr/X11R6/include conftest.cc -lSM -lICE -lc -lm -L/usr/X11R6/lib -lX11
5
/usr/i386-slackware-linux/bin/ld: cannot find -lqt3
collect2: ld returned 1 exit status
---
configure:13944: g++ -o conftest -g -O -Wno-non-template-friend -ftemplate-depth
-30 -W -Wall -I/usr/lib/qt-2.3.1/include -L/usr/lib/qt-2.3.1/lib -lqt2 -isystem
/usr/X11R6/include conftest.cc -lSM -lICE -lc -lm -L/usr/X11R6/lib -lX11
5
/usr/i386-slackware-linux/bin/ld: cannot find -lqt2
collect2: ld returned 1 exit status
configure:13947: $? = 1
=Note: there is no libqt2... just libqt - should there be a link?
config.status:760: creating src/frontends/xforms/forms/Makefile
config.status:760: creating src/frontends/qt2/Makefile
config.status:760: creating src/frontends/qt2/moc/Makefile
config.status:760: creating src/frontends/qt2/ui/Makefile
config.status:760: creating src/frontends/qt2/ui/moc/Makefile
config.status:760: creating src/frontends/gnome/Makefile
config.status:864: creating src/config.h
lyx_cv_modern_streams=no
lyx_cv_qtversion=$'2.3.1 '
lyx_cv_std_count=yes
qt_cv_dir=/usr/lib/qt-2.3.1
qt_cv_includes=/usr/lib/qt-2.3.1/include
qt_cv_libname=-lqt
qt_cv_libraries=/usr/lib/qt-2.3.1/lib
qt_cv_path_moc=/usr/lib/qt-2.3.1/bin/moc
qt_cv_path_moc2=NONE
qt_cv_path_uic=/usr/lib/qt-2.3.1/bin/uic
FRONTEND='qt2'
FRONTEND_GUILIB='qt2/*.lo qt2/ui/*.lo qt2/moc/*.lo qt2/ui/moc/*.lo'
FRONTEND_INCLUDES='-I${srcdir}/qt2 $(QT_INCLUDES)'
FRONTEND_LDFLAGS='$(QT_LDFLAGS)'
FRONTEND_LIBS='$(QT_LIB)'
QT_INCLUDES='-I/usr/lib/qt-2.3.1/include'
QT_LDFLAGS='-L/usr/lib/qt-2.3.1/lib'
QT_LIB='-lqt'
QT_VERSION='2.3.1 '
RANLIB='ranlib'
SET_MAKE=''
SHELL='/bin/sh'
STRIP='strip'
UIC='/usr/lib/qt-2.3.1/bin/uic'
This is the (first) error when doing make:
g++ -DHAVE_CONFIG_H -I. -I. -I../../../../src -I../../../../src
-I../../../../src/frontends -I../../../../src/frontends/qt2 -I./qt2
-I/usr/lib/qt-2.3.1/include -I../../../../boost
-I../../../../src/frontends/controllers -isystem /usr/X11R6/include
-DQT_CLEAN_NAMESPACE -DQT_GENUINE_STR -DQT_NO_TRANSLATION -g -O
-Wno-non-template-friend -ftemplate-depth-30 -W -Wall -c QAboutDialogBase.C
-Wp,-MD,.deps/QAboutDialogBase.TPlo
QAboutDialogBase.C: In method `QAboutDialogBase::QAboutDialogBase(QWidget * = 0, const
char * = 0, bool = FALSE, unsigned int = 0)':
QAboutDialogBase.C:36: implicit declaration of function `int trUtf8(...)'
QAboutDialogBase.C:36: no matching function for call to `QAboutDialogBase::setCaption
(int)'
/usr/lib/qt-2.3.1/include/qwidget.h:264: candidates are: void
QWidget::setCaption(const QString )
QAboutDialogBase.C:49: no matching function for call to `QLabel::setText (int)'
/usr/lib/qt-2.3.1/include/qlabel.h:100: candidates are: void QLabel::setText(const
QString )
QAboutDialogBase.C:52: no matching function for call to `QTabWidget::insertTab
(QWidget *, int)'
Re: QT compile problems.
On Thu, Dec 05, 2002 at 01:02:45AM -0300, John Coppens wrote: I'm trying to compile LyX CVS with the --with-frontend=qt option. Configure goes quite well, but compilation fails at the end with a long list of messages about missing references. Now, configure reports Qt3, which really is installed. And I've noticed that LyX actually explicitly links to qt2... I'm guessing this is the cause if the problem. (I have both Qt's installed). You have a) passed the wrong $QTDIR or set the wrong $QTDIR b) used a compiler version that doesn't match the one Qt was compiled with regards john -- Trolls like content too. - Bob Abooey, /.
Re: QT compile problems.
Thanks John... QTDIR is pointing to the 3.0.4 version, which is logical, because its the latest. But LyX internally has quite a few hardwired links to the qt2 directories. I now defined QTDIR to point to 2.3.1, reconfigured (deleted config.log first), and in the final link, LyX still tries to access the 3.0.4 directory... I did a make clean, and then I get these errors: g++ -DHAVE_CONFIG_H -I. -I. -I../../../../src -I../../../../src -I../../../../src/frontends -I../../../../src/frontends/qt2 -I./qt2 -I/usr/lib/qt-2.3.1/include -I../../../../boost -I../../../../src/frontends/controllers -isystem /usr/X11R6/include -DQT_CLEAN_NAMESPACE -DQT_GENUINE_STR -DQT_NO_TRANSLATION -g -O -Wno-non-template-friend -ftemplate-depth-30 -W -Wall -c QAboutDialogBase.C -Wp,-MD,.deps/QAboutDialogBase.TPlo QAboutDialogBase.C: In method `QAboutDialogBase::QAboutDialogBase(QWidget * = 0, const char * = 0, bool = FALSE, unsigned int = 0)': QAboutDialogBase.C:36: implicit declaration of function `int trUtf8(...)' QAboutDialogBase.C:36: no matching function for call to `QAboutDialogBase::setCaption (int)' /usr/lib/qt-2.3.1/include/qwidget.h:264: candidates are: void QWidget::setCaption(const QString ) QAboutDialogBase.C:49: no matching function for call to `QLabel::setText (int)' /usr/lib/qt-2.3.1/include/qlabel.h:100: candidates are: void QLabel::setText(const QString ) And so on Does it have to be an explicit version of Qt? John On Thu, 5 Dec 2002 12:46:07 + John Levon [EMAIL PROTECTED] wrote: On Thu, Dec 05, 2002 at 01:02:45AM -0300, John Coppens wrote: I'm trying to compile LyX CVS with the --with-frontend=qt option. Configure goes quite well, but compilation fails at the end with a long list of messages about missing references. Now, configure reports Qt3, which really is installed. And I've noticed that LyX actually explicitly links to qt2... I'm guessing this is the cause if the problem. (I have both Qt's installed). You have a) passed the wrong $QTDIR or set the wrong $QTDIR b) used a compiler version that doesn't match the one Qt was compiled with regards john -- Trolls like content too. - Bob Abooey, /.
Re: QT compile problems.
On Thu, Dec 05, 2002 at 03:09:20PM -0300, John Coppens wrote: QTDIR is pointing to the 3.0.4 version, which is logical, because its the latest. But LyX internally has quite a few hardwired links to the qt2 directories. There are no hardwired links at all. Where are the Qt 3.0.4 headers on your system ? You must make sure that it finds the same library version and headers version. Check config.log for the qt bits g++ -DHAVE_CONFIG_H -I. -I. -I../../../../src -I../../../../src -I../../../../src/frontends -I../../../../src/frontends/qt2 -I./qt2 -I/usr/lib/qt-2.3.1/include -I../../../../boost -I../../../../src/frontends/controllers -isystem /usr/X11R6/include -DQT_CLEAN_NAMESPACE -DQT_GENUINE_STR -DQT_NO_TRANSLATION -g -O -Wno-non-template-friend -ftemplate-depth-30 -W -Wall -c QAboutDialogBase.C -Wp,-MD,.deps/QAboutDialogBase.TPlo QAboutDialogBase.C: In method `QAboutDialogBase::QAboutDialogBase(QWidget * = 0, const char * = 0, bool = FALSE, unsigned int = 0)': QAboutDialogBase.C:36: implicit declaration of function `int trUtf8(...)' QAboutDialogBase.C:36: no matching function for call to `QAboutDialogBase::setCaption (int)' /usr/lib/qt-2.3.1/include/qwidget.h:264: candidates are: void QWidget::setCaption(const QString ) QAboutDialogBase.C:49: no matching function for call to `QLabel::setText (int)' /usr/lib/qt-2.3.1/include/qlabel.h:100: candidates are: void QLabel::setText(const QString ) And so on Something has got badly confused. Btw, deleting config.log makes no difference, maybe you are thinking of config.cache Does it have to be an explicit version of Qt? No. regards john
Re: QT compile problems.
On Thu, 5 Dec 2002 18:33:30 +
John Levon [EMAIL PROTECTED] wrote:
On Thu, Dec 05, 2002 at 03:09:20PM -0300, John Coppens wrote:
QTDIR is pointing to the 3.0.4 version, which is logical, because its
the latest. But LyX internally has quite a few hardwired links to the
qt2 directories.
There are no hardwired links at all.
Where are the Qt 3.0.4 headers on your system ?
You must make sure that it finds the same library version and headers
version. Check config.log for the qt bits
Both 3.0.4 and 2.3.1 are under /usr/lib.
Why, if no qt isn't hardcoded, is this in configure.ac:
qt)
QT_DO_IT_ALL
FRONTEND=qt2
FRONTEND_GUILIB=qt2/*.lo qt2/ui/*.lo qt2/moc/*.lo qt2/ui/moc/*.lo
FRONTEND_LDFLAGS=\$(QT_LDFLAGS)
FRONTEND_INCLUDES=-I\${srcdir}/qt2 \$(QT_INCLUDES)
FRONTEND_LIBS=\$(QT_LIB)
FRONTEND_INFO=Qt version: ${QT_VERSION}\n
This always gets activated - even if $QTDIR is pointing to 3.0.4, and
if LyX correctly detects this version of Qt? (of course not the .ac,
but the actual configure and makefiles do use these options)
Sorry if I'm wrong - I'm surely no software guru...
John
Re: QT compile problems.
On Thu, 5 Dec 2002, John Coppens wrote:
On Thu, 5 Dec 2002 18:33:30 +
John Levon [EMAIL PROTECTED] wrote:
On Thu, Dec 05, 2002 at 03:09:20PM -0300, John Coppens wrote:
QTDIR is pointing to the 3.0.4 version, which is logical, because its
the latest. But LyX internally has quite a few hardwired links to the
qt2 directories.
There are no hardwired links at all.
Where are the Qt 3.0.4 headers on your system ?
You must make sure that it finds the same library version and headers
version. Check config.log for the qt bits
Both 3.0.4 and 2.3.1 are under /usr/lib.
Why, if no qt isn't hardcoded, is this in configure.ac:
qt)
QT_DO_IT_ALL
FRONTEND=qt2
FRONTEND_GUILIB=qt2/*.lo qt2/ui/*.lo qt2/moc/*.lo qt2/ui/moc/*.lo
FRONTEND_LDFLAGS=\$(QT_LDFLAGS)
FRONTEND_INCLUDES=-I\${srcdir}/qt2 \$(QT_INCLUDES)
FRONTEND_LIBS=\$(QT_LIB)
FRONTEND_INFO=Qt version: ${QT_VERSION}\n
These qt2 bits are references into the LyX source, not your system...
This always gets activated - even if $QTDIR is pointing to 3.0.4, and
if LyX correctly detects this version of Qt? (of course not the .ac,
but the actual configure and makefiles do use these options)
...is the qt frontend even usable with qt3?
- Bruce
Re: QT compile problems.
On Thu, Dec 05, 2002 at 05:37:59PM -0700, Bruce Sass wrote: ...is the qt frontend even usable with qt3? Yes (in fact it works a little bit better) john -- Yeah, I woke up in the day accidentally once, the moon was on fire for some reason and I couldn't see very well and all the bandwidth disappeared, it was very scary :( - Orion
Re: QT compile problems.
Hi John.
I didn't notice the first time around this reply was turned down
by the lyx mail server (happened before):
On Thu, 5 Dec 2002 22:17:38 +
John Levon [EMAIL PROTECTED] wrote:
On Thu, Dec 05, 2002 at 07:11:57PM -0300, John Coppens wrote:
Where are the Qt 3.0.4 headers on your system ?
Please answer this, or I can't help you.
Both 3.0.4 and 2.3.1 are under /usr/lib.
Sorry.. But that's really _it_:
/usr/lib/qt-2.3.1/include/qt.h
/usr/lib/qt-3.0.4/include/qt.h
Don't ask me WHY. This is a Slackware Distro, and it's installed
that way.
How do you expect us to guess which one you want then ?
Ok. I forgot to mention there's a symlink (qt) in the same place that
points to one of both.
FRONTEND_LDFLAGS=\$(QT_LDFLAGS)
FRONTEND_INCLUDES=-I\${srcdir}/qt2 \$(QT_INCLUDES)
This is src/frontends/qt2/ in the LyX source.
All the variables are set at configure time.
Ok - but even when LyX detects 3.0.4, the qt2 bits of above _are_ included.
Is that correct?
You still haven't posted the relevant bits from config.log either ...
regards
john
--
Yeah, I woke up in the day accidentally once, the moon was on fire for some
reason and I couldn't see very well and all the bandwidth disappeared, it was
very scary :(
- Orion
-Parts from the config.log (This is with $QTDIR=2.3.1/symlink to 2.3.1)
configure:13884: result: /usr/lib/qt-2.3.1/bin/uic
configure:13899: checking for Qt library name
configure:13944: g++ -o conftest -g -O -Wno-non-template-friend -ftemplate-depth
-30 -W -Wall -I/usr/lib/qt-2.3.1/include -L/usr/lib/qt-2.3.1/lib -lqt3 -isystem
/usr/X11R6/include conftest.cc -lSM -lICE -lc -lm -L/usr/X11R6/lib -lX11
5
/usr/i386-slackware-linux/bin/ld: cannot find -lqt3
collect2: ld returned 1 exit status
---
configure:13944: g++ -o conftest -g -O -Wno-non-template-friend -ftemplate-depth
-30 -W -Wall -I/usr/lib/qt-2.3.1/include -L/usr/lib/qt-2.3.1/lib -lqt2 -isystem
/usr/X11R6/include conftest.cc -lSM -lICE -lc -lm -L/usr/X11R6/lib -lX11
5
/usr/i386-slackware-linux/bin/ld: cannot find -lqt2
collect2: ld returned 1 exit status
configure:13947: $? = 1
=Note: there is no libqt2... just libqt - should there be a link?
config.status:760: creating src/frontends/xforms/forms/Makefile
config.status:760: creating src/frontends/qt2/Makefile
config.status:760: creating src/frontends/qt2/moc/Makefile
config.status:760: creating src/frontends/qt2/ui/Makefile
config.status:760: creating src/frontends/qt2/ui/moc/Makefile
config.status:760: creating src/frontends/gnome/Makefile
config.status:864: creating src/config.h
lyx_cv_modern_streams=no
lyx_cv_qtversion=$'2.3.1 '
lyx_cv_std_count=yes
qt_cv_dir=/usr/lib/qt-2.3.1
qt_cv_includes=/usr/lib/qt-2.3.1/include
qt_cv_libname=-lqt
qt_cv_libraries=/usr/lib/qt-2.3.1/lib
qt_cv_path_moc=/usr/lib/qt-2.3.1/bin/moc
qt_cv_path_moc2=NONE
qt_cv_path_uic=/usr/lib/qt-2.3.1/bin/uic
FRONTEND='qt2'
FRONTEND_GUILIB='qt2/*.lo qt2/ui/*.lo qt2/moc/*.lo qt2/ui/moc/*.lo'
FRONTEND_INCLUDES='-I${srcdir}/qt2 $(QT_INCLUDES)'
FRONTEND_LDFLAGS='$(QT_LDFLAGS)'
FRONTEND_LIBS='$(QT_LIB)'
QT_INCLUDES='-I/usr/lib/qt-2.3.1/include'
QT_LDFLAGS='-L/usr/lib/qt-2.3.1/lib'
QT_LIB='-lqt'
QT_VERSION='2.3.1 '
RANLIB='ranlib'
SET_MAKE=''
SHELL='/bin/sh'
STRIP='strip'
UIC='/usr/lib/qt-2.3.1/bin/uic'
This is the (first) error when doing make:
g++ -DHAVE_CONFIG_H -I. -I. -I../../../../src -I../../../../src
-I../../../../src/frontends -I../../../../src/frontends/qt2 -I./qt2
-I/usr/lib/qt-2.3.1/include -I../../../../boost
-I../../../../src/frontends/controllers -isystem /usr/X11R6/include
-DQT_CLEAN_NAMESPACE -DQT_GENUINE_STR -DQT_NO_TRANSLATION -g -O
-Wno-non-template-friend -ftemplate-depth-30 -W -Wall -c QAboutDialogBase.C
-Wp,-MD,.deps/QAboutDialogBase.TPlo
QAboutDialogBase.C: In method `QAboutDialogBase::QAboutDialogBase(QWidget * = 0, const
char * = 0, bool = FALSE, unsigned int = 0)':
QAboutDialogBase.C:36: implicit declaration of function `int trUtf8(...)'
QAboutDialogBase.C:36: no matching function for call to `QAboutDialogBase::setCaption
(int)'
/usr/lib/qt-2.3.1/include/qwidget.h:264: candidates are: void
QWidget::setCaption(const QString )
QAboutDialogBase.C:49: no matching function for call to `QLabel::setText (int)'
/usr/lib/qt-2.3.1/include/qlabel.h:100: candidates are: void QLabel::setText(const
QString )
QAboutDialogBase.C:52: no matching function for call to `QTabWidget::insertTab
(QWidget *, int)'
Re: QT compile problems.
On Thu, Dec 05, 2002 at 01:02:45AM -0300, John Coppens wrote: > I'm trying to compile LyX CVS with the --with-frontend=qt option. > Configure goes quite well, but compilation fails at the end with a > long list of messages about missing references. > > Now, configure reports Qt3, which really is installed. And I've > noticed that LyX actually explicitly links to qt2... I'm guessing > this is the cause if the problem. (I have both Qt's installed). You have a) passed the wrong $QTDIR or set the wrong $QTDIR b) used a compiler version that doesn't match the one Qt was compiled with regards john -- "Trolls like content too." - Bob Abooey, /.
Re: QT compile problems.
Thanks John... QTDIR is pointing to the 3.0.4 version, which is logical, because its the latest. But LyX internally has quite a few hardwired links to the qt2 directories. I now defined QTDIR to point to 2.3.1, reconfigured (deleted config.log first), and in the final link, LyX still tries to access the 3.0.4 directory... I did a make clean, and then I get these errors: g++ -DHAVE_CONFIG_H -I. -I. -I../../../../src -I../../../../src -I../../../../src/frontends -I../../../../src/frontends/qt2 -I./qt2 -I/usr/lib/qt-2.3.1/include -I../../../../boost -I../../../../src/frontends/controllers -isystem /usr/X11R6/include -DQT_CLEAN_NAMESPACE -DQT_GENUINE_STR -DQT_NO_TRANSLATION -g -O -Wno-non-template-friend -ftemplate-depth-30 -W -Wall -c QAboutDialogBase.C -Wp,-MD,.deps/QAboutDialogBase.TPlo QAboutDialogBase.C: In method `QAboutDialogBase::QAboutDialogBase(QWidget * = 0, const char * = 0, bool = FALSE, unsigned int = 0)': QAboutDialogBase.C:36: implicit declaration of function `int trUtf8(...)' QAboutDialogBase.C:36: no matching function for call to `QAboutDialogBase::setCaption (int)' /usr/lib/qt-2.3.1/include/qwidget.h:264: candidates are: void QWidget::setCaption(const QString &) QAboutDialogBase.C:49: no matching function for call to `QLabel::setText (int)' /usr/lib/qt-2.3.1/include/qlabel.h:100: candidates are: void QLabel::setText(const QString &) And so on Does it have to be an explicit version of Qt? John On Thu, 5 Dec 2002 12:46:07 + John Levon <[EMAIL PROTECTED]> wrote: > On Thu, Dec 05, 2002 at 01:02:45AM -0300, John Coppens wrote: > > > I'm trying to compile LyX CVS with the --with-frontend=qt option. > > Configure goes quite well, but compilation fails at the end with a > > long list of messages about missing references. > > > > Now, configure reports Qt3, which really is installed. And I've > > noticed that LyX actually explicitly links to qt2... I'm guessing > > this is the cause if the problem. (I have both Qt's installed). > > You have a) passed the wrong $QTDIR or set the wrong $QTDIR > b) used a compiler version that doesn't match the one Qt was compiled > with > > regards > john > -- > "Trolls like content too." > - Bob Abooey, /.
Re: QT compile problems.
On Thu, Dec 05, 2002 at 03:09:20PM -0300, John Coppens wrote: > QTDIR is pointing to the 3.0.4 version, which is logical, because its > the latest. But LyX internally has quite a few hardwired links to the > qt2 directories. There are no hardwired links at all. Where are the Qt 3.0.4 headers on your system ? You must make sure that it finds the same library version and headers version. Check config.log for the qt bits > g++ -DHAVE_CONFIG_H -I. -I. -I../../../../src -I../../../../src >-I../../../../src/frontends -I../../../../src/frontends/qt2 -I./qt2 >-I/usr/lib/qt-2.3.1/include -I../../../../boost >-I../../../../src/frontends/controllers -isystem /usr/X11R6/include >-DQT_CLEAN_NAMESPACE -DQT_GENUINE_STR -DQT_NO_TRANSLATION -g -O >-Wno-non-template-friend -ftemplate-depth-30 -W -Wall -c QAboutDialogBase.C >-Wp,-MD,.deps/QAboutDialogBase.TPlo > QAboutDialogBase.C: In method `QAboutDialogBase::QAboutDialogBase(QWidget * = 0, >const char * = 0, bool = FALSE, unsigned int = 0)': > QAboutDialogBase.C:36: implicit declaration of function `int trUtf8(...)' > QAboutDialogBase.C:36: no matching function for call to >`QAboutDialogBase::setCaption (int)' > /usr/lib/qt-2.3.1/include/qwidget.h:264: candidates are: void >QWidget::setCaption(const QString &) > QAboutDialogBase.C:49: no matching function for call to `QLabel::setText (int)' > /usr/lib/qt-2.3.1/include/qlabel.h:100: candidates are: void QLabel::setText(const >QString &) > And so on Something has got badly confused. Btw, deleting config.log makes no difference, maybe you are thinking of config.cache > Does it have to be an explicit version of Qt? No. regards john
Re: QT compile problems.
On Thu, 5 Dec 2002 18:33:30 +
John Levon <[EMAIL PROTECTED]> wrote:
> On Thu, Dec 05, 2002 at 03:09:20PM -0300, John Coppens wrote:
>
> > QTDIR is pointing to the 3.0.4 version, which is logical, because its
> > the latest. But LyX internally has quite a few hardwired links to the
> > qt2 directories.
>
> There are no hardwired links at all.
>
> Where are the Qt 3.0.4 headers on your system ?
>
> You must make sure that it finds the same library version and headers
> version. Check config.log for the qt bits
>
Both 3.0.4 and 2.3.1 are under /usr/lib.
Why, if no qt isn't hardcoded, is this in configure.ac:
qt)
QT_DO_IT_ALL
FRONTEND="qt2"
FRONTEND_GUILIB="qt2/*.lo qt2/ui/*.lo qt2/moc/*.lo qt2/ui/moc/*.lo"
FRONTEND_LDFLAGS="\$(QT_LDFLAGS)"
FRONTEND_INCLUDES="-I\${srcdir}/qt2 \$(QT_INCLUDES)"
FRONTEND_LIBS="\$(QT_LIB)"
FRONTEND_INFO="Qt version: ${QT_VERSION}\n"
This always gets activated - even if $QTDIR is pointing to 3.0.4, and
if LyX correctly detects this version of Qt? (of course not the .ac,
but the actual configure and makefiles do use these options)
Sorry if I'm wrong - I'm surely no software guru...
John
Re: QT compile problems.
On Thu, 5 Dec 2002, John Coppens wrote:
> On Thu, 5 Dec 2002 18:33:30 +
> John Levon <[EMAIL PROTECTED]> wrote:
> > On Thu, Dec 05, 2002 at 03:09:20PM -0300, John Coppens wrote:
> >
> > > QTDIR is pointing to the 3.0.4 version, which is logical, because its
> > > the latest. But LyX internally has quite a few hardwired links to the
> > > qt2 directories.
> >
> > There are no hardwired links at all.
> >
> > Where are the Qt 3.0.4 headers on your system ?
> >
> > You must make sure that it finds the same library version and headers
> > version. Check config.log for the qt bits
> >
>
> Both 3.0.4 and 2.3.1 are under /usr/lib.
> Why, if no qt isn't hardcoded, is this in configure.ac:
>
> qt)
> QT_DO_IT_ALL
> FRONTEND="qt2"
> FRONTEND_GUILIB="qt2/*.lo qt2/ui/*.lo qt2/moc/*.lo qt2/ui/moc/*.lo"
> FRONTEND_LDFLAGS="\$(QT_LDFLAGS)"
> FRONTEND_INCLUDES="-I\${srcdir}/qt2 \$(QT_INCLUDES)"
> FRONTEND_LIBS="\$(QT_LIB)"
> FRONTEND_INFO="Qt version: ${QT_VERSION}\n"
These qt2 bits are references into the LyX source, not your system...
> This always gets activated - even if $QTDIR is pointing to 3.0.4, and
> if LyX correctly detects this version of Qt? (of course not the .ac,
> but the actual configure and makefiles do use these options)
...is the qt frontend even usable with qt3?
- Bruce
Re: QT compile problems.
On Thu, Dec 05, 2002 at 05:37:59PM -0700, Bruce Sass wrote:
> ...is the qt frontend even usable with qt3?
Yes (in fact it works a little bit better)
john
--
"Yeah, I woke up in the day accidentally once, the moon was on fire for some
reason and I couldn't see very well and all the bandwidth disappeared, it was
very scary :("
- Orion
Re: QT compile problems.
Hi John.
I didn't notice the first time around this reply was turned down
by the lyx mail server (happened before):
On Thu, 5 Dec 2002 22:17:38 +
John Levon <[EMAIL PROTECTED]> wrote:
> On Thu, Dec 05, 2002 at 07:11:57PM -0300, John Coppens wrote:
>
> > > Where are the Qt 3.0.4 headers on your system ?
>
> Please answer this, or I can't help you.
>
> > Both 3.0.4 and 2.3.1 are under /usr/lib.
Sorry.. But that's really _it_:
/usr/lib/qt-2.3.1/include/qt.h
/usr/lib/qt-3.0.4/include/qt.h
Don't ask me WHY. This is a Slackware Distro, and it's installed
that way.
>
> How do you expect us to guess which one you want then ?
Ok. I forgot to mention there's a symlink (qt) in the same place that
points to one of both.
>
> > FRONTEND_LDFLAGS="\$(QT_LDFLAGS)"
> > FRONTEND_INCLUDES="-I\${srcdir}/qt2 \$(QT_INCLUDES)"
>
> This is src/frontends/qt2/ in the LyX source.
>
> All the variables are set at configure time.
Ok - but even when LyX detects 3.0.4, the qt2 bits of above _are_ included.
Is that correct?
>
> You still haven't posted the relevant bits from config.log either ...
>
> regards
> john
> --
> "Yeah, I woke up in the day accidentally once, the moon was on fire for some
> reason and I couldn't see very well and all the bandwidth disappeared, it was
> very scary :("
> - Orion
-Parts from the config.log (This is with $QTDIR=2.3.1/symlink to 2.3.1)
configure:13884: result: /usr/lib/qt-2.3.1/bin/uic
configure:13899: checking for Qt library name
configure:13944: g++ -o conftest -g -O -Wno-non-template-friend -ftemplate-depth
-30 -W -Wall -I/usr/lib/qt-2.3.1/include -L/usr/lib/qt-2.3.1/lib -lqt3 -isystem
/usr/X11R6/include conftest.cc -lSM -lICE -lc -lm -L/usr/X11R6/lib -lX11 >
&5
/usr/i386-slackware-linux/bin/ld: cannot find -lqt3
collect2: ld returned 1 exit status
---
configure:13944: g++ -o conftest -g -O -Wno-non-template-friend -ftemplate-depth
-30 -W -Wall -I/usr/lib/qt-2.3.1/include -L/usr/lib/qt-2.3.1/lib -lqt2 -isystem
/usr/X11R6/include conftest.cc -lSM -lICE -lc -lm -L/usr/X11R6/lib -lX11 >
&5
/usr/i386-slackware-linux/bin/ld: cannot find -lqt2
collect2: ld returned 1 exit status
configure:13947: $? = 1
=Note: there is no libqt2... just libqt - should there be a link?
config.status:760: creating src/frontends/xforms/forms/Makefile
config.status:760: creating src/frontends/qt2/Makefile
config.status:760: creating src/frontends/qt2/moc/Makefile
config.status:760: creating src/frontends/qt2/ui/Makefile
config.status:760: creating src/frontends/qt2/ui/moc/Makefile
config.status:760: creating src/frontends/gnome/Makefile
config.status:864: creating src/config.h
lyx_cv_modern_streams=no
lyx_cv_qtversion=$'2.3.1 '
lyx_cv_std_count=yes
qt_cv_dir=/usr/lib/qt-2.3.1
qt_cv_includes=/usr/lib/qt-2.3.1/include
qt_cv_libname=-lqt
qt_cv_libraries=/usr/lib/qt-2.3.1/lib
qt_cv_path_moc=/usr/lib/qt-2.3.1/bin/moc
qt_cv_path_moc2=NONE
qt_cv_path_uic=/usr/lib/qt-2.3.1/bin/uic
FRONTEND='qt2'
FRONTEND_GUILIB='qt2/*.lo qt2/ui/*.lo qt2/moc/*.lo qt2/ui/moc/*.lo'
FRONTEND_INCLUDES='-I${srcdir}/qt2 $(QT_INCLUDES)'
FRONTEND_LDFLAGS='$(QT_LDFLAGS)'
FRONTEND_LIBS='$(QT_LIB)'
QT_INCLUDES='-I/usr/lib/qt-2.3.1/include'
QT_LDFLAGS='-L/usr/lib/qt-2.3.1/lib'
QT_LIB='-lqt'
QT_VERSION='2.3.1 '
RANLIB='ranlib'
SET_MAKE=''
SHELL='/bin/sh'
STRIP='strip'
UIC='/usr/lib/qt-2.3.1/bin/uic'
This is the (first) error when doing make:
g++ -DHAVE_CONFIG_H -I. -I. -I../../../../src -I../../../../src
-I../../../../src/frontends -I../../../../src/frontends/qt2 -I./qt2
-I/usr/lib/qt-2.3.1/include -I../../../../boost
-I../../../../src/frontends/controllers -isystem /usr/X11R6/include
-DQT_CLEAN_NAMESPACE -DQT_GENUINE_STR -DQT_NO_TRANSLATION -g -O
-Wno-non-template-friend -ftemplate-depth-30 -W -Wall -c QAboutDialogBase.C
-Wp,-MD,.deps/QAboutDialogBase.TPlo
QAboutDialogBase.C: In method `QAboutDialogBase::QAboutDialogBase(QWidget * = 0, const
char * = 0, bool = FALSE, unsigned int = 0)':
QAboutDialogBase.C:36: implicit declaration of function `int trUtf8(...)'
QAboutDialogBase.C:36: no matching function for call to `QAboutDialogBase::setCaption
(int)'
/usr/lib/qt-2.3.1/include/qwidget.h:264: candidates are: void
QWidget::setCaption(const QString &)
QAboutDialogBase.C:49: no matching function for call to `QLabel::setText (int)'
/usr/lib/qt-2.3.1/include/qlabel.h:100: candidates are: void QLabel::setText(const
QString &)
QAboutDialogBase.C:52: no matching function for call to `QTabWidget::insertTab
(QWidget *&, int)'
