CCP4 Pages for Developers

Nightly builds

• Most recent working builds from Buildbot
• Buildbot status
• Daily snapshot of the CCP4 suite

Source code

• Building instructions
• CCP4Forge portal

Project documents

• Developers' Meeting 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011
• New CCP4 Software Library (January 2002)
• Developer's Guide to Upgrading Programs to CCP4 5.0 Libraries (March 2004)
• Kevin Cowtan's Clipper libraries for reflection data (February 2001)
• Change of CCP4 working co-ordinate format to mmCIF subset (updated Jun 1999)

Bulletin board

• ccp4-dev - The Developers Mailing List

Miscellaneous

• A quick guide to using Bazaar [pdf] (April 2014)
• A presentation on CCP4 nightly builds, updates and tests [pdf] (April 2014)
• Users guide and Developers Guide to Missing Number Flags in MTZ files (old)
• Repository of X-ray crystallographic datasets from the Joint Center for Structural Genomics
• Test Data at Autostruct/CCP4
• CCP4i Developers Resource page
• Templates for using CCP4 library routines (September 1998)
• How to Write CCP4 Documentation [pdf] (February 1998)

• Information for CCP4 RAL Staff (restricted access)

Bugs and features

The usual way to report bugs or request new features is by email to ccp4@ccp4.ac.uk.

However, developers may take a more active approach by submitting reports and requests on the CCP4Forge site. If a tracker for the component in question is already set up, please use it. Otherwise, use one of the general trackers for series-65.

After the requested changes have gone out to nightly builds and are tested, an update request should be placed on the updates tracker, as described on the Project Home Page under the section Updates Tracker.