Liebe Raimund,
First of all thanks for all the detailed info,
I'll look into everything another day (when I have slightly more time) and post
back my findings and the setup we used in the end!
MfG,
Pez
From: Klein, Raimund [mailto:raimund.kl...@berenberg.de]
Sent: Tuesday, August 21, 2012 2:09 PM
To: doxygen-users@lists.sourceforge.net
Subject: Re: [Doxygen-users] Multiple Projects, Languages and Shared Config
Files
Importance: High
Hi Pez,
Welcome to the Light. :)
As to your first question, you have basically two ways:
- The obvious way is to just create a master HTML page manually and
link statically to the generated documentation.
- If you want to ensure a consistent appearance, you can just create
another general documentation project which will only consist of files with
comments. (AFAIK This is how Dimitri maintains the Doxygen website itself.)
I'll combine the replies to your other questions, as we have a similar setup:
We're combining documentation for Java and VB .NET code (via the VB .NET to
C#-filter) and doing our best to manage at least most of it in just one master
config file. What came in very handy was the features of @INCLUDE_PATH and
@INCLUDE for the configuration:
http://www.stack.nl/~dimitri/doxygen/config.html combined with doxygen's
ability to process configuration settings via stdin (look at
http://www.stack.nl/~dimitri/doxygen/faq.html Item
#17<http://www.stack.nl/~dimitri/doxygen/faq.html%20Item%20#17>). Of course,
you can also just add a single doxyfile with additional settings to every
project and just @INCLUDE the master file there.
However, what I never found out is whether it's actually possible to build a
real inheritance hierarchy with these options. Maybe someone can enlighten
both of us on this matter? E.g. is the following scenario possible: One
concrete project config file @INCLUDEs a general Java config file which in turn
@INCLUDEs a master config file with the common options for all of my projects?
Mit freundlichen Grüßen
Raimund Klein
EDV / Software Entwickler
BERENBERG BANK
Joh. Berenberg, Gossler & Co. KG
Neuer Jungfernstieg 20
20354 Hamburg
Telefon +49 40 350 60-8129
Telefax +49 40 350 60-955
E-Mail raimund.kl...@berenberg.de<mailto:raimund.kl...@berenberg.de>
www.berenberg.de<outbind://75/www.berenberg.de>
Sitz: Hamburg - Amtsgericht Hamburg HRA 42659
Von: Cuckow, Pez [mailto:pez.cuc...@gs.com]<mailto:[mailto:pez.cuc...@gs.com]>
Gesendet: Dienstag, 21. August 2012 12:00
An: 'doxygen-users@lists.sourceforge.net'
Betreff: [Doxygen-users] Multiple Projects, Languages and Shared Config Files
Hi all,
I am new to Doxygen trying to get everyone in my team to look at using it, I've
generated docs for one project and they seemed to like it so looking at
multiple projects, I was wondering if someone could point me in the correct
direction/give me some suggestions.
As a team we manage 5/6 projects, what is the best way to approach this within
Doxygen? Ideally we'd like them to be linked so you can go to one central page
and access all the docs for each project but obviously as code there are no
dependencies between them.
On a further note a few of the projects code bases have 2/3 sets of programing
language for example Java for the server, C# for GUI and some C for some other
services. How does Doxygen code/how best to configure so it copes?
My final question (appreciate this is a long one) is, is it possible to inherit
config files? Ideally I'd like to be able to make one "master file", and then
have one for each project with any project specific settings that all inherit
the defaults from the master!
Thanks for your time,
Pez
Diese Nachricht einschliesslich etwa beigefuegter Anhaenge ist vertraulich und
kann dem Bank- und Datengeheimnis unterliegen oder sonst rechtlich geschuetzte
Daten und Informationen enthalten. Wenn Sie nicht der richtige Adressat sind
oder diese Nachricht irrtuemlich erhalten haben, informieren Sie bitte sofort
den Absender über die Antwortfunktion. Anschliessend moechten Sie bitte diese
Nachricht einschliesslich etwa beigefuegter Anhaenge unverzueglich vollstaendig
loeschen. Das unerlaubte Kopieren oder Speichern dieser Nachricht und/oder der
ihr etwa beigefuegten Anhaenge sowie die unbefugte Weitergabe der darin
enthaltenen Daten und Informationen sind nicht gestattet. Wir weisen darauf
hin, dass rechtsverbindliche Erklaerungen namens unseres Hauses grundsaetzlich
der Unterschriften zweier ausreichend bevollmaechtigter Vertreter unseres
Hauses beduerfen. Wir verschicken daher keine rechtsverbindlichen Erklaerungen
per E-Mail an Dritte. Demgemaess nehmen wir per E-Mail auch keine
rechtsverbindlichen Erklaerungen oder Auftraege von Dritten entgegen.
Sollten Sie Schwierigkeiten beim Oeffnen dieser E-Mail haben, wenden Sie sich
bitte an den Absender oder an i...@berenberg.de<mailto:i...@berenberg.de>.
Please refer to http://www.berenberg.de/my_berenberg/disclaimer_e.html for our
confidentiality notice.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users
