Обсуждение: Docs on web site
Hi Vince. I've put the 7.1 docs on the web site in the appropriate place. Nice auto-generating web page stuff btw. I modified and compiled *but did not check into cvs* build.c to get nice references for the new Developer's and Reference docs. OK? If you want to inspect the changes, then commit (or tell me to) that would be great. TIA - Thomas The web site itself seems very slow at the moment; some robot process is chewing up lots of CPU so perhaps that is the reason. hub.org (which may actually be a different machine) is quite fast otherwise.
On Fri, 20 Apr 2001, Thomas Lockhart wrote: > Hi Vince. I've put the 7.1 docs on the web site in the appropriate > place. Nice auto-generating web page stuff btw. > > I modified and compiled *but did not check into cvs* build.c to get nice > references for the new Developer's and Reference docs. I never had buildmenu.c checked in. What did you modify? I didn't see anything noticable. Anyway unless new filetypes are being introduced you only need to run makeindex with the current release version number. eg.. $ makeindex 7.1 And it'll find all files and create the index with the 7.1 link. > OK? If you want to inspect the changes, then commit (or tell me to) that > would be great. TIA > > - Thomas > > The web site itself seems very slow at the moment; some robot process is > chewing up lots of CPU so perhaps that is the reason. hub.org (which may > actually be a different machine) is quite fast otherwise. We're working on that too. Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com http://www.pop4.net 56K Nationwide Dialup from $16.00/mo atPop4 Networking Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ==========================================================================
> > I modified and compiled *but did not check into cvs* build.c to get nice > > references for the new Developer's and Reference docs. > I never had buildmenu.c checked in. What did you modify? I didn't > see anything noticable. Anyway unless new filetypes are being introduced > you only need to run makeindex with the current release version number. > eg.. There are two new documents (formed by splitting some info from the original ones): o Reference Manual o Developer's Guide If we check buildmenu.c into cvs then we can check for differences ;) > $ makeindex 7.1 Right. Worked great, except for needing the small additions to buildmenu to adjust names. > And it'll find all files and create the index with the 7.1 link. Yeah, neat feature. - Thomas