From: Arjen M. <Arj...@de...> - 2013-09-16 19:09:59
|
> -----Original Message----- > From: Arjen Markus [mailto:Arj...@de...] > Sent: Monday, September 16, 2013 8:54 PM > To: Alan W. Irwin > Cc: plp...@li... > Subject: Re: [Plplot-devel] Cygwin - for the next release? > > > Yes, several other device drivers were loaded successfully. I have not run the > test_noninteractive target yet. (That is running right now) > The test_noninteractive target shows a perfectly clean test result. Even the odd extra "L" for one of the Python output files has gone. Regards, Arjen DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. |
From: Arjen M. <Arj...@de...> - 2013-09-16 19:41:24
|
I can now confirm that the xcairo device accepts the -display argument. I had to build the libraries and the device drivers statically to avoid the build error I reported earlier, but it works. Regards, Arjen DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. |
From: Alan W. I. <ir...@be...> - 2013-09-16 19:54:51
|
On 2013-09-16 18:53-0000 Arjen Markus wrote: > Turning off the cairo devices made the build process succeed and ... eh presto! > We have Qt4 on Cygwin. Nice result. > > Just a few minor oddities: > > - The X Window device is extraordinarily slow - normally the four plots of example 1 are > shown immediately, but now I saw each line segment being drawn. I do not know where > this coming from. On Linux -dev xwin is extremely fast since X is the native display capability, but the problem may be that X is inefficiently implemented on Cygwin. It is good to know that -dev xwin at least works, but I think you will likely prefer to use either -dev qtwidget or -dev xcairo since they have access to much better fonts. Because the xcairo device is based on X it may also be as slow as -dev xwin, but -dev qtwidget might be much faster since there is a chance it is based directly on the native Windows interactive display capability rather than X. Anyhow, try all the interactive devices (which the test_interactive target does for you as well) and see which you like the best in terms of speed and font choice. 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 __________________________ |
From: Arjen M. <Arj...@de...> - 2013-09-16 20:01:31
|
HI Alan, > -----Original Message----- > From: Alan W. Irwin [mailto:ir...@be...] > > On Linux -dev xwin is extremely fast since X is the native display capability, but the > problem may be that X is inefficiently implemented on Cygwin. > > It is good to know that -dev xwin at least works, but I think you will likely prefer to use > either -dev qtwidget or -dev xcairo since they have access to much better fonts. > Because the xcairo device is based on X it may also be as slow as -dev xwin, but - > dev qtwidget might be much faster since there is a chance it is based directly on the > native Windows interactive display capability rather than X. > > Anyhow, try all the interactive devices (which the test_interactive target does for you > as well) and see which you like the best in terms of speed and font choice. > xcairo is slow as well, but qtwidget does not work. I get the message: QWidget: Cannot create a QWidget when no GUI is being used Regards, Arjen DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. |
From: Alan W. I. <ir...@be...> - 2013-09-17 08:42:32
|
On 2013-09-16 20:01-0000 Arjen Markus wrote: > [I said] >> Anyhow, try all the interactive devices (which the test_interactive target does for you >> as well) and see which you like the best in terms of speed and font choice. >> > > xcairo is slow as well, but qtwidget does not work. I get the message: > > QWidget: Cannot create a QWidget when no GUI is being used I did a google search for that particular error message. There were a number of hits, but they all seemed to be concerned with misusing the Qt4 libraries on Unix, e.g., forgetting to use #include <QApplication> But we obviously do that (see include/qt.h), and we have no such trouble on Linux so I don't think our code misuses Qt4 at all. Therefore, I have no idea why you are getting this run-time error message on Cygwin. The only faint possibility I can think of is you might need to install some additional Qt4 component. But I am virtually positive that would generate a cmake WARNING message so I suggest you double check the cmake command output (cmake.out) for any such messages concerning Qt and also check your Qt4 installation for consistency, i.e. all versions the same, no additional Qt4 installations interfering, etc. If those checks don't give you any ideas, then you should also obviously check on the Cygwin mailing list although my google searching above found nothing Cygwin-specific about the above error message. 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 __________________________ |
From: Arjen M. <Arj...@de...> - 2013-09-17 10:54:53
|
Hi Alan, > -----Original Message----- > From: Alan W. Irwin [mailto:ir...@be...] > Sent: Tuesday, September 17, 2013 10:42 AM > To: Arjen Markus > Cc: plp...@li... > Subject: RE: [Plplot-devel] Cygwin - for the next release? > > On 2013-09-16 20:01-0000 Arjen Markus wrote: > > > [I said] > >> Anyhow, try all the interactive devices (which the test_interactive > >> target does for you as well) and see which you like the best in terms of speed and > font choice. > >> > > > > xcairo is slow as well, but qtwidget does not work. I get the message: > > > > QWidget: Cannot create a QWidget when no GUI is being used > > I did a google search for that particular error message. There were a number of hits, > but they all seemed to be concerned with misusing the > Qt4 libraries on Unix, e.g., forgetting to use > > #include <QApplication> > > But we obviously do that (see include/qt.h), and we have no such trouble on Linux so > I don't think our code misuses Qt4 at all. > Therefore, I have no idea why you are getting this run-time error message on Cygwin. > > The only faint possibility I can think of is you might need to install some additional > Qt4 component. But I am virtually positive that would generate a cmake WARNING > message so I suggest you double check the cmake command output (cmake.out) for > any such messages concerning Qt and also check your Qt4 installation for > consistency, i.e. all versions the same, no additional Qt4 installations interfering, etc. > > If those checks don't give you any ideas, then you should also obviously check on > the Cygwin mailing list although my google searching above found nothing Cygwin- > specific about the above error message. > The only warning message I can find that might be related is one about PyQt4. That seems related to CMake not finding the sip directory. I did note that pango is not found. Perhaps this is the cause for the cairo problems? For these I have been unable to find a reason - Google did not bring up anything that seemed relevant, nor did dependency walker or ldd show missing libraries. Well, I will try and dig further. Regards, Arjen DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. |
From: Arjen M. <Arj...@de...> - 2013-09-17 11:04:48
|
Hi, > -----Original Message----- > From: Arjen Markus [mailto:Arj...@de...] > Sent: Tuesday, September 17, 2013 12:50 PM > To: Alan W. Irwin > Cc: plp...@li... > Subject: Re: [Plplot-devel] Cygwin - for the next release? > > Hi Alan, > > ... > > I did note that pango is not found. Perhaps this is the cause for the cairo problems? > For these I have been unable to find a reason - Google did not bring up anything that > seemed relevant, nor did dependency walker or ldd show missing libraries. > > Well, I will try and dig further. > The message was actually about pango, pangoft2 AND lasi. It is the last that is not found. Regards, Arjen DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. |
From: Alan W. I. <ir...@be...> - 2013-09-17 17:34:22
|
On 2013-09-17 11:04-0000 Arjen Markus wrote: > Hi, > >> -----Original Message----- >> From: Arjen Markus [mailto:Arj...@de...] >> Sent: Tuesday, September 17, 2013 12:50 PM >> To: Alan W. Irwin >> Cc: plp...@li... >> Subject: Re: [Plplot-devel] Cygwin - for the next release? >> >> Hi Alan, >> >> ... >> >> I did note that pango is not found. Perhaps this is the cause for the cairo problems? >> For these I have been unable to find a reason - Google did not bring up anything that >> seemed relevant, nor did dependency walker or ldd show missing libraries. >> >> Well, I will try and dig further. >> > > The message was actually about pango, pangoft2 AND lasi. It is the last that is not found. Yes, you would have to build libLASi yourself on Cygwin in order to get the psttf device driver to work, but probably that psttf functionality is not worth the effort since you have all the different cairo (without dyndrivers) and qt PostScript device drivers working. It sounds to me like you are now finished with all the "easy" stuff on Cygwin, and the rest is going to take substantially more effort. Therefore, could you write up your current Cygwin results on our Wiki? Once that task is completed (hopefully in the next few days and still comfortably before the September 28th deadline for the release) I plan (unless you prefer to do it yourself) to write up the highlights of your Cygwin breakthrough in README.release while referring to your Wiki writeup for all the details. Of course, the wiki notes should include details of all the issues you encountered on the Cygwin platform, but in contrast I plan in README.release to emphasize the positive generalities of your breakthrough. After all, the fundamental goal of that section of the release notes should be to encourage Windows users to try out the Cygwin platform with many of the dependency issues solved so they get access to a much more complete and powerful PLplot than is readily available for other Windows platforms. If those release notes do encourage more Windows users to try building PLplot on Cygwin like I hope, then you might be able to recruit some additional manpower/expertise to help solve the remaining PLplot issues on Cygwin. 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 __________________________ |
From: Arjen M. <Arj...@de...> - 2013-09-18 06:27:28
|
Hi Alan, yes, I will write a report on my experiences with Cygwin now they are still fresh in my memory. I agree with you that the easy stuff is indeed done and I do not think I will get any further before the deadline. Regards, Arjen > -----Original Message----- > From: Alan W. Irwin [mailto:ir...@be...] > Sent: Tuesday, September 17, 2013 7:34 PM > To: Arjen Markus > Cc: plp...@li... > Subject: RE: [Plplot-devel] Cygwin - for the next release? > > On 2013-09-17 11:04-0000 Arjen Markus wrote: > > > Hi, > > > >> -----Original Message----- > >> From: Arjen Markus [mailto:Arj...@de...] > >> Sent: Tuesday, September 17, 2013 12:50 PM > >> To: Alan W. Irwin > >> Cc: plp...@li... > >> Subject: Re: [Plplot-devel] Cygwin - for the next release? > >> > >> Hi Alan, > >> > >> ... > >> > >> I did note that pango is not found. Perhaps this is the cause for the cairo > problems? > >> For these I have been unable to find a reason - Google did not bring > >> up anything that seemed relevant, nor did dependency walker or ldd show > missing libraries. > >> > >> Well, I will try and dig further. > >> > > > > The message was actually about pango, pangoft2 AND lasi. It is the last that is not > found. > > Yes, you would have to build libLASi yourself on Cygwin in order to get the psttf > device driver to work, but probably that psttf functionality is not worth the effort since > you have all the different cairo (without dyndrivers) and qt PostScript device drivers > working. > > It sounds to me like you are now finished with all the "easy" stuff on Cygwin, and the > rest is going to take substantially more effort. > Therefore, could you write up your current Cygwin results on our Wiki? > > Once that task is completed (hopefully in the next few days and still comfortably > before the September 28th deadline for the release) I plan (unless you prefer to do it > yourself) to write up the highlights of your Cygwin breakthrough in README.release > while referring to your Wiki writeup for all the details. Of course, the wiki notes > should include details of all the issues you encountered on the Cygwin platform, but > in contrast I plan in README.release to emphasize the positive generalities of your > breakthrough. After all, the fundamental goal of that section of the release notes > should be to encourage Windows users to try out the Cygwin platform with many of > the dependency issues solved so they get access to a much more complete and > powerful PLplot than is readily available for other Windows platforms. If those release > notes do encourage more Windows users to try building PLplot on Cygwin like I hope, > then you might be able to recruit some additional manpower/expertise to help solve > the remaining PLplot issues on Cygwin. > > 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 > __________________________ DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. |