On 2015-06-06 13:56+0100 Phil Rosenberg wrote:

> I sent my previous email to just alan rather than reply all - Arjen
> and others see below.
>
> I've just uploaded a commit which means FindwxWidgets.cmake looks for
> wx-config-3.0 and wx-config-2.8. This will work for now while we only
> have those two versions to check for, but frustratingly this means
> that we will have to update when each new version comes out. Alan your
> better CMAKE skill might mean you can come up with a better solution.

Hi Phil:

Good catch on the versioned wx-config names for Cygwin!

I did find a slicker solution for those various names, see commit 215a6f6.  
Furthermore,
it turns out that CMake-3.3.0-rc1 has already started to deal with
this issue (they search for

wx-config-3.0 wx-config

), but obviously
that is not enough so I have just posted to the CMake developer list
asking them to change that list of aliases to

wx-config-3.0 wx-config-2.9 wx-config-2.8 wx-config

which is what we are adopting locally for PLplot.

> This change allows wxWidgets to be found on my Cygwin install. I can
> build the library and examples, but unfortunately the Cygwin upgrade
> that occurred alongside my wxWidgets install appears to have stuffed
> up my X11 setup so I can't test it running right now.
>
> Arjen if you are testing this immediately you might need to include
> -DPLD_wxwidgets=ON until Alan is happy to reenable wxWidgets by
> default after my Linux build issue the other day.

@Phil and Arjen:

I can now build the wxwidgets device driver on Linux against
wxwidgets-2.8 so I have now changed our build system (commit ID
354bffe) so that PLD_wxwidgets=ON by default.

@Phil:

However, the wxwidgets device is still extraordinarily slow on Linux,
e.g.,

software@raven> time examples/c/x00c -dev wxwidgets

real    0m8.755s
user    0m0.028s
sys     0m0.068s

You should be able to verify this slowness yourself (using the time
application [which comes with bash] as above) when you try master tip
on your Linux platform.  Note also, the actual cpu time as measured by
user and sys is quite small. I also verify that during mass testing of
-dev wxwidgets via the test_c_wxwidgets target, the actual CPU use is
negligible with a GUI I have that measures overall CPU usage.  So
something else than CPU usage is slowing down the app. You have
mentioned before that there is a polling interval you can set so I
assume some adjustment of that will reduce the real time to something
much more reasonable.  I wonder, for example, whether this trouble is
caused by the units of that polling interval being different on Linux
versus Windows?

@Arjen:

If the current wxwidgets slowness on Linux is also true on Cygwin, it
will not affect your comprehensive testing even if you do the
interactive part of it.  The reason is that I have deliberately
removed wxwidgets tests from overall testing targets such as
test_interactive until these slowness issues and in particular the -np
issue can be fixed.  However, you and Phil can build the test_c_wxwidgets
target by itself from the build tree on Cygwin to evaluate how
fast a fairly wide subset of the examples will render with the wxwidgets
device.

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
__________________________

------------------------------------------------------------------------------
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to