[prev in list] [next in list] [prev in thread] [next in thread] 

List:       doxygen-users
Subject:    Re: [Doxygen-users] Multiple Projects, Languages and Shared Config Files
From:       "Cuckow, Pez" <Pez.Cuckow () gs ! com>
Date:       2012-08-21 16:18:45
Message-ID: B7D572E1B916084BB85E69BCC27B510F2BF0576031 () GSCMEUP15EX ! firmwide ! corp ! gs ! com
[Download RAW message or body]

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.Klein@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 an=
d link statically to the generated documentation.

-          If you want to ensure a consistent appearance, you can just crea=
te another general documentation project which will only consist of files w=
ith comments. (AFAIK This is how Dimitri maintains the Doxygen website itse=
lf.)

I'll combine the replies to your other questions, as we have a similar setu=
p: 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_P=
ATH and @INCLUDE for the configuration: http://www.stack.nl/~dimitri/doxyge=
n/config.html combined with doxygen's ability to process configuration sett=
ings 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 enlight=
en 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 p=
rojects?


Mit freundlichen Gr=FC=DFen
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.klein@berenberg.de<mailto:raimund.klein@berenberg.de>
www.berenberg.de<outbind://75/www.berenberg.de>

Sitz: Hamburg - Amtsgericht Hamburg HRA 42659
Von: Cuckow, Pez [mailto:Pez.Cuckow@gs.com]<mailto:[mailto:Pez.Cuckow@gs.co=
m]>
Gesendet: Dienstag, 21. August 2012 12:00
An: 'doxygen-users@lists.sourceforge.net'
Betreff: [Doxygen-users] Multiple Projects, Languages and Shared Config Fil=
es

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 a=
t multiple projects, I was wondering if someone could point me in the corre=
ct direction/give me some suggestions.

As a team we manage 5/6 projects, what is the best way to approach this wit=
hin Doxygen? Ideally we'd like them to be linked so you can go to one centr=
al page and access all the docs for each project but obviously as code ther=
e are no dependencies between them.

On a further note a few of the projects code bases have 2/3 sets of program=
ing language for example Java for the server, C# for GUI and some C for som=
e 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 inh=
erit config files? Ideally I'd like to be able to make one "master file", a=
nd then have one for each project with any project specific settings that a=
ll 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 gesc=
huetzte Daten und Informationen enthalten. Wenn Sie nicht der richtige Adre=
ssat sind oder diese Nachricht irrtuemlich erhalten haben, informieren Sie =
bitte sofort den Absender =FCber die Antwortfunktion. Anschliessend moechte=
n Sie bitte diese Nachricht einschliesslich etwa beigefuegter Anhaenge unve=
rzueglich vollstaendig loeschen. Das unerlaubte Kopieren oder Speichern die=
ser Nachricht und/oder der ihr etwa beigefuegten Anhaenge sowie die unbefug=
te Weitergabe der darin enthaltenen Daten und Informationen sind nicht gest=
attet. Wir weisen darauf hin, dass rechtsverbindliche Erklaerungen namens u=
nseres Hauses grundsaetzlich der Unterschriften zweier ausreichend bevollma=
echtigter Vertreter unseres Hauses beduerfen. Wir verschicken daher keine r=
echtsverbindlichen 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 si=
ch bitte an den Absender oder an info@berenberg.de<mailto:info@berenberg.de=
>. Please refer to http://www.berenberg.de/my_berenberg/disclaimer_e.html f=
or our confidentiality notice.

[Attachment #3 (text/html)]

<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type \
content="text/html; charset=iso-8859-1"><meta name=Generator content="Microsoft Word \
14 (filtered medium)"><style><!-- /* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:237709159;
	mso-list-type:hybrid;
	mso-list-template-ids:-1495099560 132149664 67567619 67567621 67567617 67567619 \
67567621 67567617 67567619 67567621;} @list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:53.25pt;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:89.25pt;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:125.25pt;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:161.25pt;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:197.25pt;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:233.25pt;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:269.25pt;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:305.25pt;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:341.25pt;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link=blue vlink=purple><div \
class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Liebe \
Raimund,<o:p></o:p></span></p><p class=MsoNormal><span \
style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span \
style='color:#1F497D'>First of all thanks for all the detailed \
info,<o:p></o:p></span></p><p class=MsoNormal><span \
style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span \
style='color:#1F497D'>I&#8217;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!<o:p></o:p></span></p><p class=MsoNormal><span \
style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span \
style='color:#1F497D'>MfG,<o:p></o:p></span></p><p class=MsoNormal><span \
style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span \
style='color:#1F497D'>Pez<o:p></o:p></span></p><p class=MsoNormal><span \
style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div \
style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p \
class=MsoNormal style='margin-left:36.0pt'><b><span lang=EN-US \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-GB'>From:</span></b><span \
lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-GB'> \
Klein, Raimund [mailto:Raimund.Klein@berenberg.de] <br><b>Sent:</b> Tuesday, August \
21, 2012 2:09 PM<br><b>To:</b> doxygen-users@lists.sourceforge.net<br><b>Subject:</b> \
Re: [Doxygen-users] Multiple Projects, Languages and Shared Config \
Files<br><b>Importance:</b> High<o:p></o:p></span></p></div></div><p class=MsoNormal \
style='margin-left:36.0pt'><o:p>&nbsp;</o:p></p><p class=MsoNormal \
style='margin-left:36.0pt'><span lang=EN-US style='color:#1F497D'>Hi \
Pez,<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span \
lang=EN-US style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal \
style='margin-left:36.0pt'><span lang=EN-US style='color:#1F497D'>Welcome to the \
Light. </span><span lang=DE style='font-family:Wingdings;color:#1F497D'>J</span><span \
lang=EN-US style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal \
style='margin-left:36.0pt'><span lang=EN-US \
style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal \
style='margin-left:36.0pt'><span lang=EN-US style='color:#1F497D'>As to your first \
question, you have basically two ways:<o:p></o:p></span></p><p class=MsoListParagraph \
style='margin-left:89.25pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if \
!supportLists]><span lang=EN-US style='color:#1F497D'><span \
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New \
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \
</span></span></span><![endif]><span lang=EN-US style='color:#1F497D'>The obvious way \
is to just create a master HTML page manually and link statically to the generated \
documentation.<o:p></o:p></span></p><p class=MsoListParagraph \
style='margin-left:89.25pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if \
!supportLists]><span lang=EN-US style='color:#1F497D'><span \
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New \
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \
</span></span></span><![endif]><span lang=EN-US style='color:#1F497D'>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.)<o:p></o:p></span></p><p class=MsoNormal \
style='margin-left:36.0pt'><span lang=EN-US \
style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal \
style='margin-left:36.0pt'><span lang=EN-US style='color:#1F497D'>I&#8217;ll combine \
the replies to your other questions, as we have a similar setup: We&#8217;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: <a href="http://www.stack.nl/~dimitri/doxygen/config.html">http://www.stack.nl/~dimitri/doxygen/config.html</a> \
combined with doxygen&#8217;s ability to process configuration settings via stdin \
(look at <a href="http://www.stack.nl/~dimitri/doxygen/faq.html%20Item%20#17">http://www.stack.nl/~dimitri/doxygen/faq.html \
Item #17</a>). Of course, you can also just add a single doxyfile with additional \
settings to every project and just @INCLUDE the master file \
there.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span \
lang=EN-US style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal \
style='margin-left:36.0pt'><span lang=EN-US style='color:#1F497D'>However, what I \
never found out is whether it&#8217;s actually possible to build a real \
&nbsp;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?<o:p></o:p></span></p><p \
class=MsoNormal style='margin-left:36.0pt'><span lang=EN-US \
style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal \
style='margin-left:36.0pt'><span lang=EN-US \
style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt'><span \
lang=DE style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D;mso-fareast-language:DE'>Mit \
freundlichen Grüßen <o:p></o:p></span></p><p class=MsoNormal \
style='mso-margin-top-alt:3.0pt;margin-right:0cm;margin-bottom:3.0pt;margin-left:36.0pt'><span \
lang=DE style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D;mso-fareast-language:DE'>Raimund \
Klein</span><span lang=DE style='font-size:12.0pt;font-family:"Times New \
Roman","serif";color:#1F497D;mso-fareast-language:DE'><o:p></o:p></span></p><p \
class=MsoNormal style='margin-left:36.0pt'><span lang=DE \
style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#1F497D;mso-fareast-language:DE'>EDV \
/ Software Entwickler<o:p></o:p></span></p><p class=MsoNormal \
style='mso-margin-top-alt:6.0pt;margin-right:0cm;margin-bottom:3.0pt;margin-left:36.0pt'><span \
lang=DE style='font-size:6.0pt;font-family:"Arial","sans-serif";color:#1F497D;mso-fareast-language:DE'><o:p>&nbsp;</o:p></span></p><p \
class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:3.0pt;margin-left:36.0pt'><span \
lang=DE style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#FF9900;mso-fareast-language:DE'>BERENBERG \
BANK<o:p></o:p></span></p><p class=MsoNormal \
style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:2.0pt;margin-left:36.0pt'><span \
lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D;mso-fareast-language:DE'>Joh. \
Berenberg, Gossler &amp; Co. KG<o:p></o:p></span></p><p class=MsoNormal \
style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:2.0pt;margin-left:36.0pt'><span \
lang=DE style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#1F497D;mso-fareast-language:DE'>Neuer \
Jungfernstieg 20<o:p></o:p></span></p><p class=MsoNormal \
style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:2.0pt;margin-left:36.0pt'><span \
lang=DE style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#1F497D;mso-fareast-language:DE'>20354 \
Hamburg<o:p></o:p></span></p><p class=MsoNormal \
style='mso-margin-top-alt:2.0pt;margin-right:0cm;margin-bottom:2.0pt;margin-left:36.0pt'><span \
lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D;mso-fareast-language:DE'><o:p>&nbsp;</o:p></span></p><p \
class=MsoNormal style='mso-margin-top-alt:2.0pt;margin-right:0cm;margin-bottom:2.0pt;margin-left:36.0pt'><span \
lang=DE style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#1F497D;mso-fareast-language:DE'>Telefon \
+49 40 350 60-8129</span><span lang=DE style='font-size:12.0pt;font-family:"Times New \
Roman","serif";color:#1F497D;mso-fareast-language:DE'><o:p></o:p></span></p><p \
class=MsoNormal style='mso-margin-top-alt:2.0pt;margin-right:0cm;margin-bottom:2.0pt;margin-left:36.0pt'><span \
lang=DE style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#1F497D;mso-fareast-language:DE'>Telefax \
+49 40 350 60-955<o:p></o:p></span></p><p class=MsoNormal \
style='mso-margin-top-alt:2.0pt;margin-right:0cm;margin-bottom:2.0pt;margin-left:36.0pt'><span \
lang=DE style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#1F497D;mso-fareast-language:DE'>E-Mail \
<a href="mailto:raimund.klein@berenberg.de">raimund.klein@berenberg.de</a><o:p></o:p></span></p><p \
class=MsoNormal style='mso-margin-top-alt:2.0pt;margin-right:0cm;margin-bottom:2.0pt;margin-left:36.0pt'><span \
lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D;mso-fareast-language:DE'><a \
href="outbind://75/www.berenberg.de" title="outbind://75/www.berenberg.de"><span \
style='font-size:7.5pt'>www.berenberg.de</span></a><o:p></o:p></span></p><p \
class=MsoNormal style='margin-left:36.0pt'><span lang=DE \
style='font-size:6.0pt;font-family:"Arial","sans-serif";color:#1F497D;mso-fareast-language:DE'><o:p>&nbsp;</o:p></span></p></div><p \
class=MsoNormal style='margin-left:36.0pt'><span lang=DE \
style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#1F497D;mso-fareast-language:DE'>Sitz: \
Hamburg - Amtsgericht Hamburg HRA 42659</span><span \
lang=DE><o:p></o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF \
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal \
style='margin-left:36.0pt'><b><span lang=DE \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:DE'>Von:</span></b><span \
lang=DE style='font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:DE'> \
Cuckow, Pez <a href="mailto:[mailto:Pez.Cuckow@gs.com]">[mailto:Pez.Cuckow@gs.com]</a> \
<br><b>Gesendet:</b> Dienstag, 21. August 2012 12:00<br><b>An:</b> \
'doxygen-users@lists.sourceforge.net'<br><b>Betreff:</b> [Doxygen-users] Multiple \
Projects, Languages and Shared Config Files<o:p></o:p></span></p></div></div><p \
class=MsoNormal style='margin-left:36.0pt'><span \
lang=DE><o:p>&nbsp;</o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'>Hi \
all,<o:p></o:p></p><p class=MsoNormal \
style='margin-left:36.0pt'><o:p>&nbsp;</o:p></p><p class=MsoNormal \
style='margin-left:36.0pt'>I am new to Doxygen trying to get everyone in my team to \
look at using it, I&#8217;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.<o:p></o:p></p><p class=MsoNormal \
style='margin-left:36.0pt'><o:p>&nbsp;</o:p></p><p class=MsoNormal \
style='margin-left:36.0pt'>As a team we manage 5/6 projects, what is the best way to \
approach this within Doxygen? Ideally we&#8217;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.<o:p></o:p></p><p class=MsoNormal \
style='margin-left:36.0pt'><o:p>&nbsp;</o:p></p><p class=MsoNormal \
style='margin-left:36.0pt'>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?<o:p></o:p></p><p class=MsoNormal \
style='margin-left:36.0pt'><o:p>&nbsp;</o:p></p><p class=MsoNormal \
style='margin-left:36.0pt'>My final question (appreciate this is a long one) is, is \
it possible to inherit config files? Ideally I&#8217;d like to be able to make one \
&#8220;master file&#8221;, and then have one for each project with any project \
specific settings that all inherit the defaults from the master!<o:p></o:p></p><p \
class=MsoNormal style='margin-left:36.0pt'><o:p>&nbsp;</o:p></p><p class=MsoNormal \
style='margin-left:36.0pt'>Thanks for your time,<o:p></o:p></p><p class=MsoNormal \
style='margin-left:36.0pt'><o:p>&nbsp;</o:p></p><p class=MsoNormal \
style='margin-left:36.0pt'>Pez<o:p></o:p></p><p style='margin-left:36.0pt'><span \
lang=DE>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. <br>Sollten Sie Schwierigkeiten beim Oeffnen dieser E-Mail haben, wenden \
Sie sich bitte an den Absender oder an <a \
href="mailto:info@berenberg.de">info@berenberg.de</a>. Please refer to <a \
href="http://www.berenberg.de/my_berenberg/disclaimer_e.html">http://www.berenberg.de/my_berenberg/disclaimer_e.html</a> \
for our confidentiality notice.<o:p></o:p></span></p></div></body></html>


[Attachment #4 (--===============4754079131311034025==)]
------------------------------------------------------------------------------
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


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic