On 2013-09-09 08:59+0200 Arjen Markus wrote: > I have an X Window installation available: > - the xwin device looks fairly nice (the fonts are as always rather > wriggly) > - the xcairo device produces samller graphs for some reason and it > does not take the -display command line argument (whereas the xwin > device does). Something to be repaired, I'd say. I had to use the > DISPLAY environment variable instead. > > (I do not have a window manager running yet, so the windows are created > full-screen) > >> Did your good test results also include the test_interactive target? >> That target should exercise all interactive devices (such as xcairo if >> that is available) that you have built. >> > > The non-interactive tests were almost as clean as possible.
Do you get similar good results for the test_interactive (as opposed to test_noninteractive) target? Warning... this target is a bit of a pain to run because you have to do some clicking (or hitting return) on the GUI's to move through some of the examples. But for completeness you should run it (using make test_interactive >& test_interactive.out to capture most error/warning messages in test_interactive.out) because it exercises a different set of devices (the interactive devices rather than the file devices exercised by the the test_noninteractive target). >> I am glad you got Python to work since that is a really important >> computer language for scientists. I suspect Java is equally important >> for other groups, but if some quick attempts to fix Java language >> support on Cygwin do not work, I would set it aside for now and move >> on to getting the qt devices to work (which requires installation of >> the Qt4 development packages). That would be just as important a >> breakthrough as you have just had with the cairo devices. >> > > Now we come to the disappointing part: > Qt4 will not currently work on Cygwin, I am afraid. At least this initial issue should be easy to overcome. > Here are the details: > - I installed all the things Qt4 I could find in the set-up, but the > essential program qmake.exe was still missing. qmake.exe (which I agree is absolutely essential) is contained in the development form of the Qt4 libraries. To find the appropriate package names, look at http://cygwin.com/packages and use the regex search box there. Just now I used that search box to check for qmake.exe, and I got three hits: x86/libQtCore4-devel/libQtCore4-devel-4.8.4-1 x86/libQtCore4-devel/libQtCore4-devel-4.8.4-2 x86/libqt3-devel/libqt3-devel-3.3.8b-12 I am virtually positive you will want to install libQtCore4-devel-4.8.4-2 (assuming you have already installed the 4.8.4-2 version of Qt libraries including libQtCore4-4.8.4-2). 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 __________________________ ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk _______________________________________________ Plplot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plplot-devel
