Re: Wiki site approval password
On 30/05/2016 4:58 p.m., Andrew Parsloe wrote: I've updated the spreadtab.module that was enquired about on the users' list recently. I have a link on the wiki to a Dropbox folder. I need a password to approve the site. Andrew Received. Thank you. Andrew --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Re: [ANNOUNCE] LyX 2.2.0 Released
On Tue, May 31, 2016 at 05:55:22PM -0700, list_em...@icloud.com wrote: > On May 27, 2016, at 5:31 PM, Scott Kostyshak wrote: > > > On Fri, May 27, 2016 at 05:10:15PM -0700, list_em...@icloud.com wrote: > >> On May 27, 2016, at 4:55 PM, Scott Kostyshak wrote: > >> > >>> You can download LyX 2.2.0 from https://www.lyx.org/Download/. > >> > >> OS X links on this page apparently still point to 2.1.4. > > > > Can you try again Jerry? > > > > Scott > > Looks OK now but I didn't let the download complete since I already had done > the download before. OK thanks for checking. Scott signature.asc Description: PGP signature
Re: [ANNOUNCE] LyX 2.2.0 Released
On May 27, 2016, at 5:31 PM, Scott Kostyshak wrote: > On Fri, May 27, 2016 at 05:10:15PM -0700, list_em...@icloud.com wrote: >> On May 27, 2016, at 4:55 PM, Scott Kostyshak wrote: >> >>> You can download LyX 2.2.0 from https://www.lyx.org/Download/. >> >> OS X links on this page apparently still point to 2.1.4. > > Can you try again Jerry? > > Scott Looks OK now but I didn't let the download complete since I already had done the download before. Jerry
Re: Tarballs for LyX 2.2.0 are on FTP
On Tue, May 31, 2016 at 10:26:57PM +0200, Georg Baum wrote: > Guillaume Munch wrote: > > > Le 26/05/2016 07:45, Jean-Marc Lasgouttes a écrit : > > > >> Time to think about the release date of 2.3.0 now ;) > >> > > > > Yes, let's have this discussion :) > > > > I find the interval between feature releases too high. Having an > > interval longer than one year (more than two for 2.2) means that some > > features are left untested for more than a year, as we saw for some bug > > fixes for 2.2. > > I believe we all agree that we need to release more often, but there are > quite different opinions how to achieve that goal. > > > Changes should be tested more regularly, not all at once every two > > years. So one could have a fixed release interval of one year. Meeting > > the deadline would be more important than being full of features. > > > > The schedule could be decided in advance, and be on the website for > > clarity. > > We need to decide: Either have a fixed schedule, and an unknown feature set > of the next release, or a fixed feature set, and an unknown schedule. We do > not have enough man power for defining both a fixed feature set and a fixed > release schedule. > > > One could branch at feature and string freeze, between alpha and beta. > > This avoids having a master branch closed for so long. > > > > All the above suggestions are compatible with the numbering system > > described at http://www.lyx.org/VersioningSystem. > > > > In addition I would suggest the following: (Officially) allow new > > features that do not require a file format change into minor releases. > > > > The main reason is again that this allows testing more regularly. For > > instance, in my case, I can use a development version in my work, but > > only if the file format is the same. > > Unfortunately it also means we force all users to test these new features. > > --- > > IMO, the key point to more frequent releases is automation. There are many > things that are currently done manually which can be automated: > > - Automate windows installer generation. This would probably mean to switch > to mingw, since we can do both a mingw build and run nsis from a linux > machine. > > - Have a build server that does automatic builds on a regular basis for all > three platforms (Linux, OS X, windows) and makes binary packages and build > logs available. > > - Run tests automatically, using the binaries from the build server, make > test results available. > > - (not related to automation) Disentangle unrelated stuff from the release. > For example, the current way of updating the documentation is inefficient. > In agile software development you write the documentation of a new feature > almost at the same time as you implement the fetaure (this is one of the > good aspects of agile software development). If we do that as well we can > get rid of a noticeable delay at release time. Also, there is no reason why > the third-party parts of the windows installer need to be updated when a > release is done. This can be desynchronized as well to avoid delays. > > - (not related to automation) Set bug targets more realistically. This > avoids massive retargeting (with related discussions), and gives a better > picture what needs to be done for the release. I think these are all good ideas and would make the release process smoother, whether we move towards a more continuous release process or not. Scott signature.asc Description: PGP signature
po-files header
ATM all of our po-files contain a wrong entry like "Project-Id-Version: LyX 2.2.0dev\n" or "Project-Id-Version: LyX 1.6.0\n" and so on. Should we unify this string? Even if we create correct .pot file, the entry does not make it into the po-file. At least, I could not find a way to do it via msgmerge or msgfmt. So we are stick with making the change manually. Kornel signature.asc Description: This is a digitally signed message part.
Re: Horizontal crolling impossible in table in float in LyX 2.2.0
On 05/30/2016 05:42 AM, Jean-Marc Lasgouttes wrote: > Le 30/05/2016 11:20, Andrew Parsloe a écrit : >> LyX 2.2.0, windows 7 >> >> For a table outside a float the arrow-key horizontal scrolling works >> fine. If the table is in a float, there is no scrolling at all. I've >> attached an example file. I suspect this may be a known problem but I >> couldn't see anything obvious on trac. > > Does it fit the description in the following commit? > http://git.lyx.org/?p=lyx.git;a=commit;h=c8e1c092369a6708499d4503f620d028968d2167 > > > If it does, then this will be fixed in 2.2.2 (or 2.2.1 if nothing ugly > happens soon wrt 2.2.0). > > Since it is a regression and the patch is simple, this could actually > be candidate for branch right now, Richard. Sure, looks safe enough. rh
Re: Tarballs for LyX 2.2.0 are on FTP
Guillaume Munch wrote: > Le 26/05/2016 07:45, Jean-Marc Lasgouttes a écrit : > >> Time to think about the release date of 2.3.0 now ;) >> > > Yes, let's have this discussion :) > > I find the interval between feature releases too high. Having an > interval longer than one year (more than two for 2.2) means that some > features are left untested for more than a year, as we saw for some bug > fixes for 2.2. I believe we all agree that we need to release more often, but there are quite different opinions how to achieve that goal. > Changes should be tested more regularly, not all at once every two > years. So one could have a fixed release interval of one year. Meeting > the deadline would be more important than being full of features. > > The schedule could be decided in advance, and be on the website for > clarity. We need to decide: Either have a fixed schedule, and an unknown feature set of the next release, or a fixed feature set, and an unknown schedule. We do not have enough man power for defining both a fixed feature set and a fixed release schedule. > One could branch at feature and string freeze, between alpha and beta. > This avoids having a master branch closed for so long. > > All the above suggestions are compatible with the numbering system > described at http://www.lyx.org/VersioningSystem. > > In addition I would suggest the following: (Officially) allow new > features that do not require a file format change into minor releases. > > The main reason is again that this allows testing more regularly. For > instance, in my case, I can use a development version in my work, but > only if the file format is the same. Unfortunately it also means we force all users to test these new features. --- IMO, the key point to more frequent releases is automation. There are many things that are currently done manually which can be automated: - Automate windows installer generation. This would probably mean to switch to mingw, since we can do both a mingw build and run nsis from a linux machine. - Have a build server that does automatic builds on a regular basis for all three platforms (Linux, OS X, windows) and makes binary packages and build logs available. - Run tests automatically, using the binaries from the build server, make test results available. - (not related to automation) Disentangle unrelated stuff from the release. For example, the current way of updating the documentation is inefficient. In agile software development you write the documentation of a new feature almost at the same time as you implement the fetaure (this is one of the good aspects of agile software development). If we do that as well we can get rid of a noticeable delay at release time. Also, there is no reason why the third-party parts of the windows installer need to be updated when a release is done. This can be desynchronized as well to avoid delays. - (not related to automation) Set bug targets more realistically. This avoids massive retargeting (with related discussions), and gives a better picture what needs to be done for the release. Georg
Re: build requirements for Qt5 build
Jean-Marc Lasgouttes wrote: > Le 31/05/2016 à 13:53, Kornel Benko a écrit : >> use >> # export QT_SELECT=qt5 >> to select qt5 binaries. > > Indeed, it is much better. I'll change configure to do just that. Note that QT_SELECT needs to be defined not only when configure runs (that would be easy), but also during make invocation. I do not know enough about make to judge whether that is possible, but if that does not work one could as well test for "moc -qt=qt5", that should work as well. What I do personally is to export QT_SELECT=qt5 in my bashrc. Then I can select both qt versions: configure --enable-qt5 finds qt5 tools using the generic names /usr/bin/moc etc. configure finds qt4 tools using the version specific names /usr/bin/moc-qt4 etc. This might not be the way how QT_SELECT is supposed to work, but it works fine. Georg
Re: build requirements for Qt5 build
Le 31/05/2016 20:46, Georg Baum a écrit : How do we get configure to guess such peculiar path? pkgconfig. I do not see any other way, and if a linux distro does not supply pkgconfig files in some qt dev package then I'd consider that a distro packaging bug. On debian jessie the paths are the same, and the qt headers and libs are found using pkgconfig (more about moc in another message). pkg-config works. But I'd like to make the old style check work too. Of course, it would be even better to use qmake output for configuring. I began that several times, and eventually gave up. JMarc
Re: [ANNOUNCE] LyX 2.2.0 Released
Congratulations guys!!! It feels really good to know that LyX is still in development after so many years :-) I look forward to trying the new version... Abdel On 28/05/2016 01:55, Scott Kostyshak wrote: Public release of LyX version 2.2.0 We are proud to announce the release of LyX 2.2.0. With this release, LyX celebrates 20 years of existence. The 2.2 series has a rich set of new features compared to the current stable series. LyX 2.2.0 is the culmination of two years of hard work. An overview of the new features can be found here: http://wiki.lyx.org/LyX/NewInLyX22 You can download LyX 2.2.0 from https://www.lyx.org/Download/. For Windows users, if you installed a pre-release of LyX 2.2.0, you should uninstall that version before installing this newer release. We hope you will enjoy the result! The file lib/RELEASE-NOTES lists some known issues and problems compared to the current stable releases (LyX 2.1.x). We strongly recommend that packagers of LyX on various platforms and distributions read this file. As with any major release, this one comes with a lot of new features but also some bugs. If you think you have found a bug in LyX 2.2.0, either email the LyX developers' mailing list (lyx-devel at lists.lyx.org), or open a bug report at http://www.lyx.org/trac/wiki/BugTrackerHome. If you have trouble using LyX or have a question, consult the documentation that comes with LyX (under Help) and the LyX wiki, which you will find at http://wiki.lyx.org/. You can also send email to the LyX users' list (lyx-users at lists.lyx.org). The LyX team. http://www.lyx.org
Re: build requirements for Qt5 build
Jean-Marc Lasgouttes wrote: > Le 31/05/2016 à 11:38, Liviu Andronic a écrit : >> http://packages.ubuntu.com/search?searchon=contents&keywords=qglobal.h&mode=exactfilename&suite=xenial&arch=any >> >> /usr/include/i386-linux-gnu/qt5/QtCore/qglobal.h >> /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h > > How do we get configure to guess such peculiar path? pkgconfig. I do not see any other way, and if a linux distro does not supply pkgconfig files in some qt dev package then I'd consider that a distro packaging bug. On debian jessie the paths are the same, and the qt headers and libs are found using pkgconfig (more about moc in another message). Georg
Re: [LyX/master] Show names of debug modes in the debug panel
Le 31/05/2016 à 17:06, Guillaume Munch a écrit : I am tempted to do the same for the loaded modules list in the document preferences. Sometimes when I am looking for a precise module, I have to guess from the translation of the description, and it is not always obvious. Is there any objection or comment? You could maybe also experiment with a tooltip, to avoid having too long names for modules. JMarc
Re: [LyX/master] Show names of debug modes in the debug panel
Le 31/05/2016 00:15, Guillaume Munch a écrit : commit 2b6d0ae3deae80558a73346d60739fa408cbe2c3 Author: Guillaume Munch Date: Sun May 29 23:33:12 2016 +0100 Show names of debug modes in the debug panel Sometimes it's hard to know which is which from a translation of the description alone. diff --git a/src/frontends/qt4/GuiProgressView.cpp b/src/frontends/qt4/GuiProgressView.cpp index af455f2..454148f 100644 --- a/src/frontends/qt4/GuiProgressView.cpp +++ b/src/frontends/qt4/GuiProgressView.cpp @@ -88,7 +88,9 @@ GuiProgressView::GuiProgressView(GuiView & parent, Qt::DockWidgetArea area, DebugVector dmap; for (int i = 1 ; i < level_count; i++) { Debug::Type const level = Debug::value(i); - QString const desc = qt_(Debug::description(level)); + QString const desc = + toqstr(from_ascii(Debug::name(level) + " - ")) + + qt_(Debug::description(level)); dmap.push_back(DebugMap(level, desc)); } sort(dmap.begin(), dmap.end(), DebugSorter); Dear list, I am tempted to do the same for the loaded modules list in the document preferences. Sometimes when I am looking for a precise module, I have to guess from the translation of the description, and it is not always obvious. Is there any objection or comment? Guillaume
Re: build requirements for Qt5 build
On Tue, May 31, 2016 at 1:54 PM, Jean-Marc Lasgouttes wrote: > Le 31/05/2016 à 13:24, Liviu Andronic a écrit : >> >> On Tue, May 31, 2016 at 1:04 PM, Jean-Marc Lasgouttes >> wrote: >>> >>> Le 31/05/2016 à 12:06, Liviu Andronic a écrit : 'moc' it seems: http://packages.ubuntu.com/xenial/amd64/qtbase5-dev-tools/filelist >>> >>> >>> >>> And what is in /usr/bin? >>> >> Not the same version of Qt (and on my own machine), I have >> qtbase5-dev-tools installed. In /usr/bin I see this: > > > It looks like installing qt5-default helps. > This worked, thanks. Looks like the required Qt5 packages on Ubuntu are: qtbase5-dev, libqt5svg5-dev, qt5-default Regards, Liviu > I am not sure whether it is > still possible to compile for qt4 after that, though... > > JMarc > -- Do you think you know what math is? http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02 Or what it means to be intelligent? http://www.ideasroadshow.com/issues/john-duncan-2013-08-30 Think again: http://www.ideasroadshow.com/library
Re: build requirements for Qt5 build
Le 31/05/2016 à 13:53, Kornel Benko a écrit : use # export QT_SELECT=qt5 to select qt5 binaries. Indeed, it is much better. I'll change configure to do just that. JMarc
Re: build requirements for Qt5 build
Le 31/05/2016 à 13:24, Liviu Andronic a écrit : On Tue, May 31, 2016 at 1:04 PM, Jean-Marc Lasgouttes wrote: Le 31/05/2016 à 12:06, Liviu Andronic a écrit : 'moc' it seems: http://packages.ubuntu.com/xenial/amd64/qtbase5-dev-tools/filelist And what is in /usr/bin? Not the same version of Qt (and on my own machine), I have qtbase5-dev-tools installed. In /usr/bin I see this: It looks like installing qt5-default helps. I am not sure whether it is still possible to compile for qt4 after that, though... JMarc
Re: build requirements for Qt5 build
Am Dienstag, 31. Mai 2016 um 13:24:48, schrieb Liviu Andronic > On Tue, May 31, 2016 at 1:04 PM, Jean-Marc Lasgouttes > wrote: > > Le 31/05/2016 à 12:06, Liviu Andronic a écrit : > >> > >> 'moc' it seems: > >> http://packages.ubuntu.com/xenial/amd64/qtbase5-dev-tools/filelist > > > > > > And what is in /usr/bin? > > > Not the same version of Qt (and on my own machine), I have > qtbase5-dev-tools installed. In /usr/bin I see this: > > geek@liv-inspiron:~$ ls /usr/bin/moc -l > lrwxrwxrwx 1 root root 9 Feb 19 2014 /usr/bin/moc -> qtchooser use # export QT_SELECT=qt5 to select qt5 binaries. Kornel signature.asc Description: This is a digitally signed message part.
Re: build requirements for Qt5 build
On Tue, May 31, 2016 at 1:04 PM, Jean-Marc Lasgouttes wrote: > Le 31/05/2016 à 12:06, Liviu Andronic a écrit : >> >> 'moc' it seems: >> http://packages.ubuntu.com/xenial/amd64/qtbase5-dev-tools/filelist > > > And what is in /usr/bin? > Not the same version of Qt (and on my own machine), I have qtbase5-dev-tools installed. In /usr/bin I see this: geek@liv-inspiron:~$ ls /usr/bin/moc -l lrwxrwxrwx 1 root root 9 Feb 19 2014 /usr/bin/moc -> qtchooser geek@liv-inspiron:~$ /usr/bin/moc --help Usage: /usr/lib/x86_64-linux-gnu/qt5/bin/moc [options] [header-file] [@option-file] Qt Meta Object Compiler version 67 (Qt 5.2.1) [...] geek@liv-inspiron:~$ ls /usr/bin/qtchooser -l -rwxr-xr-x 1 root root 31328 Feb 19 2014 /usr/bin/qtchooser geek@liv-inspiron:~$ /usr/bin/qtchooser -l 4 5 default qt4-i386-linux-gnu qt4-x86_64-linux-gnu qt4 qt5-x86_64-linux-gnu qt5 > JMarc > > >> /usr/lib/x86_64-linux-gnu/qt5/bin/moc >> /usr/lib/x86_64-linux-gnu/qt5/bin/qdbuscpp2xml >> /usr/lib/x86_64-linux-gnu/qt5/bin/qdbusxml2cpp >> /usr/lib/x86_64-linux-gnu/qt5/bin/qdoc >> /usr/lib/x86_64-linux-gnu/qt5/bin/qlalr >> /usr/lib/x86_64-linux-gnu/qt5/bin/rcc >> /usr/lib/x86_64-linux-gnu/qt5/bin/syncqt.pl >> /usr/lib/x86_64-linux-gnu/qt5/bin/uic >> /usr/share/doc/qtbase5-dev-tools/LGPL_EXCEPTION.txt >> /usr/share/doc/qtbase5-dev-tools/changelog.Debian.gz >> /usr/share/doc/qtbase5-dev-tools/copyright >> /usr/share/man/man1/moc-qt5.1.gz > > -- Do you think you know what math is? http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02 Or what it means to be intelligent? http://www.ideasroadshow.com/issues/john-duncan-2013-08-30 Think again: http://www.ideasroadshow.com/library
Re: build requirements for Qt5 build
Le 31/05/2016 à 12:06, Liviu Andronic a écrit : 'moc' it seems: http://packages.ubuntu.com/xenial/amd64/qtbase5-dev-tools/filelist And what is in /usr/bin? JMarc /usr/lib/x86_64-linux-gnu/qt5/bin/moc /usr/lib/x86_64-linux-gnu/qt5/bin/qdbuscpp2xml /usr/lib/x86_64-linux-gnu/qt5/bin/qdbusxml2cpp /usr/lib/x86_64-linux-gnu/qt5/bin/qdoc /usr/lib/x86_64-linux-gnu/qt5/bin/qlalr /usr/lib/x86_64-linux-gnu/qt5/bin/rcc /usr/lib/x86_64-linux-gnu/qt5/bin/syncqt.pl /usr/lib/x86_64-linux-gnu/qt5/bin/uic /usr/share/doc/qtbase5-dev-tools/LGPL_EXCEPTION.txt /usr/share/doc/qtbase5-dev-tools/changelog.Debian.gz /usr/share/doc/qtbase5-dev-tools/copyright /usr/share/man/man1/moc-qt5.1.gz
Re: build requirements for Qt5 build
On Tue, May 31, 2016 at 12:01 PM, Jean-Marc Lasgouttes wrote: > Le 31/05/2016 à 11:57, Liviu Andronic a écrit : >>> >>> You do not need any qt4 stuff. It may be that moc is named moc5 or >>> something >>> for qt5. Or that moc is a link to something else. >>> >> Just checked and Qt5 moc comes with qtbase5-dev-tools, which is >> automatically pulled by qtbase5-dev. >> >> For some reason the correct moc compiler is still not detected, though. > > > What is te name of the moc binary for qt5? > 'moc' it seems: http://packages.ubuntu.com/xenial/amd64/qtbase5-dev-tools/filelist /usr/lib/x86_64-linux-gnu/qt5/bin/moc /usr/lib/x86_64-linux-gnu/qt5/bin/qdbuscpp2xml /usr/lib/x86_64-linux-gnu/qt5/bin/qdbusxml2cpp /usr/lib/x86_64-linux-gnu/qt5/bin/qdoc /usr/lib/x86_64-linux-gnu/qt5/bin/qlalr /usr/lib/x86_64-linux-gnu/qt5/bin/rcc /usr/lib/x86_64-linux-gnu/qt5/bin/syncqt.pl /usr/lib/x86_64-linux-gnu/qt5/bin/uic /usr/share/doc/qtbase5-dev-tools/LGPL_EXCEPTION.txt /usr/share/doc/qtbase5-dev-tools/changelog.Debian.gz /usr/share/doc/qtbase5-dev-tools/copyright /usr/share/man/man1/moc-qt5.1.gz -- Do you think you know what math is? http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02 Or what it means to be intelligent? http://www.ideasroadshow.com/issues/john-duncan-2013-08-30 Think again: http://www.ideasroadshow.com/library
Re: build requirements for Qt5 build
Le 31/05/2016 à 11:57, Liviu Andronic a écrit : You do not need any qt4 stuff. It may be that moc is named moc5 or something for qt5. Or that moc is a link to something else. Just checked and Qt5 moc comes with qtbase5-dev-tools, which is automatically pulled by qtbase5-dev. For some reason the correct moc compiler is still not detected, though. What is te name of the moc binary for qt5?
Re: build requirements for Qt5 build
On Tue, May 31, 2016 at 11:50 AM, Jean-Marc Lasgouttes wrote: > Le 31/05/2016 à 11:47, Liviu Andronic a écrit : > So either it is a Qt4 moc and qt4 is not corectly installed, or something else is wrong. >>> Since I'm building only for Qt5 (so using qtbase5-dev), should I also >>> install Qt4 development libraries (i.e. libqt4-dev)? >>> >> I'm definitely not getting the right moc files. I tried adding >> libqt4-dev, and now the compilation error message is as follows: >> >> https://launchpadlibrarian.net/262539787/buildlog_ubuntu-xenial-amd64.lyx_2.2.0-2~xenial~ppa8_BUILDING.txt.gz >> == The found moc compiler is for Qt 4.8.7 but the Qt library version is >> 5.5.1. >> >> Not sure where to go from here. > > > You do not need any qt4 stuff. It may be that moc is named moc5 or something > for qt5. Or that moc is a link to something else. > Just checked and Qt5 moc comes with qtbase5-dev-tools, which is automatically pulled by qtbase5-dev. For some reason the correct moc compiler is still not detected, though. Liviu > JMarc > -- Do you think you know what math is? http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02 Or what it means to be intelligent? http://www.ideasroadshow.com/issues/john-duncan-2013-08-30 Think again: http://www.ideasroadshow.com/library
Re: build requirements for Qt5 build
Le 31/05/2016 à 11:38, Liviu Andronic a écrit : On Tue, May 31, 2016 at 11:31 AM, Jean-Marc Lasgouttes wrote: Le 31/05/2016 à 11:21, Liviu Andronic a écrit : If it is, you may need to add something to your include path. Or we may need to use something more reasonable than #include #include At least qstring.h seems very old-fashionned. I've added libqt5svg5-dev and at least this part is now working: I'd still like to know about qglobal.h location. Since I'm installing qtbase5-dev, I suspect it will end up here (depending on platform): http://packages.ubuntu.com/search?searchon=contents&keywords=qglobal.h&mode=exactfilename&suite=xenial&arch=any /usr/include/i386-linux-gnu/qt5/QtCore/qglobal.h /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h How do we get configure to guess such peculiar path? JMarc
Re: build requirements for Qt5 build
Le 31/05/2016 à 11:47, Liviu Andronic a écrit : So either it is a Qt4 moc and qt4 is not corectly installed, or something else is wrong. Since I'm building only for Qt5 (so using qtbase5-dev), should I also install Qt4 development libraries (i.e. libqt4-dev)? I'm definitely not getting the right moc files. I tried adding libqt4-dev, and now the compilation error message is as follows: https://launchpadlibrarian.net/262539787/buildlog_ubuntu-xenial-amd64.lyx_2.2.0-2~xenial~ppa8_BUILDING.txt.gz == The found moc compiler is for Qt 4.8.7 but the Qt library version is 5.5.1. Not sure where to go from here. You do not need any qt4 stuff. It may be that moc is named moc5 or something for qt5. Or that moc is a link to something else. JMarc
Re: build requirements for Qt5 build
On Tue, May 31, 2016 at 11:38 AM, Liviu Andronic wrote: > On Tue, May 31, 2016 at 11:31 AM, Jean-Marc Lasgouttes > wrote: >> Le 31/05/2016 à 11:21, Liviu Andronic a écrit : If it is, you may need to add something to your include path. Or we may need to use something more reasonable than #include #include At least qstring.h seems very old-fashionned. >>> I've added libqt5svg5-dev and at least this part is now working: >> >> >> I'd still like to know about qglobal.h location. >> > Since I'm installing qtbase5-dev, I suspect it will end up here > (depending on platform): > http://packages.ubuntu.com/search?searchon=contents&keywords=qglobal.h&mode=exactfilename&suite=xenial&arch=any > > /usr/include/i386-linux-gnu/qt5/QtCore/qglobal.h > /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h > > > > >>> >>> https://launchpadlibrarian.net/262536549/buildlog_ubuntu-xenial-amd64.lyx_2.2.0-2~xenial~ppa5_BUILDING.txt.gz >>> checking for moc-qt5... no >>> checking for moc... /usr/bin/moc >> >> >> When compiling, moc says: >> >> /usr/bin/moc -o moc_Compare.cpp ../../src/Compare.h >> moc: could not find a Qt installation of '' >> >> So either it is a Qt4 moc and qt4 is not corectly installed, or something >> else is wrong. >> > Since I'm building only for Qt5 (so using qtbase5-dev), should I also > install Qt4 development libraries (i.e. libqt4-dev)? > I'm definitely not getting the right moc files. I tried adding libqt4-dev, and now the compilation error message is as follows: https://launchpadlibrarian.net/262539787/buildlog_ubuntu-xenial-amd64.lyx_2.2.0-2~xenial~ppa8_BUILDING.txt.gz == The found moc compiler is for Qt 4.8.7 but the Qt library version is 5.5.1. Not sure where to go from here. Liviu > Liviu > > >> JMarc >> > > > > -- > Do you think you know what math is? > http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02 > Or what it means to be intelligent? > http://www.ideasroadshow.com/issues/john-duncan-2013-08-30 > Think again: > http://www.ideasroadshow.com/library -- Do you think you know what math is? http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02 Or what it means to be intelligent? http://www.ideasroadshow.com/issues/john-duncan-2013-08-30 Think again: http://www.ideasroadshow.com/library
Re: build requirements for Qt5 build
On Tue, May 31, 2016 at 11:31 AM, Jean-Marc Lasgouttes wrote: > Le 31/05/2016 à 11:21, Liviu Andronic a écrit : >>> >>> If it is, you may need to add something >>> to your include path. Or we may need to use something more reasonable >>> than >>> #include >>> #include >>> >>> At least qstring.h seems very old-fashionned. >>> >> I've added libqt5svg5-dev and at least this part is now working: > > > I'd still like to know about qglobal.h location. > Since I'm installing qtbase5-dev, I suspect it will end up here (depending on platform): http://packages.ubuntu.com/search?searchon=contents&keywords=qglobal.h&mode=exactfilename&suite=xenial&arch=any /usr/include/i386-linux-gnu/qt5/QtCore/qglobal.h /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h >> >> https://launchpadlibrarian.net/262536549/buildlog_ubuntu-xenial-amd64.lyx_2.2.0-2~xenial~ppa5_BUILDING.txt.gz >> checking for moc-qt5... no >> checking for moc... /usr/bin/moc > > > When compiling, moc says: > > /usr/bin/moc -o moc_Compare.cpp ../../src/Compare.h > moc: could not find a Qt installation of '' > > So either it is a Qt4 moc and qt4 is not corectly installed, or something > else is wrong. > Since I'm building only for Qt5 (so using qtbase5-dev), should I also install Qt4 development libraries (i.e. libqt4-dev)? Liviu > JMarc > -- Do you think you know what math is? http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02 Or what it means to be intelligent? http://www.ideasroadshow.com/issues/john-duncan-2013-08-30 Think again: http://www.ideasroadshow.com/library
Re: build requirements for Qt5 build
Le 31/05/2016 à 11:21, Liviu Andronic a écrit : If it is, you may need to add something to your include path. Or we may need to use something more reasonable than #include #include At least qstring.h seems very old-fashionned. I've added libqt5svg5-dev and at least this part is now working: I'd still like to know about qglobal.h location. https://launchpadlibrarian.net/262536549/buildlog_ubuntu-xenial-amd64.lyx_2.2.0-2~xenial~ppa5_BUILDING.txt.gz checking for moc-qt5... no checking for moc... /usr/bin/moc When compiling, moc says: /usr/bin/moc -o moc_Compare.cpp ../../src/Compare.h moc: could not find a Qt installation of '' So either it is a Qt4 moc and qt4 is not corectly installed, or something else is wrong. JMarc
Re: build requirements for Qt5 build
an On Tue, May 31, 2016 at 11:11 AM, Jean-Marc Lasgouttes wrote: > Le 31/05/2016 à 11:06, Jean-Marc Lasgouttes a écrit : >> >> Le 31/05/2016 à 10:57, Liviu Andronic a écrit : Could we see your config.log? >>> I think it's automatically dumped here after the configure error: >>> >>> https://launchpadlibrarian.net/262531359/buildlog_ubuntu-xenial-i386.lyx_2.2.0-2~xenial~ppa3_BUILDING.txt.gz >>> >> >> I see complaints about missing Qt5Svg. Did you install the necessary >> packages? > > > This complaint is in the part that relies on pkg-config. > > Then configure tries to find Qt in the good old way, and qglobal.h cannot be > found. Is it somewhere on your disk? > I am building on Launchpad which generates a fresh, minimal Ubuntu install. So it will only detect what the various packages install on the image. > If it is, you may need to add something > to your include path. Or we may need to use something more reasonable than > #include > #include > > At least qstring.h seems very old-fashionned. > I've added libqt5svg5-dev and at least this part is now working: https://launchpadlibrarian.net/262536549/buildlog_ubuntu-xenial-amd64.lyx_2.2.0-2~xenial~ppa5_BUILDING.txt.gz checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for QT_CORE... yes checking for QT_FRONTEND... yes checking whether Qt uses the X Window system... yes checking for moc-qt5... no checking for moc... /usr/bin/moc checking for uic-qt5... no checking for uic... /usr/bin/uic checking for rcc-qt5... no checking for rcc... /usr/bin/rcc And configure ends up gracefully: Configuration Host type: x86_64-pc-linux-gnu Special build flags: build=release warnings c++11 std-regex use-aspell use-enchant use-hunspell C++ Compiler: g++ (5.3.1) C++ Compiler flags: -Wall -Wextra -std=c++11 -fPIC -O2 -Wno-deprecated-declarations C++ Compiler user flags: Linker flags: Linker user flags: Qt Frontend: Qt version: 5.5.1 Packaging: posix LyX binary dir: /usr/bin LyX files dir: /usr/share/lyx === The following minor problems have been detected by configure. === Please check the messages below before running 'make'. === (see the section 'Problems' in the INSTALL file) == The found moc compiler is for Qt moc: could not find a Qt installation of '' but the Qt library version is 5.5.1. Though I'm not sure what this last message means, and compilation itself fails. Liviu > JMarc > -- Do you think you know what math is? http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02 Or what it means to be intelligent? http://www.ideasroadshow.com/issues/john-duncan-2013-08-30 Think again: http://www.ideasroadshow.com/library
Re: build requirements for Qt5 build
Le 31/05/2016 à 11:06, Jean-Marc Lasgouttes a écrit : Le 31/05/2016 à 10:57, Liviu Andronic a écrit : Could we see your config.log? I think it's automatically dumped here after the configure error: https://launchpadlibrarian.net/262531359/buildlog_ubuntu-xenial-i386.lyx_2.2.0-2~xenial~ppa3_BUILDING.txt.gz I see complaints about missing Qt5Svg. Did you install the necessary packages? This complaint is in the part that relies on pkg-config. Then configure tries to find Qt in the good old way, and qglobal.h cannot be found. Is it somewhere on your disk? If it is, you may need to add something to your include path. Or we may need to use something more reasonable than #include #include At least qstring.h seems very old-fashionned. JMarc
Re: build requirements for Qt5 build
Le 31/05/2016 à 10:57, Liviu Andronic a écrit : Could we see your config.log? I think it's automatically dumped here after the configure error: https://launchpadlibrarian.net/262531359/buildlog_ubuntu-xenial-i386.lyx_2.2.0-2~xenial~ppa3_BUILDING.txt.gz I see complaints about missing Qt5Svg. Did you install the necessary packages? JMarc
Re: build requirements for Qt5 build
On Tue, May 31, 2016 at 10:55 AM, Jean-Marc Lasgouttes wrote: > Le 31/05/2016 à 10:53, Liviu Andronic a écrit : checking for QT_CORE... yes checking for QT_FRONTEND... checking for X... libraries , headers checking for gethostbyname... yes checking for connect... yes checking for remove... yes checking for shmat... yes checking for IceConnectionNumber in -lICE... yes checking for Qt library name... failed configure: error: cannot compile a simple Qt executable. Check you have the right $QTDIR. Am I missing something else? > > > Could we see your config.log? > I think it's automatically dumped here after the configure error: https://launchpadlibrarian.net/262531359/buildlog_ubuntu-xenial-i386.lyx_2.2.0-2~xenial~ppa3_BUILDING.txt.gz See line: ==> config.log <== Liviu > JMarc -- Do you think you know what math is? http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02 Or what it means to be intelligent? http://www.ideasroadshow.com/issues/john-duncan-2013-08-30 Think again: http://www.ideasroadshow.com/library
Re: build requirements for Qt5 build
Le 31/05/2016 à 10:53, Liviu Andronic a écrit : checking for QT_CORE... yes checking for QT_FRONTEND... checking for X... libraries , headers checking for gethostbyname... yes checking for connect... yes checking for remove... yes checking for shmat... yes checking for IceConnectionNumber in -lICE... yes checking for Qt library name... failed configure: error: cannot compile a simple Qt executable. Check you have the right $QTDIR. Am I missing something else? Could we see your config.log? JMarc
Re: build requirements for Qt5 build
On Tue, May 31, 2016 at 10:50 AM, Kornel Benko wrote: > Am Dienstag, 31. Mai 2016 um 10:33:46, schrieb Liviu Andronic > >> On Tue, May 31, 2016 at 10:21 AM, Kornel Benko wrote: >> > Am Dienstag, 31. Mai 2016 um 10:04:54, schrieb Liviu Andronic >> > >> >> Dear all, >> >> I am trying to build 2.2.0 using Qt5 on Ubuntu 16.04 but fail. I've >> >> added qtbase5-dev and qtdeclarative5-dev to the build deps, but for >> >> some reason this seems to be insufficient and configure ends up in an >> >> error: >> >> >> >> https://launchpadlibrarian.net/262523166/buildlog_ubuntu-xenial-amd64.lyx_2.2.0-2~xenial~ppa2_BUILDING.txt.gz >> >> >> >> checking for QT_CORE... yes >> >> checking for QT_FRONTEND... checking for X... libraries , headers >> >> checking for gethostbyname... yes >> >> checking for connect... yes >> >> checking for remove... yes >> >> checking for shmat... yes >> >> checking for IceConnectionNumber in -lICE... no >> >> checking for Qt library name... failed >> >> configure: error: cannot compile a simple Qt executable. Check you >> >> have the right $QTDIR. >> >> >> >> Should $QTDIR somehow be explicitly passed to configure? >> > >> > QTDIR is environment variable, but as other libs QT libs are found, you >> > don't neet to set it. >> > >> > But from your log, you are missing libICE. >> > Package libice-dev ... >> > >> >> Thanks. I add the dep but I'm getting the same error: >> https://launchpadlibrarian.net/262531359/buildlog_ubuntu-xenial-i386.lyx_2.2.0-2~xenial~ppa3_BUILDING.txt.gz >> >> checking for QT_CORE... yes >> checking for QT_FRONTEND... checking for X... libraries , headers >> checking for gethostbyname... yes >> checking for connect... yes >> checking for remove... yes >> checking for shmat... yes >> checking for IceConnectionNumber in -lICE... yes >> checking for Qt library name... failed >> configure: error: cannot compile a simple Qt executable. Check you >> have the right $QTDIR. >> >> Am I missing something else? >> >> Regards, >> Liviu > > Did you run ./autogen.sh prior to configure? > No, I didn't. But is it necessary for release tarballs? For the Qt4 builds of 2.2.0 I'm not running ./autogen.sh either, but compilation proceeds as expected... So maybe we're missing something in our Qt5 setup... Liviu > I am getting totally different output. > ... > checking for QT_CORE... yes > checking for QT_FRONTEND... yes > checking whether Qt uses the X Window system... yes > checking for moc-qt5... no > checking for moc... /usr/BUILD/BuildQt5/5.6/gcc_64/bin/moc > checking for uic-qt5... no > checking for uic... /usr/BUILD/BuildQt5/5.6/gcc_64/bin/uic > checking for rcc-qt5... no > checking for rcc... /usr/BUILD/BuildQt5/5.6/gcc_64/bin/rcc > checking whether NLS is requested... yes > ... > > Kornel >> >> >> >> Regards, >> >> Liviu >> > >> > Kornel >> >> >> >> -- Do you think you know what math is? http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02 Or what it means to be intelligent? http://www.ideasroadshow.com/issues/john-duncan-2013-08-30 Think again: http://www.ideasroadshow.com/library
Re: build requirements for Qt5 build
Am Dienstag, 31. Mai 2016 um 10:33:46, schrieb Liviu Andronic > On Tue, May 31, 2016 at 10:21 AM, Kornel Benko wrote: > > Am Dienstag, 31. Mai 2016 um 10:04:54, schrieb Liviu Andronic > > > >> Dear all, > >> I am trying to build 2.2.0 using Qt5 on Ubuntu 16.04 but fail. I've > >> added qtbase5-dev and qtdeclarative5-dev to the build deps, but for > >> some reason this seems to be insufficient and configure ends up in an > >> error: > >> > >> https://launchpadlibrarian.net/262523166/buildlog_ubuntu-xenial-amd64.lyx_2.2.0-2~xenial~ppa2_BUILDING.txt.gz > >> > >> checking for QT_CORE... yes > >> checking for QT_FRONTEND... checking for X... libraries , headers > >> checking for gethostbyname... yes > >> checking for connect... yes > >> checking for remove... yes > >> checking for shmat... yes > >> checking for IceConnectionNumber in -lICE... no > >> checking for Qt library name... failed > >> configure: error: cannot compile a simple Qt executable. Check you > >> have the right $QTDIR. > >> > >> Should $QTDIR somehow be explicitly passed to configure? > > > > QTDIR is environment variable, but as other libs QT libs are found, you > > don't neet to set it. > > > > But from your log, you are missing libICE. > > Package libice-dev ... > > > > Thanks. I add the dep but I'm getting the same error: > https://launchpadlibrarian.net/262531359/buildlog_ubuntu-xenial-i386.lyx_2.2.0-2~xenial~ppa3_BUILDING.txt.gz > > checking for QT_CORE... yes > checking for QT_FRONTEND... checking for X... libraries , headers > checking for gethostbyname... yes > checking for connect... yes > checking for remove... yes > checking for shmat... yes > checking for IceConnectionNumber in -lICE... yes > checking for Qt library name... failed > configure: error: cannot compile a simple Qt executable. Check you > have the right $QTDIR. > > Am I missing something else? > > Regards, > Liviu Did you run ./autogen.sh prior to configure? I am getting totally different output. ... checking for QT_CORE... yes checking for QT_FRONTEND... yes checking whether Qt uses the X Window system... yes checking for moc-qt5... no checking for moc... /usr/BUILD/BuildQt5/5.6/gcc_64/bin/moc checking for uic-qt5... no checking for uic... /usr/BUILD/BuildQt5/5.6/gcc_64/bin/uic checking for rcc-qt5... no checking for rcc... /usr/BUILD/BuildQt5/5.6/gcc_64/bin/rcc checking whether NLS is requested... yes ... Kornel > > > >> Regards, > >> Liviu > > > > Kornel > > > > signature.asc Description: This is a digitally signed message part.
Re: build requirements for Qt5 build
On Tue, May 31, 2016 at 10:21 AM, Kornel Benko wrote: > Am Dienstag, 31. Mai 2016 um 10:04:54, schrieb Liviu Andronic > >> Dear all, >> I am trying to build 2.2.0 using Qt5 on Ubuntu 16.04 but fail. I've >> added qtbase5-dev and qtdeclarative5-dev to the build deps, but for >> some reason this seems to be insufficient and configure ends up in an >> error: >> >> https://launchpadlibrarian.net/262523166/buildlog_ubuntu-xenial-amd64.lyx_2.2.0-2~xenial~ppa2_BUILDING.txt.gz >> >> checking for QT_CORE... yes >> checking for QT_FRONTEND... checking for X... libraries , headers >> checking for gethostbyname... yes >> checking for connect... yes >> checking for remove... yes >> checking for shmat... yes >> checking for IceConnectionNumber in -lICE... no >> checking for Qt library name... failed >> configure: error: cannot compile a simple Qt executable. Check you >> have the right $QTDIR. >> >> Should $QTDIR somehow be explicitly passed to configure? > > QTDIR is environment variable, but as other libs QT libs are found, you don't > neet to set it. > > But from your log, you are missing libICE. > Package libice-dev ... > Thanks. I add the dep but I'm getting the same error: https://launchpadlibrarian.net/262531359/buildlog_ubuntu-xenial-i386.lyx_2.2.0-2~xenial~ppa3_BUILDING.txt.gz checking for QT_CORE... yes checking for QT_FRONTEND... checking for X... libraries , headers checking for gethostbyname... yes checking for connect... yes checking for remove... yes checking for shmat... yes checking for IceConnectionNumber in -lICE... yes checking for Qt library name... failed configure: error: cannot compile a simple Qt executable. Check you have the right $QTDIR. Am I missing something else? Regards, Liviu >> Regards, >> Liviu > > Kornel -- Do you think you know what math is? http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02 Or what it means to be intelligent? http://www.ideasroadshow.com/issues/john-duncan-2013-08-30 Think again: http://www.ideasroadshow.com/library
Re: build requirements for Qt5 build
Am Dienstag, 31. Mai 2016 um 10:04:54, schrieb Liviu Andronic > Dear all, > I am trying to build 2.2.0 using Qt5 on Ubuntu 16.04 but fail. I've > added qtbase5-dev and qtdeclarative5-dev to the build deps, but for > some reason this seems to be insufficient and configure ends up in an > error: > > https://launchpadlibrarian.net/262523166/buildlog_ubuntu-xenial-amd64.lyx_2.2.0-2~xenial~ppa2_BUILDING.txt.gz > > checking for QT_CORE... yes > checking for QT_FRONTEND... checking for X... libraries , headers > checking for gethostbyname... yes > checking for connect... yes > checking for remove... yes > checking for shmat... yes > checking for IceConnectionNumber in -lICE... no > checking for Qt library name... failed > configure: error: cannot compile a simple Qt executable. Check you > have the right $QTDIR. > > Should $QTDIR somehow be explicitly passed to configure? QTDIR is environment variable, but as other libs QT libs are found, you don't neet to set it. But from your log, you are missing libICE. Package libice-dev ... > Regards, > Liviu Kornel signature.asc Description: This is a digitally signed message part.
build requirements for Qt5 build
Dear all, I am trying to build 2.2.0 using Qt5 on Ubuntu 16.04 but fail. I've added qtbase5-dev and qtdeclarative5-dev to the build deps, but for some reason this seems to be insufficient and configure ends up in an error: https://launchpadlibrarian.net/262523166/buildlog_ubuntu-xenial-amd64.lyx_2.2.0-2~xenial~ppa2_BUILDING.txt.gz checking for QT_CORE... yes checking for QT_FRONTEND... checking for X... libraries , headers checking for gethostbyname... yes checking for connect... yes checking for remove... yes checking for shmat... yes checking for IceConnectionNumber in -lICE... no checking for Qt library name... failed configure: error: cannot compile a simple Qt executable. Check you have the right $QTDIR. Should $QTDIR somehow be explicitly passed to configure? Regards, Liviu -- Do you think you know what math is? http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02 Or what it means to be intelligent? http://www.ideasroadshow.com/issues/john-duncan-2013-08-30 Think again: http://www.ideasroadshow.com/library