untu), but still it
> would be useful to see if you can reproduce the problem with version
> 1.8.9.1. I'm not familiar with a program called "doxygen-latex
> 1.8.7-2~precise1". The version of Texlive is also a bit old but I don't
> think the problem comes from this.
Hi.
Recently (although my installation is quite old) I
haven't been able to produce PDF output with
doxygen.
The reason is pdftex always complains of undefined
control sequences. After looking at the errors and
the .tex files, it seems that most of C macros got
a \+
You are right.
It's even in the documentation in the "Preprocessing" section.
2014/1/9 Richard Damon
> On 1/9/14, 7:07 AM, Thomas Nemeth wrote:
> >
> > Hi.
> >
> > I'm documenting some structures that looks like this :
> >
&
Hi.
I'm documenting some structures that looks like this :
/*! Dataset for status data. */
typedef struct __attribute__ ((__packed__)) {
UINT16 outputs; /*!< Board outputs. */
UINT32 inputs; /*!< Board inputs. */
UINT16 status; /*!< Board status. */
UINT1
to be enclosed in a doxygen comment
> block but
>
> /**
> Your comment here
> */
>
> Would this suit your needs.
>
> Paul
>
>
> On Mon, Jan 6, 2014 at 8:50 AM, Thomas Nemeth wrote:
>
>> Hi Albert.
>>
>> I'm sorry not beeing clear enough
tension
mapping...
Thanks.
Thomas.
2014/1/6 Albert
> Hi Thomas,
>
> It is not 100% clear what you want to achieve, but have you looked at
> EXTENSION_MAPPING and at the markdown possibilities?
>
> Albert
>
>
> On Mon, Jan 6, 2014 at 2:56 PM, Thomas Nemeth wrote:
>
>
Hi.
I'd like to include in my projects documentation, some doxygen
documentation
that lies in a non-source-code file (eg: .txt). Up to new I had to
manually
copy/paste (well, not really manually, but using head/cat/tail using a
makefile)
into a .h file so that the titlepage and
