On Mon, 1 Oct 2007 08:54:49 -0500 "Nathan Ingersoll" <[EMAIL PROTECTED]> wrote:
> On 10/1/07, Gustavo Sverzut Barbieri <[EMAIL PROTECTED]> wrote: > > On 10/1/07, Nathan Ingersoll <[EMAIL PROTECTED]> wrote: > > > Are these docs generated from the code? If so, they could > > > probably be added to run after the doxygen stuff on the e.org web > > > server. > > > > Kind of. They're generated from the final binaries. You first > > compile the "Pyrex" into C, then compile C into a shared object > > and then it "import module" and do the introspection to extract > > those. The generator I'm using is "epydoc", think of it as the > > python version of doxygen. > > > > As recently we switched from Pyrex to Cython (a fork, with more > > features and less bugs) and now we depend on the yet unreleased > > version (from their Mercurial repo), we're thinking about providing > > ".c" in the repository. That means we would require just a C > > compiler on that machine. Is that ok? > > It would probably be best to run this as part of the nightly build > process. A gendoc script is supported for generating docs by nightly build process. Nothing in done with the docs other than leaving them in the install directory, but links or something could be arranged.
signature.asc
Description: PGP signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
