plplot-devel

[Plplot-devel] How to build with QT5?

[Hazen B. <hba...@ma...>]

How does one get PLplot to build with QT5 now?

This is what I used to do:
cmake -DPLPLOT_USE_QT5=ON ../plplot

However the cmake cache now has the following mistakes (or what appear 
to me to be mistakes):

//Enable pyqt4 Python extension module
ENABLE_pyqt4:BOOL=ON

//Enable pyqt5 Python extension module
ENABLE_pyqt5:BOOL=OFF

..

//Where can the qmake-qt4 library be found
QT_QMAKE_EXECUTABLE:FILEPATH=/usr/bin/qmake-qt4

PyQt4 will not work with Qt5, and qmake-qt4 also seems to be the wrong 
choice for a Qt5 build.

-Hazen

Re: [Plplot-devel] How to build with QT5?

[Alan W. I. <ir...@be...>]

On 2016-11-17 16:35-0500 Hazen Babcock wrote:

>
> How does one get PLplot to build with QT5 now?
>
> This is what I used to do:
> cmake -DPLPLOT_USE_QT5=ON ../plplot
>
> However the cmake cache now has the following mistakes (or what appear to me 
> to be mistakes):
>
> //Enable pyqt4 Python extension module
> ENABLE_pyqt4:BOOL=ON
>
> //Enable pyqt5 Python extension module
> ENABLE_pyqt5:BOOL=OFF
>
> ..
>
> //Where can the qmake-qt4 library be found
> QT_QMAKE_EXECUTABLE:FILEPATH=/usr/bin/qmake-qt4
>
> PyQt4 will not work with Qt5, and qmake-qt4 also seems to be the wrong choice 
> for a Qt5 build.

Hi Hazen:

My recent set of changes introduced no changes concerning the meaning
of PLPLOT_USE_QT5.  In fact, my recent tests of those changes (see my
commit message) show Plplot builds properly here with both
-DPLPLOT_USE_QT5=ON (i.e., Qt5) and -DPLPLOT_USE_QT5=OFF (i.e, Qt4).
But in each case I used scripts/comprehensive_test.sh which
automatically executes cmake in the ideal way, i.e., in an initially
empty build tree.

In your case, it looks like -DPLPLOT_USE_QT5=ON is being ignored and
you are getting consistent Qt4 results instead.  (Your cache file
reports PLPLOT_USE_QT5=OFF and nothing is found that is Qt5 related.)

Is a dirty build tree reflecting previous Qt4 builds causing you the
present difficulties with attempting to use Qt5?

Of course, if that speculation is not correct, then the next thing you
should do is look at your complete cmake output starting with an empty
build tree and pristine source tree to see what it says regarding
finding Qt5 when you specify -DPLPLOT_USE_QT5=ON.  If our build system cannot
find Qt5 with -DPLPLOT_USE_QT5=ON it forces PLPLOT_USE_QT5 to
OFF and falls back to looking for and using Qt4 in a consistent way.

So either scenario (dirty build tree or cannot find Qt5) is consistent
with your current cache file.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

Re: [Plplot-devel] How to build with QT5?

[Hazen B. <hba...@ma...>]

On 11/17/2016 07:26 PM, Alan W. Irwin wrote:
>
> Hi Hazen:
>
> My recent set of changes introduced no changes concerning the meaning
> of PLPLOT_USE_QT5.  In fact, my recent tests of those changes (see my
> commit message) show Plplot builds properly here with both
> -DPLPLOT_USE_QT5=ON (i.e., Qt5) and -DPLPLOT_USE_QT5=OFF (i.e, Qt4).
> But in each case I used scripts/comprehensive_test.sh which
> automatically executes cmake in the ideal way, i.e., in an initially
> empty build tree.
>
> In your case, it looks like -DPLPLOT_USE_QT5=ON is being ignored and
> you are getting consistent Qt4 results instead.  (Your cache file
> reports PLPLOT_USE_QT5=OFF and nothing is found that is Qt5 related.)
>
> Is a dirty build tree reflecting previous Qt4 builds causing you the
> present difficulties with attempting to use Qt5?
>
> Of course, if that speculation is not correct, then the next thing you
> should do is look at your complete cmake output starting with an empty
> build tree and pristine source tree to see what it says regarding
> finding Qt5 when you specify -DPLPLOT_USE_QT5=ON.  If our build system
> cannot
> find Qt5 with -DPLPLOT_USE_QT5=ON it forces PLPLOT_USE_QT5 to
> OFF and falls back to looking for and using Qt4 in a consistent way.
>
> So either scenario (dirty build tree or cannot find Qt5) is consistent
> with your current cache file.

Sorry, it appears that I was missing the qttools5-dev package.

As an aside it looks like x02c works fine with Qt5 even in -fam mode.

-Hazen

Re: [Plplot-devel] How to build with QT5?

[Alan W. I. <ir...@be...>]

On 2016-11-17 20:43-0500 Hazen Babcock wrote:

> Sorry, it appears that I was missing the qttools5-dev package.

Glad that "how to build" issue is sorted out.

> As an aside it looks like x02c works fine with Qt5 even in -fam mode.

Does that mean valgrind reports no memory management issues?  That is
a pretty reliable measurement of the probability of encountering
segfaults with Qt5, and would be an important improvement compared to
my Qt5 version 5.3.2 from Debian Jessie.

Alan

__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

Re: [Plplot-devel] How to build with QT5?

[Hazen B. <hba...@ma...>]

On 11/18/2016 02:34 AM, Alan W. Irwin wrote:
> On 2016-11-17 20:43-0500 Hazen Babcock wrote:
>
>> Sorry, it appears that I was missing the qttools5-dev package.
>
> Glad that "how to build" issue is sorted out.
>
>> As an aside it looks like x02c works fine with Qt5 even in -fam mode.
>
> Does that mean valgrind reports no memory management issues?  That is
> a pretty reliable measurement of the probability of encountering
> segfaults with Qt5, and would be an important improvement compared to
> my Qt5 version 5.3.2 from Debian Jessie.

I just meant that it ran without segfaulting. However it does also seem 
to have fewer invalid reads than the Qt4 equivalent.

$ qmake --version
QMake version 3.0
Using Qt version 5.5.1 in /usr/lib/x86_64-linux-gnu

-Hazen