3 INSTALL - installing StepMake
7 This page documents installation and usage of StepMake
13 To use StepMake with your package, you do something remotely like:
15 tar xzf releases/stepmake-0.1.23
16 cd package-x.x.x/ # package to be StepMake-ised
17 ./../stepmake-0.1.23/bin/stepmakeise.sh
19 You'll have to customize at least the files:
24 to your package's needs. You might want to take a look at:
26 ./make/Toplevel.make.in
31 Also, you should put a Makefile in every subdirectory of your
32 package. These makefiles generally are quite simple, e.g. this
33 is a the makefile for an include directory of LilyPond:
35 # lily/include/Makefile
38 include $(depth)/make/Stepmake.make
41 it will identify all code(.h, .hh, ...) files and take care of distributing
44 There's a file(make/Template.make) that you can use as an example.
45 See also the Makefiles in the LilyPond or Yodl package.
48 Once included in your package, StepMake (or in fact, any
49 StepMake-ised package) behaves as a normal subdirectory;
50 make commands such as 'make dist' recurse into the stepmake tree
51 (For a list of available targets, type code(make help) after
53 Stepmake (and any changes made) will be distributed with the main
54 pacakage. However, StepMake doesn't lose its independency, change
55 to the stepmake directory, and it'll behave as a main package.
56 You shouldn't version directory names of subpackages, otherwise
57 you'll see that package twice in each patch when you upgrade.
61 To use StepMake with a package you need:
64 it()A GNU system: StepMake is known to work on these GNU systems: Linux
65 (PPC, intel), FreeBSD, AIX, NeXTStep, IRIX, Digital Unix and Solaris.
66 If you have the Cygnus WINDOWS32 port of the GNU utils, it will even
67 work in Windows NT/95, but we don't promise to support it.
74 Although not strictly necessary, these are recommended to have.
78 it()Yodl. All documentation will be in Yodl. (1.22.jcn3)
83 COMMENT(Hmm, started-out as an email...)
85 Over time, we put a lot of effort in the configure, make, distribute
86 system (CMDS) for LilyPond. Some months ago, we realised it was not
87 standard GNU --- we require GNU make for building, and Python for extra
88 scripting. In an effort to be more GNU, we tried automake, but after two
89 weeks we realised the costs were too high for us and we reverted to our
90 own system (see file(automake.urgh)). Not long after that i was confronted
91 with two other packages that lacked a decent CMDS. I realised that Lily's
92 would be perfect, it's modular and easy. The only problem was to make a
93 clean cut between generic and Lily specific stuff. The result was
94 StepMake: a bunch of generic makefiles, found in:
96 stepmake/stepmake/*.make
98 eneric helper scripts:
103 and modular configure functions:
105 stepmake/configure.in
107 stepmake/config.hh.in
108 stepmake/config.make.in
111 Of course, every package has its own configure- and make peculiarities.
112 The best way to create the configure scripts is to copy them from
113 nop(stepmake)footnote(Actually, stepmake/bin/stepmakeise.sh will do
114 that for you.) into you package's toplevel directory. For most
115 packages, you'll only have to comment in/out some functions in
118 Package specific makefiles go in:
124 and are included by the generic StepMake makefiles.
128 If you want to make and manage (binary) distributions, create and apply
129 patches, you'll need some framework that's outside of the package's
131 For a number of simple maintenance tasks, StepMake will therefore assume
132 the following directory structure:
134 includefile(../layout.yo)
136 Check and update the layout with the command:
138 ./stepmake/bin/stepdirs.sh
147 Stepmake comes with a number of precooked configure functions for
148 general needs, such as AC_STEPMAKE_COMPILE for simple C development
149 and AC_STEPMAKE_CXX for C++.
151 See configure.in and comment in/out the functions that your package
152 needs. For specific needs, you can write your own autoconf code,
153 see code(info autoconf).
157 nemail(Jan Nieuwenhuizen)(janneke@gnu.org)
159 nemail(Han-Wen Nienhuys)(hanwen@cs.uu.nl)