Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Wed, Jul 6, 2011 at 9:32 AM, Matthew Gillen <me at mattgillen.net> wrote: > On 07/05/2011 09:27 PM, Stephen Adler wrote: > > Guys, > > > > I want to use an automated web'izing documentation tool like doxygen for > > a software project I'm working on. I'm wondering what's the use case for > > this is. What I mean by use case is the way one adds the html generation > > into the software development cycle. This question may be too simplistic > > but maybe there are some general rules which would make life easy for me > > that I wouldn't think of when I start using a tool like doxygen. For > > example, does one only generate html documentation output when one > > prepares the code for a release or version tag? Does one include a > > documentation target in the make file so one can type 'make > > documentation' How often do you generate the documentation? After each > > make? etc. etc. If there is a web resource I should read through, I'd > > greatly appreciate the url and any comments you guys may have. > <http://lists.blu.org/mailman/listinfo/discuss> > The last time I setup a dev environment I used phpDocumentor I set a nightly cron job to generate the documentation for various source trees and publish those to a 'docs.example.net' location
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |