source: trunk/README.developers @ 1822

Revision 1004, 2.0 KB checked in by Freddie Akeroyd, 4 years ago (diff)

Add in fixes from 4.1 branch for r985:r1003

  • require autoconf 2.61 and above
  • fix for JAVAC being defined

Refs #94

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
Line 
1Initial Setup
2-------------
3
4You first need to type:
5
6    sh autogen.sh
7
8to generate the initial configure and *.in files. You only need to
9type this again if you upgrade you system's versions of
10libtool/automake/autoconf and wish to use these newer version for the build
11
12After doing this type:
13
14    ./configure
15
16For a full list of options that can be passed to configure type:
17
18    ./configure --help
19
20(typical configure options include the choice of compiler, enabling or
21 disabling creation of bindings and the location of HDF libraries)
22
23General Building
24----------------
25
26Just typing
27
28    make
29
30should be enough to build the NeXus libraries and executables from source.
31Make will automatically re-run configure if it needs to.
32The test programs can then be run with
33
34    make check
35
36and everything installed onto the local system with
37
38    make install
39
40Making a distribution kit
41-------------------------
42
43To generate a *.tar.gz distribution kit just type:
44
45    make distcheck
46
47If you need to pass arguments to "configure" during the distcheck process,
48you must add these to the DISTCHECK_CONFIGURE_FLAGS variable in Makefile.am
49
50To generate an RPM install kit see README.rpm
51
52If you have problems
53--------------------
54
55If  autogen.sh  reports errors, it may be that you need
56to install/upgrade your versions of autoconf, automake and libtool.
57Source for these can be obtained from:
58
59ftp://ftp.gnu.org/gnu/autoconf
60ftp://ftp.gnu.org/gnu/automake
61ftp://ftp.gnu.org/gnu/libtool
62
63Most likely it will be autoconf that will need updating - NeXus
64now requires autoconf 2.61 or above
65
66NeXus Developer Mailing Lists
67-----------------------------
68
69CVS commit/log messages are automatically sent to the nexus-cvs@anl.gov
70mailing list - if you wish to receive these, subscribe to the list via the link
71
72  http://www.neutron.anl.gov/mailman/listinfo/nexus-cvs
73
74Any general developer questions should be directed to nexus-developers@anl.gov
75list - you can subscribe to this via the link
76
77  http://www.neutron.anl.gov/mailman/listinfo/nexus-developers
78
79$Id$
Note: See TracBrowser for help on using the repository browser.