Rolf Hemmerling | 24 Jan 10:51 2015

Doxygen 1.8.9 on Win8.1 "Error: Reference source not found" in refman.

Hello,

a)
with RTF output of Doxygen 1.8.9 on english Windows 8.1, there is the 
problem in the file refman.rtf

> File Index
> 	File List
> Here is a list of all documented files with brief descriptions:
> C:/Users/Public/projects_local/hemmerling/hemmerling_pwendean_keil/src/getline.c (Line
Edited Character Input for the application "Paketwendeanlage" ) 	Error: Reference source not found

while of course Doxygen was/is processing all the mentioned files, 
successfully ( as shown by the HTML output, and the logging ).

If I move the "refman.rtf" file to another *german* Windows 7, the error 
message even changes to German language "Fehler: Referenz nicht gefunden".

There is nothing special with the files, or the file location. I did not 
include special informations in the parsed files to handle the "File 
list" section.

b)
I found a description of this kind of bug here

"Don’t Let Word Get You Down, With “Error! Reference Source Not Found”
http://www.turbolaw.com/blog/2007/10/05/dont-let-word-get-you-down-with-error-reference-source-not-found/

So I would be pleased about an improved software update :-).

(Continue reading)

Rolf Hemmerling | 24 Jan 10:32 2015
Picon
Picon

Doxygen 1.8.9 on Win8.1 is "swallowing" some (expected) characters in the log

Hello,

Some output of Doxygen 1.8.9 on Win8.1 is "missing", see

**************
> Combining RTF output...
> lookup cache used 44/65536 hits=71 misses=44
> finished...
> irq.c is not documented.
--^
There is never a file "irq.c" in the directory, but just "sioirq.c".
> C:/Users/Public/projects_local/hemmerling/hemmerling_pwendean_keil/src/sioirq.c:50:
warning: Member oend (variable) of file sioirq.c is not documented.
--^
Here and everyelse, "sioirq.c" is properly displayed.
*************

This means that Doxygen at that point is "swallowing" some characters in 
the output to the log file.

Maybe it is a typical "buffer problem", as known from such legacy 
software ( 1997 was initial release according to Wikipedia ), and so 
maybe the indication of much bigger fault.

I didn´t check the Doxygen source code for the bug.
I would be pleased if you can fix it, anyhow.

** Anyhow I think Doxygen is really-great software, thanks for 
development + free license **

(Continue reading)

Zheng, Bangyou | 13 Jan 06:12 2015
Picon

Cannot work with salt of plantuml

Hi All,

I am using latest version of doxygen 1.8.9.1 and plantuml 8071. But doxygen cannot work with salt subproject. 

Step to reproduce my problem:

1) Type an example for plantuml

\startuml salt { Just plain text [This is my button] () Unchecked radio (X) Checked radio [] Unchecked box [X] Checked box "Enter text here " ^This is a droplist^ } \enduml

2) Run doxygen
I got an error in the html output:

salt: forbidden line salt

3) The generated .pu file is 


<at> startuml salt { Just plain text [This is my button] () Unchecked radio (X) Checked radio [] Unchecked box [X] Checked box "Enter text here " ^This is a droplist^ } <at> enduml

PlantUML.jar cannot generate png for this file.

4) After I remove the new line after <at> startuml. PlantUML.jar can generate png.

I can confirm doxygen will generate a new line after <at> staruml for every plantuml code. But PlantUML require no new line for salt subproject.

Is it possible to fix it? 

Best regards,
Bangyou
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Doxygen-develop mailing list
Doxygen-develop <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-develop
Kevin McBride | 10 Jan 18:03 2015
Picon

Dual-Boot Mode on my Laptop

Hello everyone,

Now that my laptop is old enough, I have decided to make it dual boot 
Windows and Linux (Fedora 21).  Everything worked right out of the box, 
including my wi-fi connection.  I have not tried my external blu-ray 
drive (though my laptop has an internal DVD drive), but everything else 
works.

After installing development packages through yum, I was able to get 
doxygen's command line interface to compile.  I still have yet to figure 
out how to get the GUI to work, but the GUI is low-priority to me as I 
know how to edit files manually using 'vim'.  After being away from 
Linux for several years, I am slowly getting used to using Fedora.

I am back in Windows currently, as that is where most of the apps I use 
work with.  But at least now, I have a much better way once again to 
verify bugs in Doxygen, especially crashers.  I have Doxygen compiled in 
debug mode for debugging crashers.

It is certainly about time that I got (though the old way) a linux 
subsystem of some sort installed.

- Kevin McBride

------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
Stephane Fillod | 7 Jan 16:26 2015
Picon

[PATCH] typo in doxmlparser subdirectory path

Hi,

There's a typo in the doxmlparser subdirectory path.

diff --git a/addon/doxmlparser/examples/metrics/metrics.pro.in
b/addon/doxmlparser/examples/metrics/metrics.pro.in
index 3b2354d..f26a291 100644
--- a/addon/doxmlparser/examples/metrics/metrics.pro.in
+++ b/addon/doxmlparser/examples/metrics/metrics.pro.in
 <at>  <at>  -11,7 +11,7  <at>  <at>  win32-borland:LIBS          += doxmlparser.lib qtools.lib
shell32.lib
 win32-borland:TMAKE_LFLAGS  += -L..\..\..\..\lib
 win32:TMAKE_CXXFLAGS        += -DQT_NODLL
 DESTDIR                     = ../../../../bin
-OBJECTS_DIR                 = ../../../../objects/doxmlparer/metrics
+OBJECTS_DIR                 = ../../../../objects/doxmlparser/metrics
 TARGET                      = metrics
 DEPENDPATH                  = ../../include
 INCLUDEPATH                += ../../../../qtools ../../include

Best Regards
--

-- 
Stephane

------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
Paul_Hoad | 5 Jan 10:49 2015

Re: PATCH limit warnings from doxygen

Dimitri

 

I hope you don’t mind but I’m resending this to the develop list, this time with a smaller zip file as the previous one  bounced the email from the list and I am unsure if the list received the message.

 

The larger config.xml I removed, but outline the change needed here

 

-------------------------------------------------------

</docs>

    </option>

    <option type='int' id='LIMIT_WARNINGS' minval='0' maxval='10000' defval='0'>

      <docs>

<![CDATA[

The \c LIMIT_WARNINGS tag can be used to stop doxygen when a maximum number of warnings has been seen.

<br>

\b Tip: Turn warnings on while writing the documentation.

]]>

-------------------------------------------------------

 

Paul

 

From: Paul Hoad
Sent: 03 December 2014 12:57
To: 'doxygen-develop <at> lists.sourceforge.net'; 'dimitri <at> stack.nl'
Subject: PATCH limit warnings from doxygen

 

Dimitri

 

I recently posted a question on StackOverFlow regarding being able to stop doxygen after it had seen a certain number of warnings, somewhat akin to the –ferror-limit=N option that certain compilers have.

 

http://stackoverflow.com/questions/27174031/possible-to-stop-doxygen-after-n-warnings

 

I have a large code base, mostly un-doxygen’d, I have a nightly build that runs doxygen but its produces thousands of warnings. I know getting full coverage is going to require a gradual continuous improvement approach which leads to a mindset change of the individual teams of developers.

 

So to tackle this I have added doxygen running on the current source subdirectory as “PreBuild Event” in Visual Studio project files, I don’t want to use the temporary documentation it generates (that will come from the full tree nightly build), but I want to see the warnings, I format the warnings with

 

WARN_FORMAT            = "$file($line): $text"

 

Which this means that while the code is compiling, this allows the developer to go back in and double click the warnings in the output window and be taken to the location to fix those doxygen warnings (as they would any other warning), the problem is that for many of the directories the number of warnings is huge (which are too daunting to fix in one go)

 

I don’t want to do a full Doxygen scan everytime (which is also why I only do it on the sub directory) because that will take too long and I don’t want all the warnings or the developer will simply treat it a noise, I just want them to see a few and then stop.

 

My idea is to be able to tell doxygen to document locally only a certain number of warnings and then stop, this means that every build the developer will see a few more warnings (but only a couple 5-10) and be driven to fix those, over time the code will become documented and the developers will learn to document as they go, also any new code (especially in previously doxygen clean areas) will immediately become a warning. Think of it as “Continuous Incremental Documentation”

 

Given that I don’t think this is possible currently, I took it upon myself to try and learn how to do it, I am very new to the doxygen source code, so I apologize in advance if I did it in the wrong place.

 

So the change to the doxygen source to implement something like this turned out to be fairly simple, with only having to add a new LIMIT_WARNINGS option to the config file, so I thought I would share the code change, feel free to use or discard as you see fit.

 

So I’ve not contributed before, so I’m not 100% clear of the etiquette or who to send any diffs to, so I’ve included the changed files and the diff from the tip of the git tree, if I should submit this another way, bug number etc.. let me know.

 

Paul

 

P.S. I couldn’t find any requests like this in the bug tracker database.

 

 

Attachment (LIMIT_WARNING.zip): application/x-zip-compressed, 4300 bytes
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Doxygen-develop mailing list
Doxygen-develop <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-develop
Eckard Klotz | 3 Jan 16:15 2015
Picon

New snapshot of Moritz 2.0.2 to generate nassi shneiderman and UML like activity together with some tutorials is available

Hello Everybody.

I wish you a happy new year.

Since some years I'm providing  Moritz a tool to generate source diagrams. First Moritz started with html-based nassi shneiderman diagrams and since  last year dot-based UML like activity diagrams are available also.

Currently I'm working on a possibility to create mscgen-based message sequence charts. Even this feature is not available until now for you, I have posted today a new snapshot for windows and linux. For other operation-systems the source-code is provided and the both binaries abc2xml and xml2abc should be usable with the linux distribution then.

Please take a look at:

https://sourceforge.net/projects/moritz/files/Moritz_2.x/DevelopmentFor_2_1_0/Snapshot_2_0_2/

Here you will find a windows-distribution and one for linux (build with Ubuntu 14.04 for a 32bit system). Furthermore a the sources for the two binaries abc2xml and xml2abc.

New is a sub folder in this snapshot with some tutorials:
1. An introduction that explains a basic source example and the set up of the used tools.
2. A nassi shneiderman diagram example that shows how to create them and hoe to use them with doxygen.
3. A UML like activity diagram example that shows how to create them and hoe to use them with doxygen.

It would be kind if you would find the time to test it and please post a comment in the forum from Moritz.

Best regards,
Eckard Klotz.

------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Doxygen-develop mailing list
Doxygen-develop <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-develop
Dagobert Michelsen | 28 Nov 12:16 2014

configure fails on Solaris

Hi Dimitri,

I noticed the current „configure“ of doxygen is broken on my Solaris continuous integration:

> ./configure
> in dir /export/home/buildbot/slave/doxygen-solaris10-i386/build (timeout 1200 secs)
> watching logfiles {}
> argv: ['./configure']
> environment:
>  CC=/opt/solarisstudio12.3/bin/cc
>  CXX=/opt/solarisstudio12.3/bin/CC
>  HOME=/export/home/buildbot
>  LDFLAGS=-R/opt/csw/lib
>  LOGNAME=buildbot
>  MAIL=/var/mail//buildbot
>  MANPATH=/usr/share/man:/opt/csw/share/man
>  PATH=/opt/csw/gnu:/usr/bin:/usr/ccs/bin:/opt/csw/bin
>  PWD=/export/home/buildbot/slave/doxygen-solaris10-i386/build
>  SHELL=/opt/csw/bin/bash
>  SHLVL=1
>  SSH_CLIENT=192.168.1.8 51910 22
>  SSH_CONNECTION=192.168.1.8 51910 192.168.1.33 22
>  TZ=Europe/Berlin
>  USER=buildbot
>  _=/opt/csw/bin/buildslave
> using PTY: False
> 
>  Autodetected platform solaris-g++... 
>  Checking for GNU make tool... using /opt/csw/bin/gmake
>  Checking for GNU install tool... using /usr/bin/install
>  Checking for dot (part of GraphViz)... using /opt/csw/bin/dot
> 
> ./configure: syntax error at line 558: `libclang_hdr_dir=$' unexpected
> 
> program finished with exit code 2
> elapsedTime=0.264766

Can you please have a look?

You can also check the status at
 https://buildfarm.opencsw.org/buildbot/waterfall?builder=doxygen-solaris10-i386&builder=doxygen-solaris10-sparc&reload=none

Best regards

 — Dago

-- 
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

--

-- 
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

Attachment (smime.p7s): application/pkcs7-signature, 3266 bytes
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Doxygen-develop mailing list
Doxygen-develop <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-develop
Helmut Grohne | 1 Nov 18:02 2014
Picon

segfault with cyclic subgroups

Dear Doxygen developers,

I am faced with a segmentation fault of Doxygen 1.8.8 (as used by Debian
unstable on amd64) when trying to process the following (invalid?)
header:

| /**
|  *  <at> addtogroup foo1 foo2
|  *  <at> {
|  *  <at> addtogroup foo4 foo5
|  *  <at> {
|  *  <at> defgroup foo1 foo3
|  *  <at> }
|  *  <at> }
|  */

While this example looks artificial, it was processed by earlier
versions of Doxygen and the Enlightenment libraries reproduce the same
segmentation fault (see https://bugs.debian.org/762272).

What happens is that stack space is exhausted in a recursion of
recursivelyAddGroupListToTitle. Turns out the recursion alternates
between group foo1 and foo4. Conceptually, I have no clue what cyclic
subgroup membership is supposed to mean. One way to look at this problem
is to argue that Doxygen fails to refuse processing cyclic subgroups.
Alternatively the depth of the recursion can be limited.

I am proposing the attached patch (suitable to "git am") to make Doxygen
error out when faced with cyclic subgroups. Is this patch reasonable for
inclusion upstream and does it fully fix the problem?

I would like to add some minimal fix to the Debian package as Debian
jessie is almost frozen (i.e. a new upstream release of Doxygen cannot
be added to Debian atm).

Thanks for considering

Helmut
Attachment (fix-762272.diff): text/x-diff, 1122 bytes
------------------------------------------------------------------------------
_______________________________________________
Doxygen-develop mailing list
Doxygen-develop <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-develop
Andreas Tscharner | 23 Oct 13:36 2014
Picon

Superscript does not work anymore since 1.8.7

The subject says all: Superscript does not work any longer since at 
least 1.8.7.

It does not matter if I use
x^2
x<SUP>2</SUP>
&sup2;

They all result in "x^2" in the HTML output.

Best regards
	Andreas
--

-- 
       ("`-''-/").___..--''"`-._
        `o_ o  )   `-.  (     ).`-.__.`)
        (_Y_.)'  ._   )  `._ `. ``-..-'
      _..`--'_..-_/  /--'_.' .'
     (il).-''  (li).'  ((!.-'

Andreas Tscharner   andy <at> vis.ethz.ch   ICQ-No. 14356454

------------------------------------------------------------------------------
Hans Z | 5 Oct 19:39 2014
Picon

Config: Special Commands Indicator

Hello,

Is it possible either in the current release or possibly in a future
release, to configure what the special commands indicator?  Very often
documentation contains at-signs or backslashes and while I know of the
workarounds to escape them, in some cases this becomes very tedious.

Would it be possible to add a configuration directive that allows
setting what the special commands indicator would be?  For example:

SPECIAL_CMD_INDICATOR =  <at>  <at> 

Thank you,

---
Hans Zaunere / Managing Member / Stackware, LLC
              stackware.com   /   cnvyr.io

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk

Gmane