1$Header: /var/cvs/mbdyn/mbdyn/mbdyn-1.0/README,v 1.36 2017/01/12 14:40:30 masarati Exp $
2
3MBDyn (C) is a multibody analysis code.
4http://www.mbdyn.org
5
6Copyright (C) 1996-2017
7
8Pierangelo Masarati     <masarati@aero.polimi.it>
9Paolo Mantegazza        <mantegazza@aero.polimi.it>
10
11Dipartimento di Ingegneria Aerospaziale - Politecnico di Milano
12via La Masa, 34 - 20156 Milano, Italy
13http://www.aero.polimi.it
14
15
16
17developers:
18
19	- check out from the CVS tree
20	- run "sh ./bootstrap.sh" to generate ancillary files.
21	  May need some tailoring.  A system with working autoconf,
22	  automake and libtool is required; I'm currently using
23	  autoconf 2.59, automake 1.9.6, libtool 1.5.6
24	- tar the tree and move to the target system; this way, all
25	  the ancillary files will be available even if the target
26	  system does not have those tools.
27
28
29
30developers without CVS access:
31
32	- ask for a snapshot from the CVS
33	- merge: two approaches; either
34		1) post patches to the checked out sources;
35		   assuming mbdyn-HEAD is the original snapshot,
36		   and mbdyn-DEVEL is the locally modified version,
37		   run
38
39	diff -uNr mbdyn-HEAD mbdyn-DEVEL > AUTHOR-DATE-DESC.patch
40
41		   where
42			- AUTHOR is the name of the Author,
43			- DATE is the date of the snapshot,
44			- DESC is a short description of the modifications.
45
46		   Or
47
48		2) post the modified source tree, including the CVS
49		   directories and their contents, unmodified
50
51
52
53distribution:
54
55	- set build/version to the right number
56	# - set MBDYN_DEVEL=no in configure.ac
57	- follow the above instructions
58	- run "./configure" with the desired options
59	- add version and release date to NEWS
60	- add version and release notes to CHANGES
61	- check BUGS
62	- advance MBDYN_REL_ENG tag after running ./check_cvs.sh
63	- set MBDYN_REL_ENG_<version> tag
64	- run "make dist" && "make distcheck"
65	- update https://www.mbdyn.org/ web page
66	- announce on mailing lists
67
68
69
70installation:
71
72	- get a working source tree, either by following the "developers"
73	  or the "distribution" instructions or from the web site
74	  <http://www.aero.polimi.it/~mbdyn/>
75	- configure the package; "./configure" will suffice in most cases,
76	  unless you need some of the supported packages and they are not
77	  in the standard place
78	- "make" the package
79	- run "make install"; the command "mbdyn" and some utilities will
80	  be installed in "$PREFIX/bin", while some libraries will be put
81	  in "$PREFIX/lib" (PREFIX defaults to /usr/local/mbdyn).
82	  Those libraries are neither required to run mbdyn nor the utilities
83	  (unless you force the shared build).
84	  A bare-bone man page will be installed in "$PREFIX/man/man1".
85
86