headers
FJTC (Fabio Jun Takada Chino | 4 Oct 2004 03:21
Picon
Favicon

New version of the Brazilian Translator

Hi there.

Here comes the new version of the Brazilian Portuguese translator. I'm 
still having problems with the CVS repository so it is based on the 
tarball doxygen-1.3.8-20040928.tar.gz.

By the way, my e-mail address has changed to this one (jun-chino at 
uol.com.br). Since I finished my M.Sc. and left the University, I don't 
know for how long my old account (chino at icmc.usp.br) will remain active.

See you...
FJTC
Attachment (translator_br.h.gz): application/x-gzip, 9 KiB
Permalink | Reply | 0 comments |
headers
Paul.Mackay | 5 Oct 2004 22:42
Picon

FW: Extracting more source struture in XML output

I sent this mail some time ago about producing richer XML content of source code. Can I ask what others have
done in this area? In particular I got a reply from someone on this list (Fred P. [j2klib <at> hotmail.com])
whom I could not contact directly now.

Doxygen's XML schema is a good starting point to add to if I want a complete XML representation of the code, so
I would like to add to it rather than invent another schema. Also can anyone give me some pointers where I
would change the Doxygen code to output more source code structure? Doxygen must know much of this
information anyway, as it has some more detailed information in the highlight elements of the source file
XML files.

thanks

paul

-----Original Message-----
From: doxygen-develop-admin <at> lists.sourceforge.net
[mailto:doxygen-develop-admin <at> lists.sourceforge.net]On Behalf Of ext 
Sent: 26 April, 2004 12:01
To: doxygen-develop <at> lists.sourceforge.net
Subject: [Doxygen-develop] Extracting more source struture in XML output

I have recently been looking at XML and the output Doxygen can produce. The richness of information and
versatility of what can be done with it is impressive given the tools available for processing XML.

Does anyone have any comments on the idea of Doxygen outputting more information about the structure of the
source code? I am thinking of a breakdown in terms of blocks, statements, declarations, etc. This could be
used for more detailed metrics or a source browser for example, but it also opens up more possibilities for
independent tools that could use the Doxygen XML output, e.g. code checking. This would enhance the
current rich informational representation of the code in XML.
(Continue reading)

Permalink | Reply | 5 comments |
headers
Barber, Billy (AGTE | 7 Oct 2004 22:34

Error compiling doxygen 1.3.9 in Win32 with possible fix.


To all,
I tried sending this directly to Simon, but the mail system complained.  Not sure if the problem is on his end
or mine.  I downloaded the source for doxygen 1.3.9 and when I tried to build the "Win32 Debug" target I got
the following:

doxygen.obj : error LNK2001: unresolved external symbol "void __cdecl buildDirectories(void)" (?buildDirectories <at>  <at> YAXXZ)
doxygen.obj : error LNK2001: unresolved external symbol "void __cdecl generateDirDocs(class
OutputList &)" (?generateDirDocs <at>  <at> YAXAAVOutputList <at>  <at>  <at> Z)
filedef.obj : error LNK2001: unresolved external symbol "public: void __thiscall
DirDef::writeNavigationPath(class OutputList &)" (?writeNavigationPath <at> DirDef <at>  <at> QAEXAAVOutputList <at>  <at>  <at> Z)
Debug/Doxygen.exe : fatal error LNK1120: 3 unresolved externals
Error executing link.exe.

Doxygen.exe - 4 error(s), 0 warning(s)

I did a search for the "buildDirectories" signature and got hits in "dirdef.cpp" and "dirdef.h".  I added
these files to the doxygen project within the doxygen workspace as necessary and doxygen built
successfully.  I just joined the developer list so I was hoping to verify my solution with Simon before
"officially" posting, but since the message was rejected I figured I'd post and accept any deserved
consequences.  If these files should be added to a different project within the workspace please don't
hesitate to inform me of the correct solution.

Best Regards,

Bill

******************************************
The information contained in, or attached to, this e-mail, may contain confidential information and is
intended solely for the use of the individual or entity to whom they are addressed and may be subject to
(Continue reading)

Permalink | Reply | 0 comments |
headers
Chris Croughton | 8 Oct 2004 12:50
Picon

Re: FW: Extracting more source struture in XML output

(Emailed to OP as well as to the list, the sourceforge list server was
bouncing my mails, I don't know if it still is doing so...)

On Tue, Oct 05, 2004 at 01:42:07PM -0700, Paul.Mackay <at> nokia.com wrote:

> Doxygen's XML schema is a good starting point to add to if I want a
> complete XML representation of the code, so I would like to add to it
> rather than invent another schema. Also can anyone give me some
> pointers where I would change the Doxygen code to output more source
> code structure? Doxygen must know much of this information anyway, as
> it has some more detailed information in the highlight elements of the
> source file XML files.

I would very much like a C/C++ to XML translator, which seems to be what
you are suggesting as a possibility (or an extreme version of what you
are suggesting).  As you say it opens up a lot of possibilities for
extra tools, as well as for having doxygen produce internal
documentation (like local variables, tables of which functions use which
global variables (set and read), etc.  It needs to be switchable,
though.

While I'm thinking about switches, it would be very useful to have
options settable from the command line, not just in the configuration
file.  For some purposes I have to maintain three or more versions of
the config file (implementer detail, user detail, overview, sometimes
with or without relationship charts as well), a switch to set options
would be a lot easier to put in a makefile with a common config file for
all the messy stuff (include/exclude lists, etc.).  Oh, and the version
number.  Or have I missed something which already allows this?
(Continue reading)

Permalink | Reply | 4 comments |
headers
Dimitri van Heesch | 8 Oct 2004 15:49
Picon
Favicon

Re: FW: Extracting more source struture in XML output

On Fri, Oct 08, 2004 at 11:50:25AM +0100, Chris Croughton wrote:
> (Emailed to OP as well as to the list, the sourceforge list server was
> bouncing my mails, I don't know if it still is doing so...)
> 
> On Tue, Oct 05, 2004 at 01:42:07PM -0700, Paul.Mackay <at> nokia.com wrote:
> 
> > Doxygen's XML schema is a good starting point to add to if I want a
> > complete XML representation of the code, so I would like to add to it
> > rather than invent another schema. Also can anyone give me some
> > pointers where I would change the Doxygen code to output more source
> > code structure? Doxygen must know much of this information anyway, as
> > it has some more detailed information in the highlight elements of the
> > source file XML files.
> 
> I would very much like a C/C++ to XML translator, which seems to be what
> you are suggesting as a possibility (or an extreme version of what you
> are suggesting).  As you say it opens up a lot of possibilities for
> extra tools, as well as for having doxygen produce internal
> documentation (like local variables, tables of which functions use which
> global variables (set and read), etc.  It needs to be switchable,
> though.

Doxygen already produces XML. It could be improved to add more semantic
information about the bodies of functions, for instance to indicate if
something is a declaration, control statement, loop or assigment. 
Doxygen does not have this information explicitly available somewhere already
even though it can do syntax highlighting and linking.

> While I'm thinking about switches, it would be very useful to have
> options settable from the command line, not just in the configuration
(Continue reading)

Permalink | Reply | 3 comments |
headers
Chris Croughton | 8 Oct 2004 16:32
Picon

Re: FW: Extracting more source struture in XML output

On Fri, Oct 08, 2004 at 03:49:53PM +0200, Dimitri van Heesch wrote:

> Doxygen already produces XML. It could be improved to add more semantic
> information about the bodies of functions, for instance to indicate if
> something is a declaration, control statement, loop or assigment. 
> Doxygen does not have this information explicitly available somewhere already
> even though it can do syntax highlighting and linking.

Yes, it's the bodies of functions that I (and the OP) was thinking of.
I suspect that a general C/C++ to XML translator is more than Doxygen
wants to contain, however (let alone any other supported languages).

> > While I'm thinking about switches, it would be very useful to have
> > options settable from the command line, not just in the configuration
> > file.  For some purposes I have to maintain three or more versions of
> > the config file (implementer detail, user detail, overview, sometimes
> > with or without relationship charts as well), a switch to set options
> > would be a lot easier to put in a makefile with a common config file for
> > all the messy stuff (include/exclude lists, etc.).  Oh, and the version
> > number.  Or have I missed something which already allows this?
> 
> If you use a decent shell, you could use something like this:
> 
> (cat Doxyfile ; echo "PROJECT_NUMBER=0.2") | doxygen -

Ah, taking the config stuff from stdin was something I had missed,
thanks.  Yes, that would work fine, as would piping it through sed to
change options.  Or rules setting up an additional file and then cat-ing
both of them into doxygen.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Dimitri van Heesch | 8 Oct 2004 18:47
Picon
Favicon

Re: FW: Extracting more source struture in XML output

On Fri, Oct 08, 2004 at 03:32:51PM +0100, Chris Croughton wrote:
> On Fri, Oct 08, 2004 at 03:49:53PM +0200, Dimitri van Heesch wrote:
> > If you use a decent shell, you could use something like this:
> > 
> > (cat Doxyfile ; echo "PROJECT_NUMBER=0.2") | doxygen -
> 
> Ah, taking the config stuff from stdin was something I had missed,
> thanks.  Yes, that would work fine, as would piping it through sed to
> change options.  Or rules setting up an additional file and then cat-ing
> both of them into doxygen.
> 
> What does Doxygen do if the same option occurs more than once?  Take the
> last?  That would make an easy way to override options for special
> cases.

It will indeed take the last. To append to an option instead of overriding it 
you can use OPTION += value.

Regards,
  Dimitri

-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
Permalink | Reply | 1 comment |
headers
Chris Croughton | 8 Oct 2004 18:53
Picon

Re: FW: Extracting more source struture in XML output

On Fri, Oct 08, 2004 at 06:47:21PM +0200, Dimitri van Heesch wrote:

> On Fri, Oct 08, 2004 at 03:32:51PM +0100, Chris Croughton wrote:
> > 
> > What does Doxygen do if the same option occurs more than once?  Take the
> > last?  That would make an easy way to override options for special
> > cases.
> 
> It will indeed take the last. To append to an option instead of overriding it 
> you can use OPTION += value.

I can see I'm going to have fun with some makefiles.  Better than my
idea of having command-line switches.  I can just set things up to
append to the temporary control file as it runs through the make, then
cat it on the end of the base one into doxygen...

Thanks,

Chris C

-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
Permalink | Reply | 0 comments |
headers
George Varga | 8 Oct 2004 19:53
Picon

Bug: MacOS X path to Doxygen cannot contain spaces

Hello Dmitri!

I have found that you should place doxygen.app on a path that does not 
contain spaces if you want to use dot.

If the path contains spaces the dot tool will not run and the following 
error will be printed in the log:

sh: line 1: /<pathUntilFirstSpace>: No such file or directory
Problems running dot. Check your installation!

I think you need to quote the path to dot in the sh command.

Doxygen: 1.3.8
MacOS X: 10.6.5

George Varga

-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
Permalink | Reply | 1 comment |
headers
spartacus | 8 Oct 2004 22:34
Favicon

Re: Welcome to the "Doxygen-develop" mailing list

On Friday 08 October 2004 15:16, doxygen-develop-request <at> lists.sourceforge.net 
wrote:
> Welcome to the Doxygen-develop <at> lists.sourceforge.net mailing list!
>
> To post to this list, send your email to:
>
>   doxygen-develop <at> lists.sourceforge.net
>
> General information about the mailing list is at:
>
>   https://lists.sourceforge.net/lists/listinfo/doxygen-develop
>
> If you ever want to unsubscribe or change your options (eg, switch to
> or from digest mode, change your password, etc.), visit your
> subscription page at:
>
>  
> https://lists.sourceforge.net/lists/options/doxygen-develop/spartacus%40spe
>akeasy.net
>
>
> You can also make such adjustments via email by sending a message to:
>
>   Doxygen-develop-request <at> lists.sourceforge.net
>
> with the word `help' in the subject or body (don't include the
> quotes), and you will get back a message with instructions.
>
> You must know your password to change your options (including changing
> the password, itself) or to unsubscribe.  It is:
(Continue reading)

Permalink | Reply | 1 comment |

Gmane