I’m on the CSOUND-DEV list, but the earliest I’d be able to look into automatically generating and updating the Doxygen documentation is next week (and that’s optimistic). If anyone wants to take a stab at this in the meantime, the way I’d go about it is with Travis CI deployment , most likely a custom deployment 

If we can build these with travis and place them on the website directly, we should also consider doing the same with the manual that is already being built by travis.

In fact, if travis can be used as a build farm,
we should exploit ways in which it could be used to give us a linux package to 
distribute.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 2 Feb 2017, at 00:48, Nate Whetsell  wrote:
> 
> I’m on the CSOUND-DEV list, but the earliest I’d be able to look into automatically generating and updating the Doxygen documentation is next week (and that’s optimistic). If anyone wants to take a stab at this in the meantime, the way I’d go about it is with Travis CI deployment , most likely a custom deployment