On Mon, 2009-01-12 at 10:41 -0500, Beeton, Carolyn (CAR:9D60) wrote:

> If you send instructions I will update the site.  It is a useful way of
> communicating xmlrpc interfaces, and it currently very out-of-date.

This offer got me to clean up and check in the tools I had for updating
the site.  In the process I fixed the stylesheet problem, so it's no
longer served in invisible ink :-).

If you check out (or update) a working copy from the svn repo:

 https://egret.us.nortel.com/rep/buildloop/main

(I check it out using git as usual into ~/Work/buildloop , but it
_shouldn't_ matter), you'll find in there a 'projectServer' directory.
In that directory you'll find a Makefile that has targets for updating
the pub, temp, and doc directories and some assorted files.

The doc directory is updated from the projectServer directory with the
command:

   make doc-update DOCDIR=/home/INST-SDL/xecs-patch/share/doc/sipxecs/

where DOCDIR points to the documentation directory created by doing an
install from source locally.  In the case above
SIPX_INSTALLDIR=/home/INST-SDL/xecs-patch .
That command generates a couple of header and footer files, transforms
the doxygen output files to fix the hyperlinks, and uploads them to the
site.  

I have not fixed this up so that git and svn ignore the files it
generates in the source tree, but 'make clean' gets rid of them.

If nothing else, it should be easy to add a file to the top level of the
documentation directory that is installed that has the SVN version it
was built from in it.

If you want to get fancier and support multiple versions on the site,
that's ok with me too.

I'm happy to review any changes you'd like to make.

_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev

Reply via email to