New Build System

AndiVajda presented the work he had done to move to a new build system where 3rd partly packages will no longer live in our CVS tree.

Attendees: HeikkiToivonen, MorgenSagen, MarkJaffe, LisaDusseault.

• All external libraries will be available as source and binary tarballs.
• To develop Chandler, most people will not need to build - they just download the binaries
• If you need to build, third party build is in /external. Do |make expand|, |make| to build (will download source tarballs as appropriate)
• Where we make no changes or minor changes, we will have diffs in /external along with the makefiles to make things happen
• Where we anticipate we will be making lots of changes, essentially forking a library, we will keep the source in our tree. Somewhere under /osaf.

ACTION ITEMS:

• Andi to post message to dev about the current stuff
• Mark & Heikki to take over new system
  • New documentation for new build system
  • Document all build requirements (disc space, needed cygwin tools, ...)
  • |make install| for /external
  • flatten /osaf/chandler/Chandler to /osaf/chandler?
  • Move UUID out from /Chandler (so that /Chandler would have purely Python stuff)?
  • Update process for upgraded libs: send source tarball to Mark who will produce official binaries and make a seamless upgrade for everyone - this may need to be automated with some staging tinderbox at some point
  • Webtools changes - Tinderbox, Bonsai, LXR
• Do wx migration first before flipping the switch on the new build system (but those who want can start using the new system now)
• Andi (or Mark/Heikki) to give an IRC preso about the new system

-- HeikkiToivonen - 24 Mar 2004