You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
(14) |
Jun
(1) |
Jul
(3) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(16) |
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(13) |
Feb
(22) |
Mar
(7) |
Apr
(8) |
May
(8) |
Jun
(11) |
Jul
(2) |
Aug
|
Sep
(5) |
Oct
(31) |
Nov
(23) |
Dec
(3) |
2002 |
Jan
(1) |
Feb
(17) |
Mar
(10) |
Apr
(3) |
May
(1) |
Jun
(2) |
Jul
|
Aug
|
Sep
(11) |
Oct
(5) |
Nov
(21) |
Dec
(20) |
2003 |
Jan
(27) |
Feb
(13) |
Mar
(20) |
Apr
(11) |
May
(12) |
Jun
(7) |
Jul
(16) |
Aug
(21) |
Sep
(9) |
Oct
(28) |
Nov
(24) |
Dec
(30) |
2004 |
Jan
(31) |
Feb
(5) |
Mar
|
Apr
(8) |
May
(12) |
Jun
(7) |
Jul
(13) |
Aug
(12) |
Sep
(2) |
Oct
(14) |
Nov
(42) |
Dec
(14) |
2005 |
Jan
|
Feb
|
Mar
(20) |
Apr
(17) |
May
(9) |
Jun
|
Jul
(7) |
Aug
(3) |
Sep
(17) |
Oct
(14) |
Nov
(9) |
Dec
|
2006 |
Jan
|
Feb
|
Mar
(13) |
Apr
(2) |
May
(46) |
Jun
(2) |
Jul
(20) |
Aug
(26) |
Sep
(31) |
Oct
(5) |
Nov
(9) |
Dec
(13) |
2007 |
Jan
(24) |
Feb
(22) |
Mar
(13) |
Apr
(25) |
May
(25) |
Jun
(9) |
Jul
(20) |
Aug
(9) |
Sep
(26) |
Oct
(3) |
Nov
(4) |
Dec
(3) |
2008 |
Jan
(92) |
Feb
(35) |
Mar
(39) |
Apr
(15) |
May
|
Jun
|
Jul
(18) |
Aug
(5) |
Sep
(5) |
Oct
(7) |
Nov
(10) |
Dec
(27) |
2009 |
Jan
(35) |
Feb
(34) |
Mar
(13) |
Apr
(9) |
May
(18) |
Jun
(9) |
Jul
(15) |
Aug
(13) |
Sep
(64) |
Oct
(7) |
Nov
(43) |
Dec
|
2010 |
Jan
(75) |
Feb
(22) |
Mar
(44) |
Apr
(34) |
May
(47) |
Jun
(77) |
Jul
(28) |
Aug
(7) |
Sep
(45) |
Oct
(1) |
Nov
(19) |
Dec
(7) |
2011 |
Jan
(14) |
Feb
|
Mar
(6) |
Apr
(12) |
May
(19) |
Jun
(3) |
Jul
(8) |
Aug
(4) |
Sep
(3) |
Oct
(21) |
Nov
(11) |
Dec
(4) |
2012 |
Jan
(2) |
Feb
(9) |
Mar
|
Apr
(1) |
May
(2) |
Jun
|
Jul
(1) |
Aug
(5) |
Sep
(5) |
Oct
(1) |
Nov
(18) |
Dec
(2) |
2013 |
Jan
(15) |
Feb
(16) |
Mar
(8) |
Apr
(5) |
May
|
Jun
(1) |
Jul
(17) |
Aug
(3) |
Sep
(17) |
Oct
(43) |
Nov
(25) |
Dec
(9) |
2014 |
Jan
(4) |
Feb
(8) |
Mar
(20) |
Apr
(14) |
May
(49) |
Jun
(1) |
Jul
|
Aug
(18) |
Sep
(2) |
Oct
(1) |
Nov
(22) |
Dec
(3) |
2015 |
Jan
(41) |
Feb
(2) |
Mar
(34) |
Apr
(30) |
May
(14) |
Jun
(17) |
Jul
(29) |
Aug
(3) |
Sep
(3) |
Oct
(1) |
Nov
(7) |
Dec
(4) |
2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
(4) |
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
(25) |
Oct
(9) |
Nov
(14) |
Dec
(13) |
2017 |
Jan
(11) |
Feb
(8) |
Mar
(12) |
Apr
(4) |
May
(25) |
Jun
(2) |
Jul
|
Aug
(5) |
Sep
(10) |
Oct
(25) |
Nov
|
Dec
(6) |
2018 |
Jan
(18) |
Feb
(6) |
Mar
(6) |
Apr
(1) |
May
(7) |
Jun
(13) |
Jul
(8) |
Aug
|
Sep
(5) |
Oct
(2) |
Nov
(17) |
Dec
(3) |
2019 |
Jan
(11) |
Feb
(4) |
Mar
(13) |
Apr
(19) |
May
(1) |
Jun
(2) |
Jul
(8) |
Aug
(4) |
Sep
(32) |
Oct
(51) |
Nov
(1) |
Dec
(9) |
2020 |
Jan
(9) |
Feb
(6) |
Mar
|
Apr
|
May
(3) |
Jun
(2) |
Jul
(5) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(7) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(3) |
Dec
|
2022 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2025 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: <jc...@fe...> - 2003-02-03 16:33:18
|
On Friday 31 January 2003 13:52, Don Spong wrote: | (This is a re-send of an earlier message that was blocked from the | list for being too large): I've run into problems with installing | plplot-5.2.0 on an IBM RS6000 workstation running under AIX 4.3.3.0. | At the end of the make step, I get the following errors. I've also | attached a text file that has a listing of the configure step. The decoded binhex attachment that Don sent: >configure --prefix=3D/home/spongda/plplot-5.2.0 No defaults file found, performing full configure. =2E.. checking build system type... powerpc-ibm-aix4.3.3.0 =2E.. checking whether the linker (/bin/ld) supports shared libraries... yes checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... no checking dynamic linker characteristics... aix4.3.3.0 ld.so checking if libtool supports shared libraries... yes <------------------ checking whether to build shared libraries... yes checking whether to build static libraries... no <---------this is odd! =2E.. command: configure --no-reexec=20 --prefix=3D/home/spongda/plplot-5.2.0 system: powerpc-ibm-aix4.3.3.0 prefix: /home/spongda/plplot-5.2.0 CC: gcc=20 CXX: g++=20 F77: g77=20 LIB_TAG: =20 devices: dg300 hp7470 hp7580 lj_hpgl imp ljii ljiip null pbm=20 plmeta ps psc pstex xterm tek4010 tek4107 mskermit versaterm vlt conex=20 tek4 010f tek4107f tk xfig xwin Available device drivers static: dg300.lo hpgl.lo impress.lo ljii.lo ljiip.lo null.lo=20 pbm.lo plmeta.lo ps.lo pstex.lo tek.lo tk.lo xfig.lo xwin.lo dynamic: =20 with_shlib: yes with_double: no with_debug: no with_opt: no with_warn: no with_profile: no with_gcc: no with_rpath: yes with_freetype: no enable_xwin: yes enable_tcl: yes enable_tk: yes enable_itcl: no enable_cxx: yes enable_python: no enable_f77: yes enable_java: no enable_octave: no enable_gnome: no enable_tkwin: no Don, at this point you have probably already configured plplot with=20 --enable-dyndrivers, if not try it because your system is supported by=20 libtool and the building of dynamic drivers and shared libraries most=20 be OK. Thanks, Joao | | -Thanks, Don |
From: Alan W. I. <ir...@be...> - 2003-02-01 20:46:59
|
The reason for the problem has been found and the fix is in CVS. It turns out the fatal combination is static drivers and --with-double on *all* platforms. (We gave the mistaken impression before this problem only occurred on some platforms.) Thus, for any platform a workaround is to specify --enable-dyndrivers. An alternative workaround is to avoid specifying --with-double. Its a Boolean OR of those two workarounds. Thus, the combination of --enable-dyndrivers and --with-double builds fine since the first workaround condition is fulfilled. Similarly, default options (nothing specified about the kind of drivers or precision) build fine since the second condition is fulfilled. By the way, there has been quite a substantial move from PLplot-5.1.0 to PLplot-5.2.0. There have been something like 3000 downloads so far. Apparently, relatively few of those users have run into the above problem (presumably because it is rare to demand static drivers and double precision at the same time). Nevertheless, once the fix for the problem has been thoroughly tested on a wide variety of platforms it will become part of our next release of PLplot. Alan __________________________ Alan W. Irwin email: ir...@be... phone: 250-727-2902 Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the Canadian Centre for Climate Modelling and Analysis (www.cccma.bc.ec.gc.ca) and the PLplot scientific plotting software package (plplot.org). __________________________ Linux-powered Science __________________________ |
From: Alan W. I. <ir...@be...> - 2003-01-31 17:12:07
|
On Fri, 31 Jan 2003, Don Spong wrote: > (This is a re-send of an earlier message that was blocked from the > list for being too large): I've run into problems with installing > plplot-5.2.0 on an IBM RS6000 workstation running under AIX 4.3.3.0. > At the end of the make step, I get the following errors. I've also > attached a text file that has a listing of the configure step. I am sorry, Don, but I don't have time/energy to figure out that Mac text compression on your attachment. (gzip or bzip2 would be straightforward for me to interpret.) However, your error messages on the make attempt all seem to do with the device drivers. We have had a lot of bad reports from others about the default static drivers on some platforms so if you haven't done so already, could you please try the --enable-dyndrivers configure option to see if that solves the problem? If that doesn't solve it, please send me privately the complete configure and make output as uncompressed (or gzip or bzip2) text attachments. Alan __________________________ Alan W. Irwin email: ir...@be... phone: 250-727-2902 Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the Canadian Centre for Climate Modelling and Analysis (www.cccma.bc.ec.gc.ca) and the PLplot scientific plotting software package (plplot.org). __________________________ Linux-powered Science __________________________ |
From: <jc...@fe...> - 2003-01-29 19:15:29
|
On Wednesday 29 January 2003 01:47, iwan maximus cornelius wrote: | Dear all, | | I have recently installed | plplot under redhat 7.2 on an | i386 architecture. Everything | installed AOK however when | I try to execute any of the | example programs I get the | following error: | | *** PLPLOT ERROR *** | Unable to open or allocate | memory for font file | Program aborted This error happens when the font file is not found. In RH-8.0, if I remove the fonts, I get the same error: > ls ~/test/lib/plplot5.2.0/data/ cglobe.map globe.map plstnd5.fnt plxtnd5.fnt usaglobe.map usa.map (The fonts are the files with the extension .fnt, and I installed plplot=20 in ~/test) > mv ~/test/lib/plplot5.2.0/data ~/test/lib/plplot5.2.0/data- > ./x01c -dev xwin Plplot library version: 5.2.0 *** PLPLOT ERROR *** Unable to open or allocate memory for font file Program aborted Thus the question is: you are trying to run an example without first=20 installing plplot right? You can't. You *have* to install before=20 running any example. Joao | | If anybody can provide | information I'd appreciate it, | | Thanks in advance, | Iwan Cornelius | | | | | ------------------------------------------------------- | This SF.NET email is sponsored by: | SourceForge Enterprise Edition + IBM + LinuxWorld =3D Something 2 See! | http://www.vasoftware.com | _______________________________________________ | Plplot-general mailing list | Plp...@li... | https://lists.sourceforge.net/lists/listinfo/plplot-general |
From: Alan W. I. <ir...@be...> - 2003-01-29 02:21:53
|
On Wed, 29 Jan 2003, iwan maximus cornelius wrote: > Dear all, > > I have recently installed > plplot under redhat 7.2 on an > i386 architecture. Everything > installed AOK however when > I try to execute any of the > example programs I get the > following error: > > *** PLPLOT ERROR *** > Unable to open or allocate > memory for font file > Program aborted > > If anybody can provide > information I'd appreciate it. It sounds like the fonts aren't installed correctly on your system, but we'll need some more information from you to get to the bottom of this. What version of PLplot? If it's an rpm, what version of that? I have had good luck with the recently released plplot-5.2.0.tar.gz with RH 7.3, and Joao has had good luck also with that tarball for RH 8.0. I see no reason why it shouldn't work with RH 7.2 but we haven't tried it with that distribution. Alan __________________________ Alan W. Irwin email: ir...@be... phone: 250-727-2902 Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the Canadian Centre for Climate Modelling and Analysis (www.cccma.bc.ec.gc.ca) and the PLplot scientific plotting software package (plplot.org). __________________________ Linux-powered Science __________________________ |
From: Joao C. <jc...@fe...> - 2003-01-29 01:48:53
|
On Tuesday 28 January 2003 23:59, Doug Hunt wrote: > Hi all: I have been using plplot 5.1 for some time. I just downloaded > > 5.2.0 and ran into this: > > ./configure --with-double --prefix=3D/ops/tools > > make > > ... > > gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../bindings/tcl > -I../bindings/tk -I../bindings//tk-x-plat -I/usr/X11R6/include -g -O2 > -MT matrixInit.lo -MD -MP -MF .deps/matrixInit.Tpo -c > ../bindings/tcl/matrixInit.c -o matrixInit.o >/dev/null 2>&1 > mv -f .libs/matrixInit.lo matrixInit.lo > make[1]: *** No rule to make target `dg300d.lo', needed by > `libplplotdrv.la'. Stop. > make[1]: Leaving directory `/home/huntd/src/plplot-5.2.0/drivers' > make: *** [all-recursive] Error 1 Hi, Doug I confirm your report on my SuSE-8.1. We are changing our configuration stuff, using autotools/libtool, hopping= to=20 reach a more broad range of platforms, and it looks like there are still = some=20 problems left. I have tested the current release in a variety of platforms, RH-8.0, SuSE= -8.1=20 and OSF1 and other developers in Debian-?, RH-7.2 and other platforms, bu= t it=20 looks like that we didn't test all possibilities. So I advise you (and others) to configure using --enable-dyndrivers. In t= he=20 above systems that I tested I always used "--enable-dyndrivers=20 --disable-static". I always use the disable-static to save compile time = and=20 disk space, but that depends on your platform. I have just now configured and make plplot-5.2.0 with=20 ./configure --with-double --prefix=3D/usr/local/test/ \ --enable-dyndrivers and it succeeded in my SuSE-8.1 system. In case your *make* (not configure) fails with the last few lines saying: Making all in include make[1]: Entering directory `/home/jcard/tmp/plplot-5.2.0/include' cd .. && /bin/sh /home/jcard/tmp/plplot-5.2.0/missing --run autoheader WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot' WARNING: and `config.h.top', to define templates for `config.h.in' (... other warnings) please type the command: touch include/plDevs.h.in and restart the make (this has just happened to me after the first=20 configure/make fails and I issued the second configure/make). Thanks for reporting this and other problems that you might find, it is t= hanks=20 to detailed reports, including the platform and configure command used, = that=20 we can manage to solve problems and improve PLplot. > > Also, I have developed a driver under 5.1, but I can't seem to figure > out how to get it to work under 5.2. I keep running into GNU > automake/autoconf/aclocal errors. > I gather the old process of modifying cf/configure.in and running > autoconf no longer works. Yes, you are right. The best advise I can give to you is to look how othe= r=20 drivers are currently configured. Don't look at the cf directory, it is s= till=20 there because historical reasons :), look at the *.in files in both the t= op=20 and drivers directory. Joao > Is there any doc for how to do this under 5.2? The instructions in > drivers/README.drivers seems out of date. > > Any ideas on these problems? > > Thanks much! > > Doug Hunt > > P.S: > > $ uname -a > Linux pegasus.cosmic.ucar.edu 2.4.7-10 #1 Thu Sep 6 17:27:27 EDT 2001 > i686 unknown > $ cat /etc/redhat-release > Red Hat Linux release 7.2 (Enigma) > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld =3D Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Plplot-devel mailing list > Plp...@li... > https://lists.sourceforge.net/lists/listinfo/plplot-devel |
From: iwan m. c. <ic...@uo...> - 2003-01-29 01:48:22
|
Dear all, I have recently installed plplot under redhat 7.2 on an i386 architecture. Everything installed AOK however when I try to execute any of the example programs I get the following error: *** PLPLOT ERROR *** Unable to open or allocate memory for font file Program aborted If anybody can provide information I'd appreciate it, Thanks in advance, Iwan Cornelius |
From: Alan W. I. <ir...@be...> - 2003-01-28 07:20:54
|
Soon after the release of 5.2.0 last week we found PLplot-5.2.0 would not build properly on some systems. Debian woody and RH7.3 were okay, but RH 8.0 (and other systems) were not. The workaround (just verified today) is simple; execute 'touch include/plDevs.h.in' before executing the normal configure; make; make install. Since this is such a simple change I have just uploaded a new plplot-5.2.0.tar.gz (and associated RH 7.3 rpm's) with a recent date for include/plDevs.h.in that will insure that this build problem does not occur. Thus, those who download PLplot-5.2.0 from now on should not encounter these problems. The new binary rpm should not be appreciably different from the old version except for the build date. The new src rpm carries within it the revised PLplot-5.2.0 tarball. A summary (see plplot-devel for details) of what causes this problem is cruft left over from our old configuration system is confusing the new configuration system (and yours truly!). The net result is the contents of include/plDevs.h.in are correct, but the file date is older than other critical files. Thus, when make is executed on user's systems an incorrect attempt is made to update this file using autoheader, and on some systems the build is stopped by inconsistencies between the user's autoheader and the autotools used to build the PLplot-5.2.0 tarball. The touch workaround mentioned above completely takes care of this problem so the build should proceed to completion with no reference to autoheaders or any other autotool. Of course, the fundamental solution to the date problem for include/plDevs.h.in is to get rid of the cruft in our configuration system, and we are working toward that goal. We hope to bring out PLplot-5.2.1 on a time scale of weeks with this streamlining of the configuration system completed. However, the differences will probably be transparent for users compared to the PLplot-5.2.0 that was just released for the second time with new file date for include/plDevs.h.in. Keep those 5.2.0 reports coming! Alan W. Irwin for the PLplot developers. __________________________ Alan W. Irwin email: ir...@be... phone: 250-727-2902 Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the Canadian Centre for Climate Modelling and Analysis (www.cccma.bc.ec.gc.ca) and the PLplot scientific plotting software package (plplot.org). __________________________ Linux-powered Science __________________________ |
From: Alan W. I. <ir...@be...> - 2003-01-22 23:48:04
|
On Wed, 22 Jan 2003, Joao Cardoso wrote: > I enclose a step-by-step log of my last attempt. Basicaly I can't run > bootstrap.sh, i.e., the autoconf step fails: > > > ./bootstrap.sh > configure.in:219: error: popdef: undefined macro: HTML > configure.in:217: FILE_EXT is expanded from... > configure.in:219: the top level > > > aclocal > > automake --add-missing --gnu Makefile src/Makefile bin/Makefile > > autoconf > configure.in:219: error: popdef: undefined macro: HTML > configure.in:217: FILE_EXT is expanded from... > configure.in:219: the top level > > Clearly my autotools versions are capable of running plplot's top level > bootstrap.sh. Thanks for this report, Joao. Recall, I built the documentation with the mixed autotools version from Debian and uploaded it to SF, and only switched to the pure latest versions of autotools for the final tarball release (which does not build the documentation, instead it just downloads it from SF). Thus, the peculiar release process for PLplot-5.2.0 did not actually test whether the pure latest autotools will generate the documentation from the DocBook-XML source. Therefore, in light of your report I just tried that test, and I confirm the error you have found. I will put fixing this autotools version issue on my ToDo list for the next time I update the documentation. I should emphasize for the PLplot users on this list, that this issue does not affect ordinary users who can just download or view the generated documentation (html, postscript, dvi, pdf, info, and man forms) from http://plplot.sourceforge.net/resources/docbook-manual/. Alan __________________________ Alan W. Irwin email: ir...@be... phone: 250-727-2902 Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the Canadian Centre for Climate Modelling and Analysis (www.cccma.bc.ec.gc.ca) and the PLplot scientific plotting software package (plplot.org). __________________________ Linux-powered Science __________________________ |
From: Joao C. <jc...@fe...> - 2003-01-22 19:52:12
|
On Tuesday 21 January 2003 22:00, Alan W. Irwin wrote: > On Tue, 21 Jan 2003, [iso-8859-1] Jo=E3o Cardoso wrote: > > I still can't generate the docs! > > We have always been able to generate documentation using Debian. In Red= Hat > 6.2 days it was difficult to generate the documentation on that system,= but > Maurice still managed to do it. I think docbook support is now much be= tter > for modern distributions of RedHat (and SuSe?), but I just haven't had = time > to try it. Joao, if you feel this is urgent, why don't you give it a tr= y on > your system now to see how far you can get following the directions in > doc/docbook/README.developers? You might be surprised how easy it is. > > I do intend to look at this issue for RH7.3 within the next month or so= , > but I would be quite happy if someone else beats me to it for that > distribution. After I or somebody else are successful with RH7.3, we ca= n > help Joao with any of his problems with building the documentation on S= uSe > (if such problems still exist). I enclose a step-by-step log of my last attempt. Basicaly I can't run=20 bootstrap.sh, i.e., the autoconf step fails: > ./bootstrap.sh=20 =09configure.in:219: error: popdef: undefined macro: HTML =09configure.in:217: FILE_EXT is expanded from... =09configure.in:219: the top level > aclocal > automake --add-missing --gnu Makefile src/Makefile bin/Makefile > autoconf =09configure.in:219: error: popdef: undefined macro: HTML =09configure.in:217: FILE_EXT is expanded from... =09configure.in:219: the top level Clearly my autotools versions are capable of running plplot's top level=20 bootstrap.sh Joao > > Alan > __________________________ > Alan W. Irwin > email: ir...@be... > phone: 250-727-2902 > > Astronomical research affiliation with Department of Physics and Astron= omy, > University of Victoria (astrowww.phys.uvic.ca). > > Programming affiliations with the Canadian Centre for Climate Modelling= and > Analysis (www.cccma.bc.ec.gc.ca) and the PLplot scientific plotting > software package (plplot.org). > > __________________________ > > Linux-powered Science > __________________________ > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Scholarships for Techies! > Can't afford IT training? All 2003 ictp students receive scholarships. > Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. > www.ictp.com/training/sourceforge.asp > _______________________________________________ > Plplot-general mailing list > Plp...@li... > https://lists.sourceforge.net/lists/listinfo/plplot-general |
From: Rafael L. <lab...@ps...> - 2003-01-22 18:38:39
|
* Alan W. Irwin <ir...@be...> [2003-01-21 21:04]: > First, the script to convert from api.xml to plplot.h should include all > the function and argument documentation in the generated plplot.h in a > standard form. This would help guide developers in any future changes to > plplot.h if they wanted to fully document their new API. Also, when any > documenter runs that script they can carefully check that the resulting > plplot.h is consistent with the original (except possibly for improvements > in the documentation and whitespace changes). That script should not be too complicate to write. I already had something working for the perl5 bindings: bindings/perl5/api2bind.pl > Second, a script should be developed (Rafael had something like this in > rudimentary form years ago) to translate a single API description from > plplot.h in standard form (i.e, including full documentation) to api.xml. > If the developer has chosen not to put in documentation in plplot.h in the > standard form, then some provision should be made to put in the phrase > "NEEDS DOCUMENTATION" in the resulting api.xml fragment. With such a > script, then any developer change to plplot.h can quickly be put into > api.xml with a simple cut and paste operation. As far as I can remember, I never wrote any script to convert plplot.h into XML. That should not be too difficult to write, although one has to write a parser for C code... > Of course all this discussion is moot without the two scripts. > > Rafael if you could make those two scripts, [...] That an insteresting project, but I cannot commit myself to do it in the forseeable future. -- Rafael |
From: Rafael L. <lab...@ps...> - 2003-01-22 18:28:22
|
* Alan W. Irwin <ir...@be...> [2003-01-21 14:00]: > On Tue, 21 Jan 2003, [iso-8859-1] João Cardoso wrote: > > > I still can't generate the docs! > > We have always been able to generate documentation using Debian. In RedHat > 6.2 days it was difficult to generate the documentation on that system, but > Maurice still managed to do it. I think docbook support is now much better > for modern distributions of RedHat (and SuSe?), but I just haven't had time > to try it. Joao, if you feel this is urgent, why don't you give it a try on > your system now to see how far you can get following the directions in > doc/docbook/README.developers? You might be surprised how easy it is. I am sure thigs will improve in the future, as DocBook (and XML) matures and becomes more standardized. Hopefully, when we will migrate from the present DSSSL scheme to a more modern XSLT one, things will be even better. -- Rafael |
From: Alan W. I. <ir...@be...> - 2003-01-22 08:06:10
|
On Wed, 22 Jan 2003, Valerij Pipin wrote: > On Wednesday 22 January 2003 13:24, Alan W. Irwin wrote: > > Was this the only change you had to make to build the documentation on > > Sisyphus? > Yes it was. Excellent! I hope many others will be able to do the same so they will be able to check any changes to the documentation that they would like to submit. > But I don't like this method. Is it possible to change the > configure script a little or I just have to add rigth path the perl's path > variable? I am not sure, but I hope Rafael (or some other perl expert here) has an answer. > These examples are really cool.... I agree, and I should emphasize that Joao should get the credit for those cool examples. > > Do you know that AbSoft fortran is now > shipped with plplot? I saw that in an advertisement, but as far as I know AbSoft has never gotten in touch with any member of the PLplot team so there is no interaction, yet. > My congratulations to plplot team. Thanks! Alan __________________________ Alan W. Irwin email: ir...@be... phone: 250-727-2902 Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the Canadian Centre for Climate Modelling and Analysis (www.cccma.bc.ec.gc.ca) and the PLplot scientific plotting software package (plplot.org). __________________________ Linux-powered Science __________________________ |
From: Valerij P. <vp...@ir...> - 2003-01-22 06:04:33
|
On Wednesday 22 January 2003 13:24, Alan W. Irwin wrote: > On Wed, 22 Jan 2003, Valerij Pipin wrote: > > Hello, > > > > I've build succefully rpms files for the plplot-5.2.0 for the ALTLinux > > Sisyphus distribution. Now there was no problem with building octave > > (version 2.1.40) module and rpath problem as well. > > Thanks for the good report. > > > I have the similar problem with making docbook as Jo=C3=A3o Cardoso > > reported. The configure script did not find DOM.pm > > which is provided by via perl-XML-Sablotron package. The problem was due > > to the fact that in Sisyphus this package is in > > /usr/lib/perl5/vendor_perl/i386-linux/XML/Sablotron, so I copied the fi= le > > to the needed place. I think the requerement of the additional xml stuff > > (like XML-Sablotron) should be mentioned somewhere in readme. > > The problem is that each distribution may do such things differently and > change from one version to the next. Thus, it may be difficult to docume= nt > it all although the problem should get smaller as each distribution striv= es > toward LSB compliance. > > Was this the only change you had to make to build the documentation on > Sisyphus?=20 Yes it was. But I don't like this method. Is it possible to change the=20 configure script a little or I just have to add rigth path the perl's path= =20 variable? > If so, that is much simpler/easier than the modifications to RH > 6.2 DocBook that had to be done to build the documentation way back when > and gives me some hope that RH 7.3 (and SuSe?) will be easy as well. > > > I rebuild the yplot with for new version. It works fine for me. > > Thanks for that good report as well. When time permits (probably a month > or so from now) I will port the new PLplot API additions to yplot so you > can enjoy the updated examples 8 and 11 there as well. Once those yplot A= PI > additions are made, I will bring out a new release of yplot. These examples are really cool, I looked them with python. Do you know that AbSoft fortran is now=20 shipped with plplot?=20 My congratulations to plplot team rgds, v |
From: Alan W. I. <ir...@be...> - 2003-01-22 05:25:20
|
On Wed, 22 Jan 2003, Valerij Pipin wrote: > Hello, > > I've build succefully rpms files for the plplot-5.2.0 for the ALTLinux > Sisyphus distribution. Now there was no problem with building octave (ver= sion > 2.1.40) module and rpath problem as well. Thanks for the good report. > > I have the similar problem with making docbook as Jo=C3=A3o Cardoso rep= orted. > The configure script did not find DOM.pm > which is provided by via perl-XML-Sablotron package. The problem was due = to > the fact that in Sisyphus this package is in > /usr/lib/perl5/vendor_perl/i386-linux/XML/Sablotron, so I copied the file= to > the needed place. I think the requerement of the additional xml stuff (li= ke > XML-Sablotron) should be mentioned somewhere in readme. The problem is that each distribution may do such things differently and change from one version to the next. Thus, it may be difficult to document it all although the problem should get smaller as each distribution strives toward LSB compliance. Was this the only change you had to make to build the documentation on Sisyphus? If so, that is much simpler/easier than the modifications to RH 6.2 DocBook that had to be done to build the documentation way back when an= d gives me some hope that RH 7.3 (and SuSe?) will be easy as well. > > I rebuild the yplot with for new version. It works fine for me. Thanks for that good report as well. When time permits (probably a month o= r so from now) I will port the new PLplot API additions to yplot so you can enjoy the updated examples 8 and 11 there as well. Once those yplot API additions are made, I will bring out a new release of yplot. Alan __________________________ Alan W. Irwin email: ir...@be... phone: 250-727-2902 Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the Canadian Centre for Climate Modelling and Analysis (www.cccma.bc.ec.gc.ca) and the PLplot scientific plotting softwar= e package (plplot.org). __________________________ Linux-powered Science __________________________ |
From: Alan W. I. <ir...@be...> - 2003-01-22 05:05:35
|
On Wed, 22 Jan 2003, Joao Cardoso wrote: > That means that when I need to add/change something in plplot.h, because I'm > *developing*, then I need to change api.xml..... Joao, you do have *one* legitimate point there which I will now discuss. Putting in all the xml boilerplate in api.xml does take quite an effort if done by hand. So here is the compromise that I propose instead. It means continued parallel development of api.xml and plplot.h, but good scripts can substantially reduce the maintenance cost of this parallel development. First, the script to convert from api.xml to plplot.h should include all the function and argument documentation in the generated plplot.h in a standard form. This would help guide developers in any future changes to plplot.h if they wanted to fully document their new API. Also, when any documenter runs that script they can carefully check that the resulting plplot.h is consistent with the original (except possibly for improvements in the documentation and whitespace changes). Second, a script should be developed (Rafael had something like this in rudimentary form years ago) to translate a single API description from plplot.h in standard form (i.e, including full documentation) to api.xml. If the developer has chosen not to put in documentation in plplot.h in the standard form, then some provision should be made to put in the phrase "NEEDS DOCUMENTATION" in the resulting api.xml fragment. With such a script, then any developer change to plplot.h can quickly be put into api.xml with a simple cut and paste operation. Here is how I think it would work in practice. After a developer has iterated on a change to plplot.h and finalized it, then he (or somebody else if the developer does not want to document his API) has the option to run the second script on the changed fragment and do the cut and paste to api.xml. Then follow with the first script to confirm plplot.h is consistent with api.xml. Of course all this discussion is moot without the two scripts. Rafael if you could make those two scripts, then they would be a big help to me in my forthcoming efforts to bring api.xml into consistency with plplot.h. Part of the reason why I have fallen behind in keeping api.xml up to date is I don't have such scripts. Also, if such easy-to-use scripts were available, I believe developers would be much more willing to document their API changes which would take additional documentation load off me. Alan __________________________ Alan W. Irwin email: ir...@be... phone: 250-727-2902 Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the Canadian Centre for Climate Modelling and Analysis (www.cccma.bc.ec.gc.ca) and the PLplot scientific plotting software package (plplot.org). __________________________ Linux-powered Science __________________________ |
From: Valerij P. <vp...@ir...> - 2003-01-22 02:27:20
|
Hello, I've build succefully rpms files for the plplot-5.2.0 for the ALTLinux=20 Sisyphus distribution. Now there was no problem with building octave (versi= on=20 2.1.40) module and rpath problem as well.=20 I have the similar problem with making docbook as Jo=C3=A3o Cardoso repor= ted. =20 The configure script did not find DOM.pm which is provided by via perl-XML-Sablotron package. The problem was due to= =20 the fact that in Sisyphus this package is in=20 /usr/lib/perl5/vendor_perl/i386-linux/XML/Sablotron, so I copied the file t= o=20 the needed place. I think the requerement of the additional xml stuff (like= =20 XML-Sablotron) should be mentioned somewhere in readme. I rebuild the yplot with for new version. It works fine for me.=20 rgds, v |
From: Joao C. <jc...@fe...> - 2003-01-22 00:16:07
|
On Tuesday 21 January 2003 22:00, Alan W. Irwin wrote: > On Tue, 21 Jan 2003, [iso-8859-1] Jo=E3o Cardoso wrote: > > I still can't generate the docs! > > We have always been able to generate documentation using Debian. In Red= Hat > 6.2 days it was difficult to generate the documentation on that system,= but > Maurice still managed to do it. I think docbook support is now much be= tter > for modern distributions of RedHat (and SuSe?), but I just haven't had = time > to try it. Joao, if you feel this is urgent, why don't you give it a tr= y on > your system now to see how far you can get following the directions in > doc/docbook/README.developers? You might be surprised how easy it is. I did try it several times. Not very engaged, but I tried. Following the=20 instructions doesn't work. Joao > > I do intend to look at this issue for RH7.3 within the next month or so= , > but I would be quite happy if someone else beats me to it for that > distribution. After I or somebody else are successful with RH7.3, we ca= n > help Joao with any of his problems with building the documentation on S= uSe > (if such problems still exist). > > Alan > __________________________ > Alan W. Irwin > email: ir...@be... > phone: 250-727-2902 > > Astronomical research affiliation with Department of Physics and Astron= omy, > University of Victoria (astrowww.phys.uvic.ca). > > Programming affiliations with the Canadian Centre for Climate Modelling= and > Analysis (www.cccma.bc.ec.gc.ca) and the PLplot scientific plotting > software package (plplot.org). > > __________________________ > > Linux-powered Science > __________________________ > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Scholarships for Techies! > Can't afford IT training? All 2003 ictp students receive scholarships. > Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. > www.ictp.com/training/sourceforge.asp > _______________________________________________ > Plplot-general mailing list > Plp...@li... > https://lists.sourceforge.net/lists/listinfo/plplot-general |
From: Joao C. <jc...@fe...> - 2003-01-22 00:12:15
|
On Tuesday 21 January 2003 21:54, Alan W. Irwin wrote: > I will try to comment on what Joao and Rafael have said. > > On Tue, 21 Jan 2003, [iso-8859-1] Jo=E3o Cardoso wrote: > > On Tuesday 21 January 2003 20:06, Rafael Laboissiere wrote: > > > > Hi Rafael! > > > > | * Alan W. Irwin <ir...@be...> [2003-01-21 10:23]: > > | > On Mon, 20 Jan 2003, Robert Schwebel wrote: > > | > > What's the state of the Perl/PDL interface? > > | > > > | > I don't know about PDL since that is an independent effort (see > > | > Doug Hunt's messages to this list right after PLplot-5.1.0 was > > | > released last year). > > | > > | Well, my original Perl bindings code had some limited support to PD= L. > > | However, I think that Doug's approach should be superior than mine. > > | > > | > We do have a rudimentary perl interface as part of generic PLplot= , > > | > but that is unsupported at this time because its developer ran ou= t > > | > of time to work on it. > > | > > | (That is me. I am still unable to participate to the PLplot effort= =2E > > | Too many things on the way.) > > | > > | > Personally, I think we should abandon that approach (which depend= ed > > | > on parsing the API from our DocBook API chapter) and go with swig > > | > instead. > > | > > | Well, my approach combined both parsing the XML source of the API > > | _and_ usign swig (see bindings/perl5/README). > > OOPS. Sorry I missed that, Rafael. That immediately gives me much mor= e > interest in the current perl interface. > > > | I do not think that > > | parsing the XML source is a bad idea, provided that the plplot.h is > > | also automatically generated. It is unacceptable to have two sourc= es > > | of the same information being maintained in parallel. > > Rafael, I agree that one source for our API would be better, but it wil= l > take some effort, and we have lived with *many* parallel versions of ou= r > API descriptions for a long time. So it is the old tradeoff between a > constant, maintenance problem that makes a steady drain on our time/eff= ort, > or doing something much better which requires a lot more immediate > time/effort but pays off later in reducing the maintenance required.=20 > "Short term pain for long-term gain". > > Here is a summary of the current parallel API descriptions. We have the > docbook chapter describing the API, plplot.h, two separate files descri= bing > the API for both java and python, and files describing the API for fort= ran > and tcl as well. For the java and python case, the two files are almos= t > identical, but they *must* differ slightly because the current java > interface has cruder support of the call-back functions. Once that is > sorted out, the two files could be merged together, but not yet. Also, > these two files differ quite a bit from plplot.h to signal the swig > typedefs when something special has to be done with arguments (such as > dropping redundant dimensions from argument lists). > > > In that case, let the documentation be generated from the code and no= t > > the other way around! And it's easier to maintain plplot.h than > > api.xml. > > Joao, that's because api.xml has extra information such as detailed > documentation of each argument far beyond the argument types and minima= l > documentation that plplot.h has at the moment. > > Therefore, since doc/docbook/src/api.xml has the most documentation > information (by far) in an easily parsable form , I agree with Rafael t= hat > this file should be the ultimate source of all other descriptions of ou= r > API. To implement that, scripts need to be developed to generate > include/plplot.h, bindings/python/plplotcapi, bindings/java/plplotcapi, > bindings/tcl/plapi.tpl, and the equivalent API description file(s) for > fortran. I have put such scripts in the rough order from highest to lo= west > priority. From Rafael's comments above , it also looks like a script h= as > already been written to generate the required swig interface file for p= erl, > but I imagine there is some more work to do on that as well. > > Rafael, generating include/plplot.h from doc/docbook/src/api.xml might = be > the type of small project that might interest you. How about it? That means that when I need to add/change something in plplot.h, because = I'm=20 *developing*, then I need to change api.xml, run the plplot.h building=20 scripts, make, eventually make install, and then restart from the beginin= g=20 several times. Is this the development model we want for plplot? I will b= e=20 out. Joao > > Alan > __________________________ > Alan W. Irwin > email: ir...@be... > phone: 250-727-2902 > > Astronomical research affiliation with Department of Physics and Astron= omy, > University of Victoria (astrowww.phys.uvic.ca). > > Programming affiliations with the Canadian Centre for Climate Modelling= and > Analysis (www.cccma.bc.ec.gc.ca) and the PLplot scientific plotting > software package (plplot.org). > > __________________________ > > Linux-powered Science > __________________________ > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Scholarships for Techies! > Can't afford IT training? All 2003 ictp students receive scholarships. > Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. > www.ictp.com/training/sourceforge.asp > _______________________________________________ > Plplot-general mailing list > Plp...@li... > https://lists.sourceforge.net/lists/listinfo/plplot-general |
From: Alan W. I. <ir...@be...> - 2003-01-21 22:01:24
|
On Tue, 21 Jan 2003, [iso-8859-1] Jo=E3o Cardoso wrote: > I still can't generate the docs! We have always been able to generate documentation using Debian. In RedHat 6.2 days it was difficult to generate the documentation on that system, but Maurice still managed to do it. I think docbook support is now much better for modern distributions of RedHat (and SuSe?), but I just haven't had time to try it. Joao, if you feel this is urgent, why don't you give it a try on your system now to see how far you can get following the directions in doc/docbook/README.developers? You might be surprised how easy it is. I do intend to look at this issue for RH7.3 within the next month or so, bu= t I would be quite happy if someone else beats me to it for that distribution= =2E After I or somebody else are successful with RH7.3, we can help Joao with any of his problems with building the documentation on SuSe (if such problems still exist). Alan __________________________ Alan W. Irwin email: ir...@be... phone: 250-727-2902 Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the Canadian Centre for Climate Modelling and Analysis (www.cccma.bc.ec.gc.ca) and the PLplot scientific plotting softwar= e package (plplot.org). __________________________ Linux-powered Science __________________________ |
From: Alan W. I. <ir...@be...> - 2003-01-21 21:55:37
|
I will try to comment on what Joao and Rafael have said. On Tue, 21 Jan 2003, [iso-8859-1] Jo=E3o Cardoso wrote: > On Tuesday 21 January 2003 20:06, Rafael Laboissiere wrote: > > Hi Rafael! > > | * Alan W. Irwin <ir...@be...> [2003-01-21 10:23]: > | > On Mon, 20 Jan 2003, Robert Schwebel wrote: > | > > What's the state of the Perl/PDL interface? > | > > | > I don't know about PDL since that is an independent effort (see > | > Doug Hunt's messages to this list right after PLplot-5.1.0 was > | > released last year). > | > | Well, my original Perl bindings code had some limited support to PDL. > | However, I think that Doug's approach should be superior than mine. > | > | > We do have a rudimentary perl interface as part of generic PLplot, > | > but that is unsupported at this time because its developer ran out > | > of time to work on it. > | > | (That is me. I am still unable to participate to the PLplot effort. > | Too many things on the way.) > | > | > Personally, I think we should abandon that approach (which depended > | > on parsing the API from our DocBook API chapter) and go with swig > | > instead. > | > | Well, my approach combined both parsing the XML source of the API > | _and_ usign swig (see bindings/perl5/README). OOPS. Sorry I missed that, Rafael. That immediately gives me much more interest in the current perl interface. > | I do not think that > | parsing the XML source is a bad idea, provided that the plplot.h is > | also automatically generated. It is unacceptable to have two sources > | of the same information being maintained in parallel. Rafael, I agree that one source for our API would be better, but it will take some effort, and we have lived with *many* parallel versions of our AP= I descriptions for a long time. So it is the old tradeoff between a constant= , maintenance problem that makes a steady drain on our time/effort, or doing something much better which requires a lot more immediate time/effort but pays off later in reducing the maintenance required. "Short term pain for long-term gain". Here is a summary of the current parallel API descriptions. We have the docbook chapter describing the API, plplot.h, two separate files describing the API for both java and python, and files describing the API for fortran and tcl as well. For the java and python case, the two files are almost identical, but they *must* differ slightly because the current java interface has cruder support of the call-back functions. Once that is sorted out, the two files could be merged together, but not yet. Also, these two files differ quite a bit from plplot.h to signal the swig typedef= s when something special has to be done with arguments (such as dropping redundant dimensions from argument lists). > > In that case, let the documentation be generated from the code and not > the other way around! And it's easier to maintain plplot.h than > api.xml. Joao, that's because api.xml has extra information such as detailed documentation of each argument far beyond the argument types and minimal documentation that plplot.h has at the moment. Therefore, since doc/docbook/src/api.xml has the most documentation information (by far) in an easily parsable form , I agree with Rafael that this file should be the ultimate source of all other descriptions of our API. To implement that, scripts need to be developed to generate include/plplot.h, bindings/python/plplotcapi, bindings/java/plplotcapi, bindings/tcl/plapi.tpl, and the equivalent API description file(s) for fortran. I have put such scripts in the rough order from highest to lowest priority. From Rafael's comments above , it also looks like a script has already been written to generate the required swig interface file for perl, but I imagine there is some more work to do on that as well. Rafael, generating include/plplot.h from doc/docbook/src/api.xml might be the type of small project that might interest you. How about it? Alan __________________________ Alan W. Irwin email: ir...@be... phone: 250-727-2902 Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the Canadian Centre for Climate Modelling and Analysis (www.cccma.bc.ec.gc.ca) and the PLplot scientific plotting softwar= e package (plplot.org). __________________________ Linux-powered Science __________________________ |
From: <jc...@fe...> - 2003-01-21 20:33:57
|
On Tuesday 21 January 2003 20:06, Rafael Laboissiere wrote: Hi Rafael! | * Alan W. Irwin <ir...@be...> [2003-01-21 10:23]: | > On Mon, 20 Jan 2003, Robert Schwebel wrote: | > > What's the state of the Perl/PDL interface? | > | > I don't know about PDL since that is an independent effort (see | > Doug Hunt's messages to this list right after PLplot-5.1.0 was | > released last year). | | Well, my original Perl bindings code had some limited support to PDL. | However, I think that Doug's approach should be superior than mine. | | > We do have a rudimentary perl interface as part of generic PLplot, | > but that is unsupported at this time because its developer ran out | > of time to work on it. | | (That is me. I am still unable to participate to the PLplot effort.=20 | Too many things on the way.) | | > Personally, I think we should abandon that approach (which depended | > on parsing the API from our DocBook API chapter) and go with swig | > instead. | | Well, my approach combined both parsing the XML source of the API | _and_ usign swig (see bindings/perl5/README). I do not think that | parsing the XML source is a bad idea, provided that the plplot.h is | also automatically generated. It is unacceptable to have two sources | of the same information being maintained in parallel. In that case, let the documentation be generated from the code and not=20 the other way around! And it's easier to maintain plplot.h than=20 api.xml. (apart from the fact that I still can't generate the docs!) Joao |
From: Rafael L. <lab...@ps...> - 2003-01-21 20:15:12
|
* Alan W. Irwin <ir...@be...> [2003-01-21 10:23]: > On Mon, 20 Jan 2003, Robert Schwebel wrote: > > > What's the state of the Perl/PDL interface? > > I don't know about PDL since that is an independent effort (see Doug Hunt's > messages to this list right after PLplot-5.1.0 was released last year). Well, my original Perl bindings code had some limited support to PDL. However, I think that Doug's approach should be superior than mine. > We do have a rudimentary perl interface as part of generic PLplot, but that > is unsupported at this time because its developer ran out of time to work > on it. (That is me. I am still unable to participate to the PLplot effort. Too many things on the way.) > Personally, I think we should abandon that approach (which depended on > parsing the API from our DocBook API chapter) and go with swig instead. Well, my approach combined both parsing the XML source of the API _and_ usign swig (see bindings/perl5/README). I do not think that parsing the XML source is a bad idea, provided that the plplot.h is also automatically generated. It is unacceptable to have two sources of the same information being maintained in parallel. -- Rafael |
From: Alan W. I. <ir...@be...> - 2003-01-21 18:24:51
|
On Mon, 20 Jan 2003, Robert Schwebel wrote: > On Mon, Jan 20, 2003 at 12:12:39AM -0800, Alan W. Irwin wrote: > > To motivate you to try this new release, I should mention that the > > python and java interfaces to PLplot are now much more complete > > (thanks to swig). > > What's the state of the Perl/PDL interface? I don't know about PDL since that is an independent effort (see Doug Hunt's messages to this list right after PLplot-5.1.0 was released last year). We do have a rudimentary perl interface as part of generic PLplot, but that is unsupported at this time because its developer ran out of time to work on it. Personally, I think we should abandon that approach (which depended on parsing the API from our DocBook API chapter) and go with swig instead. We already have two swig-generated interfaces (python and java) to PLplot which work very well. Using the python interface as an example, I was able to generate the java interface quite straightforwardly in about a week's worth of work in December with no prior swig experience and very little java experience. As a consequence of this swig exposure I have become a big convert. Swig currently can be used to generate interfaces for 9 different languages to C/C++ libraries. So I am hoping we can generate a lot of additional PLplot interfaces (including guile, scheme, ruby, and especially perl) with swig. Do we have a swig/perl interface volunteer? Alan __________________________ Alan W. Irwin email: ir...@be... phone: 250-727-2902 Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the Canadian Centre for Climate Modelling and Analysis (www.cccma.bc.ec.gc.ca) and the PLplot scientific plotting software package (plplot.org). __________________________ Linux-powered Science __________________________ |
From: Alan W. I. <ir...@be...> - 2003-01-21 17:34:50
|
On Tue, 21 Jan 2003, Valerij Pipin wrote: > I've got the announcement about plplot-5.2.0 release. First of all, many > thanks to maintainers for such a nice software. > May I ask a question? Does the tar file of release differ from the today's > cvs tree? That's a good question, Valerij. It is the same underlying software exactly (except for one minor commit at this time), but the tarball has been massaged to make life easy for the user. So yes, CVS and tarball are quite different. Note this is the norm for software releases of many different free software packages now. In general, CVS users are expected to have all the latest/greatest development tools while that requirement is dropped for tarball users. In the specific case of PLplot, the required tools for using CVS are swig-1.3.17 (used to generate both the python and java interfaces), and the latest autotools packages (used to generate the configure script and the various *.in files in the various directories). Specifically, the autotools package versions that work are autoconf-2.57, automake-1.7.2, and libtool-1.4.3. You can generate the equivalent of the tarball with these specific tools installed by (a) making scripts/make_tarball.sh executable (we need shell access to the repository to fix this permissions problem permanently), and then by executing scripts/make_tarball.sh. If you look in that script you will see it runs .bootstrap.sh (which generates configure and the various *.in files using autoconf, automake, and libtool), fixes some additional permissions problems, downloads the generated documentation from the website, prepares the python and java interfaces using swig, and prepares the tcl interface using perl. I didn't look at your errors in detail, but I am virtually positive they are due to incorrect versions of the autotools packages and/or swig. Alternatively, if you want to do things the easy way, you can just download the tarball that was prepared in exactly the above way with the correct tool versions. In that case you will not need to run swig, autoconf, automake, or libtool so their versions on your system become irrelevant. Furthermore, the permissions will be right, and you will also have all the documentation. With the tarball you just need to run configure; make, and make install, and be happy...;-) Thanks, Valerij, for your interesting question. I am also looking forward to your report on using the tarball (or scripts/make_tarball.sh with the correct versions of the various developer tools) since you usually tend to run PLplot on platforms which we have no access to. Good luck, and let us know how it goes on the platforms you have access to. Alan __________________________ Alan W. Irwin email: ir...@be... phone: 250-727-2902 Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the Canadian Centre for Climate Modelling and Analysis (www.cccma.bc.ec.gc.ca) and the PLplot scientific plotting software package (plplot.org). __________________________ Linux-powered Science __________________________ |