Thread: [Doxygen-develop] (no subject)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

-- 
José Luis Zabalza
jlz...@ca...
Linux User 172551

Hi,                                                                             

  My school teaches programming using C++, but to simplify its use it has  
defined a bunch of new 'keywords' using #define. 
(As is shown on the following website: http://www.cis.ohio-
state.edu/~weide/sce/rcpp/RESOLVE_Catalog-HTML/AT/Array/Are_In_Order_At.html 
Believe it or not, that is valid C++)

I'd like to use Doxygen on such code, but there are several problems.
Doxygen gets confused when keywords are aliased using #define, as when the 
keyword 'class' (as used in templates) is aliased to the word 
as 'concrete_instance', then Doxygen will merge the new keyword with the 
following word.

This problem will not go away even if I enable macro preprocessing.
Does anyone else encounter the same problem or even the need to have it 
addressed?

Now, I realize that I could write a source filter to 'convert' the files to 
proper C++ before using doxygen on them. This raises another problem.

The filter is shared both by the input to doxygen's processing, and to the 
syntax hiliter. So, it would be nice if the syntax hilighter was pluggable (so 
that we could highlight our own parts of the source code), and different from 
the one used for processing.

I'd be willing to write the necessary changes myself, if I found that there was 
any interest in them.

Thank you for hearing me out,
-Eugene Talagrand

Hi All,

  I'm having an odd problem here. I built on Solaris 8 after fixing 1.3 so
that &trade; would work, and when I run doxygen I get:

Generating code for file vvxtrAPI.h...
Segmentation Fault (core dumped)

This is the first file it is trying to generate code for. The changes I
made are trivial, since there was already handling for &tm;, which I
changed to the HTML form of &trade;. The original binary I downloaded from
the site runs on this source code no problem, but the previous build I had
made (1.2.16) had just started seg-faulting on a different source tree. :(

My first response was to try to debug it, and the problem went away--when
I compile with -g the seg-fault doesn't happen. I've tried various levels
of optimization, but only -g makes it work.

If anyone has seen this before, please let me know; for now, I'm just
generating documentation with the debug build. :(  If I have a chance and
I don't hear anything from the list, I'll try digging around a bit more.
Probably an initialization problem, but who knows.

Tim

Is there some reason why \relates and \relatesalso cannot be used with 
a macro (i.e. inside a \def block)? I am willing to write the code and 
submit a patch if it is pretty straight forward.

Hi,

Pardon for the cross post from doxygen-users, but does anybody know of an
existing PPA that packages recent versions of Doxygen for older Ubuntu
releases? I'm most interested in getting 1.8.3 onto x86 and x64 machines
running precise.

Thanks for any tips.

Liam

On 25 April 2013 17:30, Liam Staskawicz <ls...@gm...> wrote:
> Hi,
>
> Pardon for the cross post from doxygen-users, but does anybody know of an
> existing PPA that packages recent versions of Doxygen for older Ubuntu
> releases? I'm most interested in getting 1.8.3 onto x86 and x64 machines
> running precise.
>

Hi, I would suggest you to just to download source code and compile.
You can either download tarball or use svn, in the last months I'm
using the latest version from svn and it's working properly and if not
you will help to discover bug. I have no problems with compilation
since I have all the required libraries anyway. Only problem is that
you need to add the new doxygen bin directory to PATH and update
manually. I'm using Ubuntu 10.04 (64bit) and 12.04 (32bit). All the
information you need is here:

http://www.stack.nl/~dimitri/doxygen/download.html

Vaclav

> Thanks for any tips.
>
> Liam
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
> _______________________________________________
> Doxygen-develop mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-develop
>

Hi Vaclav - thanks for your response.

I should have specified - I can definitely compile successfully from
source, so this request comes from the following motivations:

   - I am creating build configurations so a machine can have a full
   development environment installed (including doxygen) from scratch in an
   automated way, for both build slaves and for new developers on my project
   - automating subsequent upgrades on these machines is much easier if I
   can use the system package manager

I've never set up a PPA before, and do not regularly develop on a Linux
machine, so I was holding out some hope that this had been done and I just
couldn't find info about it :) But I may just have to dive in and try it
myself.

Liam

On Tue, Apr 30, 2013 at 2:33 AM, Vaclav Petras <wen...@gm...> wrote:

> On 25 April 2013 17:30, Liam Staskawicz <ls...@gm...> wrote:
> > Hi,
> >
> > Pardon for the cross post from doxygen-users, but does anybody know of an
> > existing PPA that packages recent versions of Doxygen for older Ubuntu
> > releases? I'm most interested in getting 1.8.3 onto x86 and x64 machines
> > running precise.
> >
>
> Hi, I would suggest you to just to download source code and compile.
> You can either download tarball or use svn, in the last months I'm
> using the latest version from svn and it's working properly and if not
> you will help to discover bug. I have no problems with compilation
> since I have all the required libraries anyway. Only problem is that
> you need to add the new doxygen bin directory to PATH and update
> manually. I'm using Ubuntu 10.04 (64bit) and 12.04 (32bit). All the
> information you need is here:
>
> http://www.stack.nl/~dimitri/doxygen/download.html
>
> Vaclav
>
> > Thanks for any tips.
> >
> > Liam
> >
> >
> ------------------------------------------------------------------------------
> > Try New Relic Now & We'll Send You this Cool Shirt
> > New Relic is the only SaaS-based application performance monitoring
> service
> > that delivers powerful full stack analytics. Optimize and monitor your
> > browser, app, & servers with just a few lines of code. Try New Relic
> > and get this awesome Nerd Life shirt!
> http://p.sf.net/sfu/newrelic_d2d_apr
> > _______________________________________________
> > Doxygen-develop mailing list
> > Dox...@li...
> > https://lists.sourceforge.net/lists/listinfo/doxygen-develop
> >
>

>
>
>
> I should have specified - I can definitely compile successfully from
> source, so this request comes from the following motivations:
>
>    - I am creating build configurations so a machine can have a full
>    development environment installed (including doxygen) from scratch in an
>    automated way, for both build slaves and for new developers on my project
>    - automating subsequent upgrades on these machines is much easier if I
>    can use the system package manager
>
> I've never set up a PPA before, and do not regularly develop on a Linux
> machine, so I was holding out some hope that this had been done and I just
> couldn't find info about it :) But I may just have to dive in and try it
> myself.
>
>
> I've been looking at installing jenkins on openshift to "build" doxygen
remotely..
deb package et all

pete