9 dec 2012 kl. 16:31 skrev Andreas Granig <[email protected]>:

> Hi Olle,
> 
> What's the exact problem?
> 
> I installed GCC::TranslationUnit, applied the patch and called "make -C
> ./doc/cfg_list all", which resulted in this:
> 
> $ ls ./doc/cfg_list
> cfg_carrierroute.txt  cfg_maxfwd.txt     cfg_tcp.txt  Makefile
> cfg_core.txt          cfg_registrar.txt  cfg_tls.txt
> cfg_dispatcher.txt    cfg_sctp.txt       cfg_tm.txt
> cfg_malloc_test.txt   cfg_siputils.txt   docbook
> 
> and the content seems just fine.
Wow. It crashes badly on my OS/X system. Guess I will have to try somewhere 
else. Something with sed and then perl.

/O

> 
> Andreas
> 
> On 12/09/2012 03:56 PM, Olle E. Johansson wrote:
>> Hi!
>> 
>> The scripts to update cfg, select and RPC docs in  /doc/scripts/cdefs2doc 
>> doesn't work for me. Even though I replace the andrei directory reference 
>> with a local one and install the modules, it fails to work. Anyone that can 
>> update these and produce a working version, so that we can update the 
>> reference docs?
>> 
>> The scripts is using an in-source code documentation that may be documented 
>> somewhere, but it seems to be the way to get all RPCs and selects 
>> documentat, so I would like to be able to run it - possibly automatically 
>> for -dev version, like doxygen.
>> 
>> But the first step would be to run it and update docs for the coming release 
>> :-)
>> 
>> The perl scripts are in /doc/scripts and are called from various makefiles 
>> under /doc.
>> 
>> Thank you for your help! I failed miserably...
>> 
>> /O ;-)
>> 
>> 
>> _______________________________________________
>> sr-dev mailing list
>> [email protected]
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>> 
> 
> _______________________________________________
> sr-dev mailing list
> [email protected]
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev


_______________________________________________
sr-dev mailing list
[email protected]
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

Reply via email to