doxygen-develop — List for discussing new features, submitting patches, etc.

[Doxygen-develop] Feature Request: disable "generated on" in HTML footer by default

[Michal S. <ms...@su...>]

Hi!

There is a problem with same packages which are build in different time
and which use doxygen to build doc part
This "generated on" feature in HTML footer causes diff in doc part,
which is not easy to recognize as "real change", so it's problem to
check if generated package was really changed or not
I know there is a option to fix this issue through the HTML_FOOTER, but
for build system which build hundreds of open source packages
 you need to patch each package separately
So I want to know if disable "generated on" by default is right and if
would be possible to fix it

thanks
Michal

[Doxygen-develop] Problems with LaTeX output

[Guy H. <guy...@or...>]

Hi there

I am trying to get a body of code that was previously documented using 
doxygen v1.3.9 to work with v1.5.8. In fact I'm using a checkout from 
svn as there is a known problem with the latex output from 1.5.8 caused 
by latex environments not being 'end'ed properly.

My initial checkout pulled down version 681 and this built and ran fine, 
but I found that it didn't manage to add hyphenation hints in long 
method names as the old version of doxygen did, and I got lots of 
overfull hbox warnings from latex. I tried a later checkout (version 
684) but hyperlinks in this version appeared to be completely broken --- 
all the links in my PDF take me to the top page.

Are these known faults in doxygen svn at the moment? Might I have 
overlooked a config change that I need in my doxyfile?

many thanks

guy

[Doxygen-develop] new snapshot of moritz ( my nassi-shneiderman addon for doxygen) is online

[<Eck...@t-...>]

Hello everybody.

There is a new snapshot of moritz ( my nassi-shneiderman addon for
doxygen) online. This is an update of the moritz binary as reaction to
the bug reported in the forum ( "Linking the output of Moritz with
doxygen" take a look into the posts of the discussion ). In the formally
versions it was possible that moritz didn't generate diagrams for all
functions in the sources under some conditions.

Please take a look to the snapshots in the download-section of 
www.sourceforge.net/projects/moritz/
Here you will find a zip-archive named Moritz_bin_2009_03_06.zip

To use this patch please copy the binary-file of your operation-system
into the bin-folder of your moritz-distribution (after renaming the
original binary-file to make a restore possible). The exe-file is for
win32-systems the other file is for linux-systems. 
You may also build the binary by your self out of the sources. Except
c++ standard-libraries no special libraries are necessary. Just put all
source-files in to a project of your favourite ide and set the
search-paths for all h-files. no special defines have to be done. 

Please test it out and post a comment into the forum of moritz (use the
link above).

Kind regards,
Eckard. 

[Doxygen-develop] Fwd: [Doxygen-users] Doxygen XML's refid attribute

[Zuzel V. P. <zu...@uh...>]

I'm generating documentation XMLs using doxygen after each commit to a version
control system repository and I have some questions about the refid attribute:

1) How is doxygen XML's refid attribute created?
2) Can it be used to identify the documentation of namespaces, classes and
functions between different revisions?

-- 
Thanks,
    Zuzel

[Doxygen-develop] C++ Namespace Alias Parsing

[Christoph H. <chr...@gm...>]

Hi,

are there any known issues related to namespace aliasing with doxygen 1.5.8?

In my examples I'm shortening namespaces using namespace aliasing.
Suppose I have a namespace ::Foo::Bar. Now I'd like to shorten this by

namespace FB = ::Foo::Bar;

and use it later (within the same file and method) by

class X : FB::Base {
 // ...
};

The problem is that FB::Base is not linked to ::Foo::Bar::Base automatically.

I guess namespace aliasing is not parsed by doxygen?

Best regards,
Christoph

[Doxygen-develop] SIGSEGV in doxygen

[Roman K. <ko...@ft...>]

The doxyfile and the test source code are attached.

 >doxygen --version
1.5.8
 >uname -a
Linux noise 2.6.18-92.1.22.el5.centos.plus #1 SMP Wed Dec 17 10:49:19 EST 
2008 x86_64 x86_64 x86_64 GNU/Linux

 >gdb $(which doxygen)
...
Program received signal SIGSEGV, Segmentation fault.
0x00000033c3e788c9 in strncpy () from /lib64/libc.so.6
(gdb) bt
#0  0x00000033c3e788c9 in strncpy () from /lib64/libc.so.6
#1  0x00000000006618d5 in QCString::mid ()
#2  0x0000000000596981 in VhdlDocGen::parseFuncProto ()
#3  0x000000000064e801 in vhdlcodeYYlex ()
#4  0x000000000064f853 in parseVhdlCode ()
#5  0x00000000004353fe in FileDef::writeSource ()
#6  0x00000000004033a7 in generateFileSources ()
#7  0x0000000000419325 in generateOutput ()
#8  0x0000000000402a0d in main ()

[Doxygen-develop] <hr> patch

[Francesco M. <f18...@ya...>]

Hi,
    while looking at doxygen docs I've noticed a small defect in the command 
listing page: some <hr> are missing...

I've added them and I'm attaching the patch...

Happy new year!
Francesco

Re: [Doxygen-develop] Let us choose the amount of detail for the class diagrams

[Raja K. <raj...@gm...>]

I also find this feature very usefull, so I reposted it into bugzilla.
See it over here: http://bugzilla.gnome.org/show_bug.cgi?id=565473

Re: [Doxygen-develop] Support for PHP namespaces

[Karsten D. <ka...@ty...>]

Hi Dimitri.

On 17.09.2008, at 10:23, Karsten Dambekalns wrote:
> On 16.09.2008, at 20:36, Dimitri Van Heesch wrote:
>> I suggest to file a bug report with severity set to enhancement  
>> about this feature request and
>> include some (references to) examples of typically usages (and/or a  
>> link to a formal grammar).
>
> I'll do so.

I did that back then (http://bugzilla.gnome.org/show_bug.cgi? 
id=552605) and have just updated the entry following up on the recent  
release of PHP 5.3.0alpha3 which included the new (final) namespace  
syntax.

I'd really love to see Doxygen supporting this, would be at least one  
piece of our toolchain that works (again).

Regards,
Karsten
-- 
Karsten Dambekalns
Gimme Five!
http://typo3.org/gimmefive

[Doxygen-develop] Problem with macros : Preprocessor doesn't handle correctly documentation generated by a macro

[Claire C. <cch...@il...>]

Hello,

 

I have an isuue with the doxygen preprocessor which doesn't handle
correctly a documentation generated by a
macro with Doxygen 1.5.6.
 
For example if you have in a header file:
 
 ILOEXTENSIONHNONINLINE(IloAlgorithm)
 
and in another :
 
#define ILOEXTENSIONHNONINLINE(hname) \
/** \
 * <p>This member function returns a character string specifying \
 * the name of the invoking object (if there is one).</p> \
 *  @@see @0#end() \
 */ \
  const char * getName() const; \
 
 
The result in the documentation is:
 
 \
 
This member function returns a character string specifying \ the name of
the
invoking object (if there is one).
\ @
 
See Also:
 
@0#end() \ 
 
 

My configuration is correct I think as the maco is expanded by the
result of the expansion is bad.

 

Do you have an idea of the problem?

 

Thanks,

Regards,

 

Claire

 

____________________________________

Claire Chardiny

Associate Internal Projects Manager

Refs Factory, Quality & Methods Manager - OneIT Team

[Doxygen-develop] Let us choose the amount of detail for the class diagrams

[Pietro M. <pie...@ya...>]

To reduce the size of the class diagrams, it would be useful to be able to select the amount of detail shown for the classes. Going from the most compact representation to the most detailed one, show:

- Just the class name (with eventual template stuff).

- Just the public member functions, with and without their parameters.

- All member functions and attributes without their parameters.
*** In this case, if there are some overloaded functions, do NOT show them all. It is useless to have a list of, e.g., 10 overoladed Print() functions which are shown in the same way because the parameters are omitted. This is an incredible waste of space on the screen and on paper, that makes diagrams appear huge even if they can be reduced to a more manageble size. Just use a simbol to indicate that the function is overloaded (e.g. #), and print it just once. ***

- All member functions and attributes with their parameters and return type.

- Show everything.

 
Pietro Mele


pietromele  at  yahoo.com
http://www.geocities.com/pietromele/



________________________________


      

[Doxygen-develop] Small graphs in latex output

[Joost v. W. <jo...@ze...>]

The graphs in the latex output are very small.
Unreadable sometimes.

I looked at the code that generates the latex for the graphs.
I found this code in dot.cpp line 1959

      if (width>maxWidth)
       {
         out << "\\includegraphics[width=" << maxWidth << "pt]";
       }
       else if (height>maxHeight)
       {
         out << "\\includegraphics[height=" << maxHeight << "pt]";
       }
       else
       {
         out << "\\includegraphics[width=" << width/2 << "pt]";
       }
       out << "{" << baseName << "}\n"
         "\\end{center}\n"
         "\\end{figure}\n";

My question is in the else case why is width divided by 2?
Beceause in my output if i would double the points (so get the width  
value back) al the pictures have a nice size.

My question is: is this a bug in the latex output?
Do i have to compile my own doxygen to fix this?
Or is there a other way to specify the width of the pictures in the  
latex output that i couldn't find?

Greetings

[Doxygen-develop] Formula generation on windows with latest tools

[Richard78 <ric...@vi...>]

Hello,

I have installed MikeTex and all the required programs (latest versions) to
generate nice formulas using doxygen. All those programs are installed under
C:\Program Files\..... Everything works fine except when the formula images
have to be generated. I get an C:/Program does not exist. There is obviously
something wrong with the space in the filename. 

I have downloaded doxygen code and debugged it. The string executed look
fine, I even could run it in a command console, but it refused to work using
"return system(fullCmd);" (line 122 in portable.cpp).
I have then commented this line and always use the ShellExecute (line 132 in
portable.cpp) and everything worked fine.

I wonder if this is a bug or a configuration problem on my computer.

Regards,
Richard
-- 
View this message in context: http://www.nabble.com/Formula-generation-on-windows-with-latest-tools-tp20499368p20499368.html
Sent from the Doxygen - Development mailing list archive at Nabble.com.

[Doxygen-develop] XML output

[Mark V. <ma...@oc...>]

I see at http://www.stack.nl/~dimitri/doxygen/output.html that "XML  
output is still under development". If I use the latest version of  
doxygen in SVN, will I get more data in the XML output than the  
release version provides? For example, I need the data types of  
variables inside classes, information extracted from IDL files, and  
paths to the source files from which the documentation was extracted.  
This is all information that is available in the HTML output.

---
Mark Volkmann

[Doxygen-develop] MSC generator patch + misc

[<aca...@fr...>]

Hi all,

Below is a patch with a few modifications. The unimportant ones are:
- Some spurious '\n' in warning string have been removed
- Replace '$filename' keyword in the warning string template by the filename
of the file without the path (normally, '$file' is replaced by path+filename)
- Additional option for MSVC++ linker to prevent a warning

The last one enables the output from the MSCGEN child process and print it
to stdout. Actually, I do not understand why it has been disabled. MSCGEN
syntax is not trivial and errors are frequent. Having to generate the
chart externally and reimport it in its source file when it is error free
is really tedious and this little change is of great help (may be some
side effect on other platform? I only tried under windows/cygwin).

The output is unfortunately quite raw, and do not print real error location
(source file name and line number) as an intermediate file is generated for
MSCGEN. I was thinking of providing a better patch that give some info
to MSCGEN as options, in order to print a correct error message if needed
but that is not obvious when looking at the doxy source. The input filename
and line seem to be unknown when MSCGEN is called; actually, I would be
interested if some doxy gurus can provide me some hints about this point,
in order to provide a elegant patch that could be integrated in the main
branch.

Thanks,

Antoine Calando

------------------------- attached patch: -------------------------

Index: src/commentscan.l
===================================================================
--- src/commentscan.l	(revision 661)
+++ src/commentscan.l	(working copy)
@@ -2462,14 +2462,14 @@
 {
   //if (g_memberGroupId!=DOX_NOGROUP)
   //{
-  //  warn(fileName,line,"Warning: end of file while inside a member group\n");
+  //  warn(fileName,line,"Warning: end of file while inside a member group");
   //}
   g_memberGroupId=DOX_NOGROUP;
   g_memberGroupRelates.resize(0);
   g_memberGroupDocs.resize(0);
   if (!g_autoGroupStack.isEmpty())
   {
-    warn(fileName,line,"Warning: end of file while inside a group\n");
+    warn(fileName,line,"Warning: end of file while inside a group");
   }
 }
 
@@ -2477,7 +2477,7 @@
 {
   if (g_memberGroupId!=DOX_NOGROUP)
   {
-    warn(fileName,line,"Warning: try to put compound %s inside a member group\n",name);
+    warn(fileName,line,"Warning: try to put compound %s inside a member group",name);
   }
   g_memberGroupId=DOX_NOGROUP;
   g_memberGroupRelates.resize(0);
Index: src/doxygen.cpp
===================================================================
--- src/doxygen.cpp	(revision 661)
+++ src/doxygen.cpp	(working copy)
@@ -518,7 +518,7 @@
             gd->setGroupTitle( root->type );
           else if ( root->type.length() > 0 && root->name != root->type && gd->groupTitle() != root->type )
             warn( root->fileName,root->startLine,
-                "group %s: ignoring title \"%s\" that does not match old title \"%s\"\n",
+                "group %s: ignoring title \"%s\" that does not match old title \"%s\"",
                 root->name.data(), root->type.data(), gd->groupTitle() );
           //if ( gd->briefDescription().isEmpty() )
             gd->setBriefDescription(root->brief,root->briefFile,root->briefLine);
Index: src/message.cpp
===================================================================
--- src/message.cpp	(revision 661)
+++ src/message.cpp	(working copy)
@@ -18,6 +18,7 @@
 #include <stdarg.h>
 #include <stdio.h>
 #include <qdatetime.h>
+#include <qfileinfo.h>
 #include "config.h"
 #include "util.h"
 #include "debug.h"
@@ -117,7 +118,15 @@
   if (!Config_getBool(tag)) return; // warning type disabled
   char text[40960];
   vsprintf(text, fmt, args);
-  QCString fileSubst = file==0 ? "<unknown>" : file;
+  QCString fileSubst = "<unknown>";
+  QCString filenameSubst = fileSubst;
+  if (file)
+  {
+    fileSubst = file;	
+    QFileInfo f(file);
+    filenameSubst = f.fileName();
+  }
+  
   QCString lineSubst; lineSubst.setNum(line);
   QCString textSubst = text;
   QCString versionSubst;
@@ -136,8 +145,11 @@
       substitute(
         substitute(
           substitute(
-            substitute( 
-              outputFormat,
+            substitute(
+              substitute( 
+                outputFormat,
+                "$filename",filenameSubst
+              ),
               "$file",fileSubst
             ),
             "$text",textSubst
Index: src/msc.cpp
===================================================================
--- src/msc.cpp	(revision 661)
+++ src/msc.cpp	(working copy)
@@ -119,7 +119,7 @@
   mscArgs+=extension+"\"";
   int exitCode;
   //printf("*** running: %s %s\n",mscExe.data(),mscArgs.data());
-  if ((exitCode=portable_system(mscExe,mscArgs,FALSE))!=0)
+  if ((exitCode=portable_system(mscExe,mscArgs,TRUE))!=0)
   {
     goto error;
   }
@@ -155,7 +155,7 @@
   mscArgs+=outFile + "\"";
 
   int exitCode;
-  if ((exitCode=portable_system(mscExe,mscArgs,FALSE))!=0)
+  if ((exitCode=portable_system(mscExe,mscArgs,TRUE))!=0)
   {
     QDir::setCurrent(oldDir);
     return "";
Index: winbuild/Doxygen.vcproj
===================================================================
--- winbuild/Doxygen.vcproj	(revision 661)
+++ winbuild/Doxygen.vcproj	(working copy)
@@ -78,6 +78,7 @@
 			/>
 			<Tool
 				Name="VCLinkerTool"
+				AdditionalOptions="/NODEFAULTLIB:library"
 				AdditionalDependencies="qtools.lib libpng.lib zlib.lib ws2_32.lib iconv.lib"
 				OutputFile="..\bin\Debug\doxygen.exe"
 				LinkIncremental="2"

[Doxygen-develop] Some features i would love to see in doxygen

[Marcelo T. <mai...@gm...>]

Hello.
I am a strong user of doxygen but i have some ideas which if implemented
would make doxygen more usefull to me and hopefully also for others.

First is member groups nesting. The question is why not? If the user feels
it has many categories and subcategories for classifying its methods, its
his decition. Isnt it?

Another, more interesting feature is a filtering feature. I would like to be
able to produce documentation with all the public methods, ignoring private
and protected. And also to filter only the classes i like to stay. This is
used when I work in a library project and i want to generate documentation
for the user of the library and not for the developer. In those cases i
would like the documentation to be as simple as possible.

The last of the features I am longing for is to be able to generate a framed
version of a class view... in that case the class methods are shown in the
right frame and the list of class methods are shown in a left frame instead
of being shown in the head of the page. That is similar to the current menu,
but different because the menu does not show methods, it shows  only
classes, and i cannot decide which information i want in the menu or not.
That would help the user to browse the page without losing a table of
contents as a help.

Please tell me what do you think about those ideas and what are the chances
that they will be implemented.
Thank you
Marcelo

Re: [Doxygen-develop] Reference to values or evaluation

[<Ste...@in...>]

Hi Martin,
I was very intensively looking for the same feature you mentioned below. I also need it for customer documentation. However, it turned out to be not available yet.

I am also missing a feature like this.

-Stefan

-----Original Message-----
From: Martin Schäfer [mailto:m.s...@vo...]
Sent: Freitag, 31. Oktober 2008 11:22
To: dox...@li...
Subject: [Doxygen-users] Reference to values or evaluation

Hello,

I'm seeking the posibillity to place the value of a constant expression in my documentation.

Example:
Somewhere in your code are contant expressions like this

   /*!
    * \brief Level to switch on.
    */
   #define ON_LIMIT   100

Somewhere in your code are references to this contant

   ...
   if (level > ON_LIMIT) {
      /* switch on */
   }
   else {
      /* switch off */
   }
   ...

If you write a doxygen comment you can reference to the above contants name but not to the defined value.

   /*!
    :  ...
    *  If level is higher than ::ON_LIMIT it is switched on.
    :  ...
    */

This will result in the following output:

   ...
   If level is higher than ON_LIMIT it is switched on.
   ...

ON_LIMIT will be a link to the definition.  This may be suitable for a developer but not for a user who is reading a manual.  It would be nice if I could place the value instead the name of the constant in my documentation.

   /*!
    :  ...
    *  If level is higher than \eval(ON_LIMIT+1) it is switched on.
    :  ...
    */

The result should be

   ...
   If level is higher than 101 it is switched on.
   ...

Is there already a feature like this implemented in doxygen?
If not it would be nice to implement it. Keep in mind of other constant expressions like single fields of arrays, structures, list of structures, const definitions, etc.


Best regards
Martin

voltwerk electronics GmbH - Sitz der Gesellschaft: Hamburg - Amtsgericht Hamburg, HRB 100909
Geschäftsführung: Dirk Wiegmann

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Doxygen-users mailing list
Dox...@li...
https://lists.sourceforge.net/lists/listinfo/doxygen-users

[Doxygen-develop] new snapshot of moritz ( my nassi-shneiderman addon for doxygen) is online

[<Eck...@t-...>]

Hello everybody.

There is a new snapshot of moritz ( my nassi-shneiderman addon for
doxygen) online that should reduce the amount of generated diagrams for
nested compiler-switches:

void my_function(void)
{
 #if defined(MEANSWITCH)
  meanCommand();
 #elif defined(SubSWITCH)
  subCommand();
 #elif defined(SubSubSWITCH) 
  subsubCommand();
 #else
  elseCommand();
 #endif 
}

In the previous versions of moritz 8 diagrams were generated since there
are 8 combinations with 3 switches whitch may be on or off. But in
reality ony 4 diagrams are diffrent fom each other. The other 4 are a
copy of one of those. Moritz is now able to recognize this copies. If
the command MRTZ_checkCompilerSwitch was used before to choose the right
diagrams its parameters have to be changed now.


To use this patch please copy the binary-file of your operation-system
into the bin-folder of your moritz-distribution (after renaming the
original binary-file to make a restore possible).The exe-file is for
win32-sytstems the other file is for linux-systems.

Please test it out and post a comment into the forum of moritz.

Kind regards,
                       Eckard.

Re: [Doxygen-develop] src/util.cpp substitute semantics ?

[Dimitri V. H. <do...@gm...>]

Hi Robbe,

You are right. I'll include your patch.

Regards,
   Dimitri

On 16 okt 2008, at 05:16, Robbie Gates wrote:

> Hi All,
>
>  it looks to me like the reimplemented subsitute in src/util.cpp in
> the 1.5.7.1 release has different semantics to the original when
> passed a null string (i.e. 0 ptr) for the dst argument. It now returns
> the string unchanged, whereas previously it treated it as if dst was
> the empty string. The patch below restores the old behaviour. It's a
> bit of a hack, but its as local a change as i could make.
>
>  I noticed this because our header.html uses relpath, and the
> relativePathToRoot function in src/util.cpp returns a null string,
> rather than an empty string, when the relative path is empty.
>
>  Hope this helps,
>
> - robbie
>
> @@ -4447,10 +4447,10 @@
>
> QCString substitute(const char *s,const char *src,const char *dst)
> {
> -  if (s==0 || src==0 || dst==0) return s;
> +  if (s==0 || src==0) return s;
>   const char *p, *q;
>   int srcLen = strlen(src);
> -  int dstLen = strlen(dst);
> +  int dstLen = dst ? strlen(dst) : 0;
>   int resLen;
>   if (srcLen!=dstLen)
>   {
> @@ -4469,7 +4469,10 @@
>     int l = (int)(q-p);
>     memcpy(r,p,l);
>     r+=l;
> -    memcpy(r,dst,dstLen);
> +    if (dst)
> +    {
> +      memcpy(r,dst,dstLen);
> +    }
>     r+=dstLen;
>   }
>   strcpy(r,p);
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's  
> challenge
> Build the coolest Linux based applications with Moblin SDK & win  
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in  
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Doxygen-develop mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-develop

[Doxygen-develop] src/util.cpp substitute semantics ?

[Robbie G. <ro...@m8...>]

Hi All,

  it looks to me like the reimplemented subsitute in src/util.cpp in
the 1.5.7.1 release has different semantics to the original when
passed a null string (i.e. 0 ptr) for the dst argument. It now returns
the string unchanged, whereas previously it treated it as if dst was
the empty string. The patch below restores the old behaviour. It's a
bit of a hack, but its as local a change as i could make.

  I noticed this because our header.html uses relpath, and the
relativePathToRoot function in src/util.cpp returns a null string,
rather than an empty string, when the relative path is empty.

  Hope this helps,

 - robbie

@@ -4447,10 +4447,10 @@

 QCString substitute(const char *s,const char *src,const char *dst)
 {
-  if (s==0 || src==0 || dst==0) return s;
+  if (s==0 || src==0) return s;
   const char *p, *q;
   int srcLen = strlen(src);
-  int dstLen = strlen(dst);
+  int dstLen = dst ? strlen(dst) : 0;
   int resLen;
   if (srcLen!=dstLen)
   {
@@ -4469,7 +4469,10 @@
     int l = (int)(q-p);
     memcpy(r,p,l);
     r+=l;
-    memcpy(r,dst,dstLen);
+    if (dst)
+    {
+      memcpy(r,dst,dstLen);
+    }
     r+=dstLen;
   }
   strcpy(r,p);

Re: [Doxygen-develop] Doxygen + Autotools integration

[Stefano D'A. <zan...@gm...>]

Just to let you know, I updated that stuff to Doxygen 1.5.7, added
support for Qt Help Project output and fixed some little things. It
currently doesn't work well because of a bad doxygen bug
(http://bugzilla.gnome.org/show_bug.cgi?id=554379), but it should have
worked.

Since it's likely I will make other changes, I leave you the address
of the hg repo: http://hg.atheme.org/naspro/

Best regards,

Stefano

Re: [Doxygen-develop] Doxygen + Autotools integration

[Stefano D'A. <zan...@gm...>]

2008/10/3 John Calcote <joh...@gm...>:
> I apologize for my lack of communication here. I didn't mean to ever
> imply that my solution was the best one out there. I was simply giving
> you some more resources to look at for building your generic doxygen
> solution. I only hope it was helpful.

No problem, don't worry. Plus, my solution cannot be considered just
"generic" (yet?).

Ah, and your manual reminded me of $EXEEXT :-P

Ciao,

Stefano

Re: [Doxygen-develop] Doxygen + Autotools integration

[Stefano D'A. <zan...@gm...>]

2008/10/3 Stefano D'Angelo <zan...@gm...>:
> 2008/10/2 John Calcote <joh...@gm...>:
>> You may wish to check out my book on Autotools, hosted by Free Software
>> Magazine. In there, I make several references to doxygen, and use code
>> snippets to implement doxygen targets within the sample projects and
>> examples provided in the book.
>>
>> http://www.freesoftwaremagazine.com/books/autotools_a_guide_to_autoconf_automake_libtool
>
> Well... at first sight the whole thing seems a bit "simplicistic" to
> me, maybe also because I'm generating html, ps, pdf, dvi and man
> output with Doxygen. I'll give it a better look tomorrow maybe.

Ok, read it. I have to congratulate with you for the manual, which
looks way better than the "autobook" (and less outdated of course),
but as said, the proposed solution wouldn't satisfy my needs.

Other than that, I think you could have used AC_CHECK_PROG instead of
AC_CHECK_PROGS to look for the doxygen binary, since it already does
the -z test on the variable used to store its path, thus you wouldn't
need the AC_PROG_TRY_DOXYGEN macro.

Stefano

Re: [Doxygen-develop] Doxygen + Autotools integration

[Stefano D'A. <zan...@gm...>]

2008/10/2 John Calcote <joh...@gm...>:
> You may wish to check out my book on Autotools, hosted by Free Software
> Magazine. In there, I make several references to doxygen, and use code
> snippets to implement doxygen targets within the sample projects and
> examples provided in the book.
>
> http://www.freesoftwaremagazine.com/books/autotools_a_guide_to_autoconf_automake_libtool

Well... at first sight the whole thing seems a bit "simplicistic" to
me, maybe also because I'm generating html, ps, pdf, dvi and man
output with Doxygen. I'll give it a better look tomorrow maybe.

Anyway, I just wanted to share what I did and see whether someone else
would like to take the challenge, otherwise I'm perfectly happy with
what I've already done. I do, honestly, have more important things to
work on at the moment.

Stefano

Re: [Doxygen-develop] Doxygen + Autotools integration

[Stefano D'A. <zan...@gm...>]

2008/10/2 Peter Johansson <tr...@gm...>:
> Hi Stefano,

Hi Peter,

> Have you checked the macro written by Oren Ben-Kiki that is available from
> the Autoconf Macro Archive:

Yes (I also named that in my prevoius e-mail -
http://www.ben-kiki.org/oren/doxample), and I'm not the only one to
think that it sucks on many fronts.

Stefano