avr-libc man pages in win-avr

Go To Last Post
4 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

They don't seem to have been generated right:

.TH "interrupt.h" 3 "15 May 2007" "Version 1.4.6" "avr-libc" \" -*- nroff -*-
.ad l
.nh
.SH NAME
interrupt.h \- 
.SH "Detailed Description"
.PP 
@{ 
.SH SYNOPSIS
.br
.PP
.SS "Global manipulation of the interrupt flag"
The global interrupt flag is maintained in the I bit of the status register (SREG). 
.in +1c
.ti -1c
.RI "#define \fBsei\fP()"
.br
.ti -1c
.RI "#define \fBcli\fP()"
.br
.in -1c
.SS "Macros for writing interrupt handler functions"

.in +1c
.ti -1c
.RI "#define \fBISR\fP(vector)"
.br
.ti -1c
.RI "#define \fBSIGNAL\fP(vector)"
.br
.ti -1c
.RI "#define \fBEMPTY_INTERRUPT\fP(vector)"
.br
.ti -1c
.RI "#define \fBISR_ALIAS\fP(vector, target_vector)"
.br
.in -1c
.SH "Author"
.PP 
Generated automatically by Doxygen for avr-libc from the source code.

:( Is this an avr-libc problem, or winavr compilation problem?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hard to say.

It could very well be an issue with compiling it for MinGW (Windows). But the problem is that there is no "man" command/program on Windows to display the pages anyhow, so it never has really mattered. I've recently found out that there might be a strong possibility to have "man" available for MinGW, so this might be useful in the future.

But the best thing to do is to build the same version of avr-libc on Linux, and then compare the output and see what's different.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

This is (to some degree) a doxygen issue it seems. The Unix
man page look the same. Somehow, doxygen appears to get confused
by the topic grouping used when generating man pages.

Jörg Wunsch

Please don't send me PMs, use email if you want to approach me personally.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Ah righty. The code editor I'm using has a man pages viewer, which is quite useful for quickly looking up avr-libc documentation. Or at least it would be...

Thanks for looking at it anyway.