source: XMLF90-doc/Tutorial/README @ 1160

Last change on this file since 1160 was 6, checked in by ymipsl, 13 years ago

Import des sources XMLF90

File size: 2.0 KB
Line 
1See the UserGuide for a tutorial and a reference to the
2SAX and stream XPATH parser APIs.
3
4The sax and xpath directories contain the source for the exercises in
5the User Guide.
6
7The new DOM interface is documented in file DOM.html.
8The WXML  writing library and the "Jumbo90" (CML writer by Jon Wakelin)
9are documented in WXML.html
10
11
12GETTING STARTED QUICKLY
13
14You should really read the User Guide, but if you insist, here is the
15*minimum* you can do to get the parser working:
16
17 * Define the environment variable FLIB_ROOT to point to the macros
18   directory in the xmlf90 distribution
19   (You could make it point anywhere, but this is the simplest setup,
20    as you have everything under the same tree)
21
22      FLIB_ROOT=/somewhere/xmlf90/macros ; export FLIB_ROOT (sh-like shells)
23      setenv FLIB_ROOT /somewhere/xmlf90/macros           (csh-like shells)
24
25 * Go into macros, look through the fortran-XXXX.mk files,
26   and see if one of them applies to your computer/compiler combination.
27   If so, copy it or make a (symbolic) link to 'fortran.mk':
28
29        ln -sf fortran-lf95.mk fortran.mk
30
31   If none of the .mk files look useful, write your own, using the
32   files provided as a guide. Basically you need to figure out the
33   name and options for the compiler,  the extension assigned to
34   module files, and the flag used to identify the module search path.
35
36 The above steps need only be done once.
37
38  Go back to the top directory.
39
40  If you have a Fortran95 compiler, simply type "sh build.sh"
41  If not, edit build.sh and comment out the DOM sections as directed.
42
43 * Go into subdirectory 'Examples' and explore.
44
45 * Go into subdirectory 'Tutorial' and try the exercises in the User Guide
46  (see the next section for compilation details).
47
48** Compiling user programs
49
50After installation, the appropriate modules and library files should
51already be in $FLIB_ROOT/modules and
52$FLIB_ROOT/lib, respectively. To compile user programs, it
53is suggested that the user create a separate directory to hold the
54program files and prepare a Makefile following the templates in the
55Examples/ directory.
Note: See TracBrowser for help on using the repository browser.