-
Notifications
You must be signed in to change notification settings - Fork 20
/
DEVEL_NOTES
53 lines (39 loc) · 1.57 KB
/
DEVEL_NOTES
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
$Id: DEVEL_NOTES,v 1.4 2009-02-17 22:07:43 wilsonp Exp $
This file contains some information on how to use automake/autoconf
and reminders about which files are necessary for the user-level
distribution and which files are only necessary for the
maintainers/developers.
1. Users should not need to run automake or autoconf.
This means that users don't need copies of configure.in or Makefile.am.
------------------------------------------
2. installation directory locations
nonxsdir = $(prefix)/data
xsdir = $(prefix)/data
docdir = $(prefix)/doc
sampledir = $(prefix)/sample
bindir = ${exec_prefix}/bin
XXXXXXXX alara executable XXXXXXXX
XXXXXXXX tools:scripts & executables XXXXXXX
---------------------------------------------
3. Upon a fresh CVS check out...
... run the following:
%> aclocal
%> autoheader
%> autoconf
%> automake --add-missing
and every time you change a Makefile.am, you need to
run automake again.
-----------------------------------------------
4. Establishing a new version or patch level....
(this assumes everything is tested and working and checked in to CVS)
a. update version string in configure.ac
b. run autoconf tools as in (3) above
c. ./configure and make new alara executable
d. replace sample output
i. run script to run samples into temporary directory
ii. move old "ref_out" directory to "ref_old"
iii. move temporary directory from (i) to "ref_out"
iv. move SVN directory from "ref_old" to "ref_out"
v. check in new ref_out files with comments
e. finish section in NEWS and check-in
f. tag repository with new version string