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
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
|
=pod
README for example pd external package 'hello'
Last updated for hello v0.01
=head1 DESCRIPTION
The 'hello' package is an example external package intended
to demonstrate one way of using GNU autotools (automake, autoconf, autoheader)
to manage a Pd external distribution.
See L</"HOWTO"> for a developer-oriented introduction.
=head1 INSTALLATION
Issue the following commands to the shell:
cd PACKAGE-XX.YY (or wherever you extracted the distribution)
./configure
make
make install
=head1 CONFIGURATION OPTIONS
The 'configure' script supports the following options, among others:
=over 4
=item * --help
Output a brief usage summary of the 'configure' script,
including a list of supported options and influential
environment variables.
=item * --enable-debug , --disable-debug
Whether to enable verbose debugging messages.
Default=no.
=item * --with-pd-dir=PD_DIR
Set base Pd directory. Default PREFIX/pd
=item * --with-pd-include=PD_INC
Where to look for m_pd.h
=item * --with-pd-extdir=PD_EXTERNS
Where to install compiled externals. Default: PD_DIR/externs
=item * --enable-object-externals , --disable-object-externals
Whether to build single-object externals or only multilibs (default),
for packages which support both.
=back
=head1 HOWTO
This section provides a brief developer-oriented description of
how to use GNU autotools to manage your own Pd external package.
=head2 Files
=over 4
=item $(top_srcdir)/common
The directory common/ includes common code for the autotools packages.
Copy it to your top-level package directory.
=item $(top_srcdir)/common/m4
Contains m4 macros for autotools.
See L</"ax_pd_external.m4"> for details.
=item $(top_srcdir)/common/pdexternal.am
May be included in your package's Makefile.am.
See L</"pdexternal.am"> for details.
=item $(top_srcdir)/common/mooPdUtils.h (optional)
The file mooPdUtils.h may be included by your C source files.
Currently, this only provides a PDEXT_UNUSED macro to avoid annoying
gcc warnings under -W.
=back
=head2 Running aclocal
You must pass the "-I common/m4" flag to aclocal when you call it.
For maintainer-mode rebuilding and autoreconf, you should add
the following to your top-level Makefile.am:
ACLOCAL_AMFLAGS = -I $(top_srcdir)/common/m4
See the example package's autogen.sh for a useful wrapper script.
=head2 configure.ac
You must call the macro AX_PD_EXTERNAL from configure.ac.
Before doing so (and before calling AC_PROG_CC), make sure
that you cache the values of important user flags in shell
variables:
##-- save user's CFLAGS,CPPFLAGS
UCPPFLAGS="$CPPFLAGS"
UCFLAGS="$CFLAGS"
ULDFLAGS="$LDFLAGS"
##-- Pd external stuff
AX_PD_EXTERNAL
See the example package's configure.ac for a complete working example.
=head2 Makefile.am
You probably want to include $(top_srcdir)/common/pdexternal.am in
your Makefile.am(s). This will allow you to build Pd externals
as "_PROGRAMS" targets. In particular, pdext_PROGRAMS targets
will be built as externals and installed in PDEXT_DIR (see above).
See the example package's Makefile.am for a complete working example.
=over 4
=item Externals
To build & install the external "hello.$(PDEXT)", add the
following to Makefile.am:
pdexterns_PROGRAMS = hello
hello_SOURCES = hello.c mooPdUtils.h
=item Abstractions
To install the abstraction "heynow.pd", add the
following to Makefile.am:
pdexterns_DATA = heynow.pd
=item Documentation
To install the documentation patch "hello-help.pd", add the
following to Makefile.am:
pddoc_DATA = hello-help.pd
=back
=cut
=pod
=head2 ax_pd_external.m4
The AX_PD_EXTERNAL macro defined in common/m4/ax_pd_external.m4
is intended to perform all common autoconf-level
checks and substitutions necessary for building Pd external packages on
various systems. Among other things, this includes:
=over 4
=item *
Providing --with-FEATURE and --enable-FEATURE arguments such as
--with-pd-dir (see L</"CONFIGURATION OPTIONS">, above).
=item *
Defining automake-style "Xdir" variables for easy definition
of package externals, abstractions, and documentation.
=item *
Checking for the required header "m_pd.h".
=item *
Defining platform-dependent compiler and linker flags for
building Pd externals, and adding these to the relevant
system variables (CPPFLAGS, CFLAGS, LDFLAGS, etc.)
=back
See the comments at the top of m4/ax_pd_external.m4 for
more details on the AX_PD_EXTERNAL macro.
=head2 pdexternal.am
pdexternal.am is intended to be included in your package's Makefile.am.
It redefines the automake EXEEXT to allow building Pd externals using
automake's _PROGRAMS targets. Additionally, it defines the
automake varibles PDEXT, SUFFIXES, EXTRA_DIST, CLEANFILES, DISTCLEANFILES,
and MAINTAINERCLEANFILES.
=head2 Multilibs and Single-Object Externals
You can use automake's EXTRA_PROGRAMS variable, together
with the pdexterns_PROGRAMS automake target, the automake conditional
WANT_OBJECT_EXTERNALS, and the C preprocessor macro WANT_OBJECT_EXTERNALS
to allow building single-object-externals or multilibs from a single
source distribution.
Makefile.am should contain something like:
##-- always build these externals
pdexterns_PROGRAMS = hello
##-- potential single-object externals (as _PROGRAMS)
EXTRA_PROGRAMS = goodbye
##-- build single-object externals?
if WANT_OBJECT_EXTERNALS
pdexterns_PROGRAMS += goodbye
endif
If single-object externals were requested by the user,
then the C preprocessor macro WANT_OBJECT_EXTERNALS will be defined
by autoheader, to allow you to
conditionally #include<> the EXTRA_PROGRAMS sources in your
top-level multilib source file if desired. In the above example,
hello.c might contain:
#ifdef HAVE_CONFIG_H
# include "config.h"
#endif
#ifndef WANT_OBJECT_EXTERNALS
/*-- Multilib build: include source for the goodbye external --*/
# include "goodbye.c"
#endif
/*... local definitions etc. go here ...*/
void hello_setup(void)
{
#ifndef WANT_OBJECT_EXTERNALS
goodbye_setup();
#endif
/*... local setup code goes here ...*/
}
=cut
=pod
=head1 ACKNOWLEDGEMENTS
PD by Miller Puckette and others.
=head1 AUTHOR
Bryan Jurish E<lt>moocow@ling.uni-potsdam.deE<gt>
|
