Developer's Documentation
How to download from the SourceForge CVS
You can download the latest (but not necessarily greatest) version of Pd and the externals packages from the SourceForge CVS. This is not for the unexperienced. You will only need to do this if you are a developer, or you are beta testing a new feature or external.
Directory Layout for Developers
This is the standard layout that Pd developers use so that all of the Makefiles, etc. are looking in the right places.
Repository Sections
The code repository is divided into various sections, this is a description of the sections.
Code Guidelines
Some guidelines for working with the Pd CVS repository and Pd-extended builds.
Joining the SourceForge Project
The Pure Data community is made up of many developers. Almost everyone who uses Pd is a developer, writing patches, externals, or contributing to the core. The Pure-Data SourceForge project was set up to provide a space for all Pd developers to contribute their work.
Adding your work to the Pd-extended Build System
The Pd-extended build system is a unified, cross-platform Pd-extended build system which aims to assemble as much of the contents of the CVS into an easy-to-install package on as many platforms as possible.
Building Pd
Building for GNU/Linux using Debian
Building for GNU/Linux using Fedora, RedHat and related distros
Building for Mac OS X using Developer Tools and Fink
Building for Windows using MinGW
Build Pd from source using MinGW and MSYS.
Pure Data の external を Borland C++ 5.5 で コンパイルする
Building Pd Externals with Borland C++ 5.5.
Packaging Pd
Building Debian .deb packages
There are debian packages for most of the code in Pd. Here is how its done.
MacOS X Pd.app building
This is how to build your own Pd.app.
Windows Installer
Here's how to build your own Windows installer from source.
Pd Internals
Pd API
A wiki to document the Pd API.
Pd Source Notes
Notes on the structure and form of the Pd source code.
Pd File Format
Miller Puckette's paper on Pd file format.
Unofficial Documentation of Pd file format
Libdir
I wrote up some documentation of the proposed libdir format for libraries of Pd patches. And with the introduction of Thomas' loader patch, this format makes sense for objects written in other languages as well:
Pd Externals
Pd Externals Howto
This is the HOWTO that taught many of the current Pd developers how to write Pd objects. The first place to start when coding your own Pd objects in C.
flext
a C++ layer for cross-platform development of Pd and Max/MSP objects. There's also an introduction into flext in PDF format
Using gdb to debug Pd externals
gdb is extremely handy for tracking down all the bugs in your code