[avr-libc-dev] [bug #36933] Documentation no longer correctly describes how to declare strings for storage in program memory

Update of bug #36933 (project avr-libc): Percent Complete: 80% => 100% Open/Closed:Open => Closed ___ Reply to this item at:

[avr-libc-dev] [bug #43261] symbols in documentation are getting their leading and trailing "__" stripped by doxygen

Update of bug #43261 (project avr-libc): Assigned to:None => elderling ___ Reply to this item at: ___

[avr-libc-dev] [bug #43261] symbols in documentation are getting their leading and trailing "__" stripped by doxygen

Update of bug #43261 (project avr-libc): Percent Complete: 0% => 80% ___ Follow-up Comment #1: Generating the documentation with doxygen 1.8.11 appears to resolve this issue completely.

[avr-libc-dev] Generating and Publishing AVR-Libc Documentation

Hello Developers! While working on bug #43261: symbols in documentation are getting their leading and trailing "__" stripped by doxygen I confirmed that the problem was with doxygen. I also noticed that Using the GNU tools

[avr-libc-dev] [bug #43104] Index is missing from online documentation

Update of bug #43104 (project avr-libc): Assigned to:None => elderling ___ Reply to this item at: ___

[avr-libc-dev] [bug #35399] User manual on website has incomplete alphabetical index

Update of bug #35399 (project avr-libc): Assigned to:None => elderling ___ Reply to this item at: ___

[avr-libc-dev] [bug #38037] "Building and Installing" needs round-up

Update of bug #38037 (project avr-libc): Assigned to:None => elderling ___ Reply to this item at: ___

[avr-libc-dev] [bug #43104] Index is missing from online documentation

Update of bug #43104 (project avr-libc): Status:None => Duplicate Open/Closed:Open => Closed ___ Follow-up Comment #1: This is a duplicat

[avr-libc-dev] [bug #43261] symbols in documentation are getting their leading and trailing "__" stripped by doxygen

Follow-up Comment #2, bug #43261 (project avr-libc): I can see the CVS repo where the documentation is stored, but I don't know whether it is acceptable for me to change it. Furthermore, if it OK for me to change it, I don't know if I should regenerate all of the documentation or just the broken f

Re: [avr-libc-dev] Generating and Publishing AVR-Libc Documentation

Hi Jonathan, many thanks for your work on the documentation! As Jonathan Taylor wrote: > What is the process for (re)generating and publishing documentation to > http://www.nongnu.org/avr-libc ? It's unfortunately a little complicated, as it still requires the use of CVS, and quite a bit of tw

Re: [avr-libc-dev] [bug #43261] symbols in documentation are getting their leading and trailing "__" stripped by doxygen

As Jonathan W. Taylor wrote: > Furthermore, if it OK for me to > change it, I don't know if I should regenerate all of the documentation or > just the broken files. Re-importing everything is the better way for sure. -- cheers, Joerg .-.-. --... ...-- -.. . DL8DTL http://www.

Re: [avr-libc-dev] Generating and Publishing AVR-Libc Documentation

Citing that CVS document: > cvs [-z3] [-n] -d $use...@cvs.savannah.nongnu.org:/web/avr-libc \ > import avr-libc/user-manual AVR-LIBC $release > > The meta variable $userid is (obviously) your User ID on savannah, > while $release is the symbolic release tag. While this tag is mostly > unimporta