[openbeos] Re: BeBook license
- From: "Matthijs Hollemans" <matthijs@xxxxxxxxxxxxxxxxxxx>
- To: <openbeos@xxxxxxxxxxxxx>
- Date: Mon, 16 Jun 2003 16:57:47 +0200
> [...] When we want to create our own developer
> documentation [...]
BTW, I forgot to mention that I started a Doxygen-based documentation
"project" a while back.
It is in the OpenBeOS repository at:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/open-beos/current/docs/user/
Right now, this only contains the Midi Kit documentation. You can build
the docs by opening a Terminal, going to your local /current/docs/user/
directory, and typing "doxygen". The HTML output files end up in
/current/distro/x86.R1/beos/docs.
Of course, you need to have Doxygen installed for this to work. Also see
the HOWTO file in that folder.
I don't know if this is going to be the "official" OpenBeOS
documentation -- there are some drawbacks to using this method -- but
at least it is a start.
-Matthijs
- References:
- [openbeos] BeBook license
- From: Niels Reedijk
Other related posts:
- » [openbeos] BeBook license
- » [openbeos] Re: BeBook license
- » [openbeos] Re: BeBook license
- » [openbeos] Re: BeBook license
- » [openbeos] Re: BeBook license
- » [openbeos] Re: BeBook license
- » [openbeos] Re: BeBook license
- » [openbeos] Re: BeBook license
- » [openbeos] Re: BeBook license
- » [openbeos] Re: BeBook license
- » [openbeos] Re: BeBook license
- » [openbeos] Re: BeBook license
- » [openbeos] Re: BeBook license
- » [openbeos] Re: BeBook license
- » [openbeos] Re: BeBook license
- » [openbeos] Re: BeBook license
- [openbeos] BeBook license
- From: Niels Reedijk