Annotation of OpenXM_contrib/gnuplot/0INSTALL, Revision 1.1.1.2
1.1 maekawa 1: Installation
2: ************
3:
4: This document is divided into four parts: the first part (For the
5: impatient) provides a quick overview of configuration and compilation
6: instructions. It also lists those options to the configure shell script
7: which are unique to gnuplot. Part two describes the environment variables
8: used by gnuplot. Part three explains in detail how --with-PACKAGE=PATH
9: works, and how this option interacts with --libdir and --includedir.
10: Part four addresses some platform specific problems and testing issues.
11: There are also some hints how to build gnuplot with pre-ANSI C compilers.
12: Part five finally describes a few graphical front ends for gnuplot.
13:
14: The description of preprocessor options previously found here has been
15: moved to a new file called 0PORTING. Generic installation instructions
16: for `configure', such as distributed with FSF/GNU packages, have been
17: moved to the file INSTALL.gnu.
18:
19: For the impatient
20: =================
21:
22: First, tune term.h to choose which terminal drivers you wish to enable.
23: If you want to support gif output, you need to download, compile and
24: install the gd library : see term/gif.trm for details.
25:
26: If you want to support png output (free gif alternative), you need
27: png and z libraries : see term/png.trm for details. Note that the
28: png library will probably not compile without an ANSI/ISO C compiler.
29:
30: A complete overview of configure options is below in the Basic
31: Installation section. On platforms which do not support GNU
32: autoconf/configure, ie. most non-Unix platforms, look for a makefile
33: that looks suitable, (makefile.emx for emx on dos, makefile.nt for
34: MS VC++ 4.x on NT and probably win95, makefile.win for borland c on
35: win95/nt, makefile.wc for DOS Watcom C etc.)
36:
37: File location defaults
38: ----------------------
39:
40: PREFIX /usr/local
41: gnuplot PREFIX/bin
42: gnuplot_x11 PREFIX/bin
43: gnuplot.1 PREFIX/man/man1
44: gnuplot.gih PREFIX/share
45:
46: The only files where the runtime location is defined at compile time are
47: gnuplot.gih and show.c. This is important if gnuplot is not installed by running
48: 'make install'.
49:
50: The default path for the help library, gnuplot.gih, can be controlled in
51: several different ways:
52:
53: o with configure's --prefix= option, eg.
54: ./configure --prefix=/gnuplot
1.1.1.2 ! maekawa 55: gnuplot will look for the online help file, gnuplot.gih, in /gnuplot/share.
! 56: Attention: This option affects the location of *all* installed files!
1.1 maekawa 57:
58: o with configure's --datadir= option, eg.
59: ./configure --datadir='/gnuplot/docs'
1.1.1.2 ! maekawa 60: gnuplot will look for the online help file, gnuplot.gih, in /gnuplot/docs.
1.1 maekawa 61:
62: o at make time, eg.
63: make HELPFILE='/gnuplot/docs/gnuplot.gih'
1.1.1.2 ! maekawa 64: gnuplot will look for the online help file /gnuplot/docs/gnupot.gih.
1.1 maekawa 65:
66: o at execution time by specifying the helpfile with the environment
67: variable GNUHELP (see "Environment Variables" below).
68:
69: The default location of the executables can be controlled in different
70: ways:
71:
72: o with configure's --prefix= option, eg.
73: ./configure --prefix=/gnuplot
1.1.1.2 ! maekawa 74: gnuplot will be installed as /gnuplot/bin/gnuplot.
1.1 maekawa 75: Attention: This affects the location of *all* installed files!
76:
77: o with configure's --bindir= option, eg.
78: ./configure --bindir='/gnuplot/bin'
1.1.1.2 ! maekawa 79: gnuplot will be installed as /gnuplot/bin/gnuplot.
1.1 maekawa 80:
81: o at make time, eg.
1.1.1.2 ! maekawa 82: make BINDIR='/gnuplot/bin'
! 83: gnuplot will be installed as /gnuplot/bin/gnuplot.
1.1 maekawa 84:
85: If the executables are not installed in the default location, files
86: written by the `save' command cannot be used as scripts on Un*x platforms.
87: There is no way to specify the location of the executables during
88: runtime. Other platforms are not affected by this.
89:
90: The gnuplot demo files are not installed by default. If desired, they
91: should be copied manually to a location of choice.
92:
93: Unix, configure
94: ---------------
95:
96: On Unix, use
97: $ ./configure
98: $ make
99: [ Optionally run demos--see "How to test gnuplot" below. ]
100: $ make install
101:
102: If gcc is installed, it is used by default. A different compiler can be
103: used through the CC environment variable:
104:
105: (Bourne shell)
106: $ CC=c89 ./configure
107:
108: (C shell)
109: $ setenv CC c89
110: $ ./configure
111:
112: Any environment settings for CFLAGS are included into the Makefile,
113: so please make sure that these are really needed.
114:
115: There are several options available for configure that you may want
116: to change. A complete list of options is available through
117:
118: $ ./configure --help
119:
120: --prefix=PREFIX Install architecture-independent files in PREFIX
121: [/usr/local]. The gnuplot (and gnuplot_x11) binary
122: is installed in PREFIX/bin.
123: --bindir=DIR user executables in DIR [PREFIX/bin]
124: --datadir=DIR Read-only architecture-independent data in DIR
125: [PREFIX/share]. The gnuplot help file is installed
126: in this directory.
127: --libdir=DIR object code libraries in DIR [EPREFIX/lib]
128: --includedir=DIR C header files in DIR [PREFIX/include]
129: --mandir=DIR Man documentation in DIR [PREFIX/man]
1.1.1.2 ! maekawa 130: --with-readline (*) use the builtin minimal readline function
! 131: --without-readline do not use the builtin readline function
! 132: --with-readline=gnu use the GNU readline library
! 133: --with-readline=PATH Specify the location of GNU readline
1.1 maekawa 134: --with-plot use the Unix plot library
135: --with-plot=PATH Specify the location of GNU libplot
136: --with-gd (*) Enable gif terminal with Tom Boutell's gd library
137: (requires GD library)
138: --with-gd=PATH Specify the location of libgd
139: --with-png (*) Enable png terminal
140: (requires libpng and libz)
141: --with-png=PATH Specify the location of libpng
1.1.1.2 ! maekawa 142: --with-cwdrc check current directory for .gnuplot file,
! 143: normally disabled for security reasons
! 144: --with-lasergnu install lasergnu printer script
! 145: --with-linux-vga use the Linux SVGA console driver
! 146: (requires /usr/lib/libvga)
1.1 maekawa 147: --enable-apollo Apollo Graphics Primitive Resource
148: --enable-gpr Apollo Graphics Primitive Resource (fixed-size window)
149: --enable-cgi enable CGI terminal (SCO only)
150: --enable-iris enable IRIS terminal (IRIS4D only)
151: --enable-sun enable sunview terminal (Sun only)
152: --enable-unixpc enable unixpc terminal (ATT 3b1 or ATT 7300)
153: --enable-system-time use the system time routines in time.c
154: --with-x (*) Use the X Window System
155:
156: Options marked with (*) are on by default, ie. these features or packages
157: will be used if configure can detect them, even if the corresponding option
158: is not specified. Please note that the `--with-PACKAGE' options can have
159: additional arguments:
160:
161: o `--with-PACKAGE' is equivalent to `--with-PACKAGE=yes'
162: o `--with-PACKAGE=no' will disable checking for PACKAGE. It has the same
163: effect as `--without-PACKAGE'.
164: o `--with-PACKAGE=PATH' will check for PACKAGE in PATH
165:
166: Unix, no configure
167: ------------------
168:
169: The older, no-longer-preferred, way is to copy makefile.unx to Makefile
170: cp makefile.unx Makefile
171: Look through the Makefile to see if you need to make any changes.
172: See especially the HELPDEST and TERMFLAGS variables. Edit if needed.
173: Alternatively, all these variables may be set as command line arguments to
174: 'make'. For example:
175:
176: make <MACHINE> HELPDEST='/usr/um/misc/lib' \
177: DEST='/usr/um/misc/bin' READLINE=
178:
179: Type
180: make
181: For further instructions.
182: If that works, try
183: make install
184: For further instructions.
185:
186: VMS
187: ---
188:
1.1.1.2 ! maekawa 189: On VMS, you can use MMS, MMK, or another make utility, or you can
! 190: use BUILDVMS.COM. The supplied files work with Alpha/VMS V6.2 and
! 191: DECC V5.7; you may get warnings or more serious errors depending on
! 192: the versions of the C compiler, the C run-time libraries, and VMS on
! 193: your system.
! 194:
! 195: To compile using MMK:
! 196: MMK/DESCRIPTION=MAKEFILE.VMS
! 197: To compile using MMS on VAX:
! 198: MMS/DESCRIPTION=MAKEFILE.VMS
! 199: To compile using MMS on Alpha:
! 200: MMS/DESCRIPTION=MAKEFILE.VMS/MACRO=__ALPHA__=1
! 201:
! 202: Alternatively, you can use MAKE_VMS.COM. This command file will run
! 203: MMK or MMS to build gnuplot. If you don't have either one installed, it
! 204: will use the command file. The first parameter on the command line is
! 205: the compiler you want to use (default DECC).
! 206:
! 207: It may sometimes be useful to add `/IGNORE=WARNING' to the `MMS' call.
! 208:
! 209: To compile using GNUC or VAXC:
! 210: add /MACRO=GNUC or /MACRO=VAXC to the above command
! 211: To compile with another make utility:
! 212: check the documentation of your utility to specify the description
! 213: file and any necessary macros (__ALPHA__, GNUC, or VAXC)
1.1 maekawa 214: Or if you don't have a suitable make:
1.1.1.2 ! maekawa 215: @BUILDVMS
1.1 maekawa 216: To tell gnuplot where to find the help library:
1.1.1.2 ! maekawa 217: $ define gnuplot$help disk:[directory]gnuplot.hlb
! 218: Alternatively, put the help in the main system help library.
1.1 maekawa 219:
220: AmigaOS
221: -------
222:
223: Using Aztec C 5.2a
224: make -f makefile.ami
225: Using SAS/C 6.1 or later versions
226: smake -f makefile.amg
1.1.1.2 ! maekawa 227: You can also copy makefile.amg to smakefile and just type `smake'.
! 228:
! 229: At the beginning of makefile.amg you will find a configuration
! 230: section where you have to adjust all settings which control the build
! 231: process. Most important is probably to select the terminal devices
! 232: which should be supported. You can create a version offering
! 233: png graphics as well as gif support. Use the appropriate settings
! 234: for CPU and MATH to compile for a specific machine type.
! 235: Be sure to enable only those devices for which you have the
! 236: necessary software already installed. Also ensure that the
! 237: libraries and the sources are all compiled using the same
! 238: settings for CPU and MATH.
1.1 maekawa 239: Using gcc: see Unix
240:
241: Atari/TOS
242: ---------
243:
244: Using gcc 2.x as unix cross- or native compiler
245: make -f makefile.st
246: (Edit top of makefile.st for name of crosscompiler or choose native setting)
247: Using PureC
248: use gnuplot.prj
249: Using TurboC
250: use gnuplot.prj
251: (Edit gnuplot.prj according to notes at the beginning)
252:
253: MS-Windows
254: ----------
255:
256: Using Microsoft C 7.0 and compiling for MS-Windows
257: copy makefile.msw makefile
258: nmake
259: Put wgnuplot.exe, wgnuplot.dll, wgnuplot.hlp and wgnuplot.mnu
260: in the windows directory.
261:
262: Using Borland C++ 3.1 and compiling for MS-Windows
263: copy makefile.win makefile
264: Edit makefile to change TC.
265: make
266: Put wgnuplot.exe, wgnuplot.dll, wgnuplot.hlp and wgnuplot.mnu
267: in the windows directory.
268:
1.1.1.2 ! maekawa 269: Using Visual C++ and compiling for Windows NT/95/98
! 270: nmake -f makefile.nt
! 271: or
! 272: copy makefile.nt makefile
! 273: nmake
! 274:
1.1 maekawa 275: Using the MinGW32 port of egcs: you need the Micrsoft SDK for the
276: moment.
277: copy makefile.mgw makefile
278: Look through the Makefile to see if you need to make any changes.
279: make
280: make install
281:
282: Using the Cygwin port of gcc, which includes MinGW32: you need the
283: Micrsoft SDK for the moment.
284: copy makefile.cyg makefile
285: Look through the Makefile to see if you need to make any changes.
286: make
287: Put wgnuplot.exe, wgnuplot.dll, wgnuplot.hlp and wgnuplot.mnu
288: in the windows directory.
289:
290: MSDOS
291: -----
292:
293: Using DJGPP
294: Basically the same as Unix+configure. Andris Pavenis <pavenis@lanet.lv>
295: has contributed a shell script which makes the whole process even easier:
296: just run djconfig.sh, and then make.
297: For novices, it is recommended to use makefile.dj2 instead:
298: copy makefile.dj2 makefile
299: make
300:
301: Using Microsoft C 7.0.
302: copy makefile.msc makefile
303: nmake
304:
305: Using Borland C++ 3.0
306: copy makefile.tc makefile
307: Edit makefile to change TC, BIN, BGI, BGIOBJ. You may also want to turn
308: off overlays (See manual for more on overlays).
309: make
310:
311: The file gnuplot.gih is needed for help on the PC.
312: If the file gnuplot.gih is not in the default directory, then use:
313: set GNUHELP={full path name of gnuplot.gih}
314:
315: OS/2
316: ----
317:
318: To compile under OS/2 (2.x and above) you need the development
319: suite EMX 0.9 (including gcc). You should also have
320: GNU Make and IBM's IPFC (Information Presentation Facility Compiler,
321: available from the Developer's Toolkit; nowadays it's accessible
322: through an IBM website for free!).
323:
324: At the beginning of Makefile.os2 you will find a configuration
325: section where you have to adjust all settings which control the build
326: process. Most important is probably to select the terminal devices
327: which should be supported. You can create a version offering
328: PM graphics as well as X11 support (to use with XFree86).
329: Support for these two terminals is provided by additional
330: executables.
331: Be sure to enable only those devices for which you have the
332: necessary software already installed. Also ensure that the
333: libraries and the sources are all compiled (not) using
334: the '-Zmt' flags.
335:
336: Executing
337: make -f makefile.os2
338: should create a default build while
339: make -f makefile.os2 help
340: will show you all pre-defined targets.
341:
342: See other sections of the manuals for more information about
343: installing/using gnuplot on OS/2.
344:
345: Environment Variables
346: =====================
347:
348: See 'help environment'.
349:
350: If the environment variable GNUTERM is found, it is used as the terminal
351: type. Otherwise, in some cases the variable TERM will be used, or the
352: hardware may be automatically detected.
353:
354: The PC version looks for the environment variable GNUPLOT to contain
355: the name of the directory from which to load the initialization file
356: GNUPLOT.INI. See the help on 'start_up' for more information.
357:
358: HOME is examined as a directory where a .gnuplot startup file might be
359: found. See help on "start-up".
360:
361: If defined, the environment variable GNUHELP is used for the name
362: of the .gih help file, otherwise HELPFILE (defined in makefile or
363: command.c) is used.
364:
365: The VMS version looks for the logical name GNUPLOT$HELP to locate
366: the help library.
367:
368: The CGI drivers need the CGIPATH environment variable to set the path
369: to the CGI agents, and the CGIDISP and/or CGIPRNT environment variables
370: to set the output devices.
371:
1.1.1.2 ! maekawa 372: If creating dynamically linked executables for the X11 Window System, it
! 373: may be necessary to add flags to the LIBS variable in Makefile
! 374: to make sure gnuplot finds all required libraries at runtime. Systems like
! 375: SunOS and Solaris use -R to specify the runtime library search path, whereas
! 376: OSF/Dec Unix, Irix and Linux use -rpath. If this is not possible, the
! 377: LD_LIBRARY_PATH environment variable should be set.
1.1 maekawa 378:
379: About --with-PACKAGE[=PATH]
380: ***************************
381:
382: The following description applies to gnuplot only.
383:
384: Every `--with-PACKAGE' option sets a `with_package' variable in
385: configure. Depending on how `--with-PACKAGE' was invoked, there are
386: only three different possible values for the `with_package' variable:
387:
388: Option $with_package
389: ----------------------------------------
390: (not specified) yes
391: --with-package yes
392: --with-package=yes yes
393: --with-package=no no
394: --with-package=PATH PATH
395: --without-package no
396:
397: This means that configure will always (by default) try to locate PACKAGE
398: unless `--with-package=no' or `--without-package' was specified. Examples
399: for with-PACKAGE options used by gnuplot's configure are `--with-gd',
400: `--with-png'. The corresponding package variables are `with_gd',
401: and `with_png'.
402:
403: For gnuplot, configure uses the macros `gp_SEARCH_LIBDIRS' and
404: `gp_SEARCH_HEADERDIRS' to search for libraries and includes, resp. These
405: macros are different from the standard GNU autoconf macros for this purpose,
406: `AC_CHECK_LIB' and `AC_CHECK_HEADER/S' (see autoconf manual). The
407: gp_XXX macros are closely tied to gnuplot, and cannot be used for other
408: packages without modification.
409:
410: The difference between these package specific macros and standard
411: autoconf macros is that they do search more than one (the default)
412: directory to determine the location of the specified file.
413:
414: Libraries will be searched in at least three, and up to five different
415: directories, depending on the PATH specified with `--with-PACKAGE=PATH':
416:
417: o the default linker path (this is really more than one directory)
418: o /usr/local/lib, which is a fairly common place for 3rd party libs
419: o the PATH directory, trailing `/lib/libPACKAGE.a' stripped off
420: o the PATH directory, trailing `/lib/libPACKAGE.a' stripped off and
421: `/lib' added
422: o the PATH directory, trailing `/libPACKAGE.a' stripped off.
423:
424: Using the default linker path as the first search directory has one
425: big, but not so obvious advantage: if all libraries are in the same
426: directory, the path to the first library specified with --with-PACKAGE
427: is added to the linker path with a `-L' option. The library searched
428: for with the next --with-PACKAGE option will now be found faster, because
429: only one additional directory is checked. This is also true for header files.
430:
431: Example: the user has unpacked the gd library distribution into
432: /home/user/source/gd:
433:
434: $ configure --with-gd=/home/user/source/gd
435:
436: will search the following directories for libgd.a:
437:
438: o the default linker path
439: o /usr/local/lib
440: o /home/user/source/gd
441: o /home/user/source/gd/lib
442: o /home/user/source/gd
443:
444: Include files will be searched in at least two, and up to three different
445: directories, depending on the PATH specified with `--with-PACKAGE=PATH':
446:
447: o the default include path (can be more than one diretcory)
448: o /usr/local/include, a fairly common place for 3rd party headers
449: o the PATH directory, trailing `/lib/libPACKAGE.a' stripped off
450: o the PATH directory, trailing `/lib/libPACKAGE.a' stripped off and
451: `/include' added
452:
453: Caveat: the `gp_SEARCH_HEADERDIRS' macro should only be used after the
454: corresponding `gp_SEARCH_LIBDIRS' macro to take full advantage of the
455: search algorithm. This is a reasonable assumption nevertheless, because
456: it allows for structuring configure.in so that the test for a header file
457: is skipped if the corresponding library is not found.
458:
459: Here are some more examples:
460:
461: o the gd and png libraries are in /usr/local/gnu/lib, which is
462: automatically searched by gcc. The corresponding header files are
463: in /usr/local/gnu/include, which is not in gcc's include search path.
464: Solution:
465:
466: $ ./configure --with-gd=/usr/local/gnu
467:
468: o the gd and png libraries are in /opt/gnu/lib, the header files are
469: in /opt/gnu/include. Solution:
470:
471: $ ./configure --with-gd=/opt/gnu
472:
473: o the gd and png libraries and headers are all in different directories,
474: none of which is in the compilers search path:
475:
476: $ ./configure --with-gd=/tmp/gd --with-png=/tmp/libpng
477:
478: [I would like to implement the more generic `--site-includes' and
479: `--site-libraries' options for additional flexibility, but this is
480: painfully difficult with the current autoconf. It also seems that such
481: a feature would not comply with GNU coding standards.]
482:
483: Platform problems and testing
484: *****************************
485:
486: This section addresses trouble shooting and testing issues. Userland
487: questions are answered in the FAQ.
488:
489: Platform notes
490: ==============
491:
492: Generally, if you think that configure has made a mistake in detecting
493: platform features, there are two ways to switch these off.
494:
495: Example:
496: configure was for some reason unable to detect the memset() function, but
497: you are sure it is ok to use on your platform. Now you can either edit
498: config.cache and change
499:
500: ac_cv_func_memset=${ac_cv_func_memset='no'} to
501: ac_cv_func_memset=${ac_cv_func_memset='yes'}
502:
503: and rerun configure, or, edit config.h and change
504:
505: /* #undef HAVE_MEMSET */ to
506: #define HAVE_MEMSET 1
507:
508: Note that changing such defines at compile time, eg. via
509: 'make DEFS=-DHAVE_MEMSET' is wrong, because the DEFS variable in Makefile
510: may contain other defines (make DEFS='-DHAVE_CONFIG_H -DHAVE_MEMSET'
511: should work, though).
512:
513: - HP-UX 9.x
514: It is recommended to use gcc, although the native compiler cc may
515: work with warnings.
516:
517: - HP-UX 10.x
518: It is recommended to use the native compiler cc, as problems
519: have been reported when using gcc. In the cases reported, we have
520: yet to establish whether the compiler is at fault, or the compiler
521: setup/configuration is broken.
522:
523: - IRIX 6.x
524: If you want to use the png terminal, you must install your own
525: versions of libpng and zlib. The versions supplied with the OS
526: are too old. Note that you need be very careful to select the
527: correct compiler options/ABI's.
528:
529: - MS-DOS
530: If ports of common Unix utilities (bash, sed etc) are available,
531: gnuplot can be built with DJGPP. Install instructions are the same
532: as for Unix (with configure).
533:
534: - SunOS 4.x
535: An ANSI/ISO C compiler should be used to compile gnuplot. It is
536: recommended to install gcc. If this is not an option, the system
537: compiler cc can be made to work with Wietse Venema's unproto tool.
538: See entry below for instructions.
539:
540: As of 1998-11-18, gnuplot compiles again with the native compiler cc.
541:
542: - System V.2/Ultrix 4.x/M88 SysV.3
543: An ANSI/ISO C compiler should be used to compile gnuplot. It is
544: recommended to install gcc. If this is not an option, the system
545: compiler cc can be made to work with Wietse Venema's unproto tool.
546:
547: unproto is available from
548: ftp://ftp.win.tue.nl/pub/unix/unproto5.shar.Z
549: ftp://ftp.porcupine.org/pub/lang/unproto5.shar.Z
550:
551: After installing unproto, configure gnuplot with
552:
553: (Bourne shell syntax)
554:
555: $ cd gnuplot
556: $ CC='cc -B/full/path/to/unproto/dir/ -tp' ./configure <options>
557:
558: or (C shell syntax)
559:
560: prompt (41) cd gnuplot
561: prompt (42) setenv CC 'cc -B/full/path/to/unproto/dir/ -tp'
562: prompt (43) ./configure <options>
563:
564: The required compiler options shown here are for System V.2. For other
565: platforms, consult the unproto documentation. `/full/path/to/unproto/dir'
566: is the full path name of the directory where unproto is installed. It is
567: not necessary to "install" unproto, one can just create a subdirectory
568: in gnuplot's source directory and use it from there.
569:
570: How to test gnuplot
571: ===================
572:
573: No comprehensive test suite for gnuplot's features has been written
574: to date. However, the supplied demo files provide a good method of
575: testing commonly used features. All command line examples below assume
576: Unix Bourne shell syntax.
577:
578: The demo files can be run interactively by eg.
579:
580: $ cd gnuplot/demo
581: $ PATH=..:$PATH ../gnuplot simple.dem
582:
583: and gnuplot prompts the user to "Hit return to continue" to cycle
584: through all the plots. (The PATH= statement is only required if you are
585: using the X11 plotting device and the gnuplot_x11 binary has not been
586: installed yet.)
587:
588: To run the demos in a specified file without interaction, one
589: can use
590:
591: $ PATH=..:$PATH ../gnuplot simple.dem </dev/null
592:
593: To run all demos non-interactively, use
594:
595: $ PATH=..:$PATH ../gnuplot all.dem </dev/null
596:
597: To use a different plotting device than the default (usually X11
598: under Unix), use eg.
599:
600: $ GNUTERM=dumb ../gnuplot all.dem </dev/null
601:
602: To test the capabilities of the terminal you are using, there is
603: the 'test' command:
604:
605: $ gnuplot
606:
607: G N U P L O T
608: Unix version 3.7
1.1.1.2 ! maekawa 609: patchlevel 1
1.1 maekawa 610: last modified Tue Jan 12 13:48:06 BST 1999
611:
612: Copyright(C) 1986 - 1993, 1998
613: Thomas Williams, Colin Kelley and many others
614:
615: Send comments and requests for help to info-gnuplot@dartmouth.edu
616: Send bugs, suggestions and mods to bug-gnuplot@dartmouth.edu
617:
618: Terminal type set to 'x11'
619: gnuplot> test
620:
621: `test` creates a display of line and point styles and other useful things
622: appropriate for the terminal you are using.
623:
624: Front Ends for gnuplot
625: ======================
626:
627: o Xgfe by David Ishee <dmishee@jasper.he.net>, available from
628: http://von-mises.home.ml.org/xgfe/xgfe.html
629: If you download the source, you need Qt library from
630: http://www.troll.no/
631:
632: o Bruce Ravel <ravel@phys.washington.edu> has written a new version of
633: gnuplot-mode for GNU emacs and XEmacs. This version is based on
634: the gnuplot.el file by Gershon Elber which is included with this
635: distribution. The package is available from
636: http://feff.phys.washington.edu/~ravel/gnuplot/
637:
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>
![[BACK]](/icons/cvsweb/back.gif){kind=icon}
Return to 0INSTALL CVS log ![[TXT]](/icons/cvsweb/text.gif){kind=icon}
![[DIR]](/icons/cvsweb/dir.gif){kind=icon}
Up to [local] / OpenXM_contrib / gnuplot