doxygen-users — List for users of doxygen

Re: [Doxygen-users] Error in file XX.f90 line:3468, state 4

[Albert <alb...@gm...>]

Hi Fabian,

The line number is the number where it saw a problem and in this case this
is when the file has been completely parsed.
The state 4 means an error with SubprogBody, so something not ended
properly (I assume the file compiles properly).

You are using version 1.6.1 and the current version is 1.8.7 so an upgrade
would certainly help.
During the run does it say something about prepassing XX.f90 ?
so like:
Reading .../XX.f90
Prepassing fixed form of .../XX.f90
Parsing file XX.f90

The line
Prepassing fixed form of .../XX.f90
should not be present, if present try to place a ! as fist line in the
XX.f90 file.

Anyhow upgrading to 1.8.7 is a very good idea.

Albert



On Tue, May 13, 2014 at 11:46 AM, Fabian Nick <
fab...@sc...> wrote:

> Hi everyone,
>
> when trying to run doxygen on a large (Fortran-)project, I get the "Error
> in file XX.f90 line:3468, state 4" error. The interesting thing is that the
> file only has 3466 lines...
> The file is in fixed format. Somewhere on the web it was said that
> enabling the C-preprocessor might help but it doesn't in my case. I also
> read that there was a bug which was fixed in version 1.5.6 (I think),
> however I'm using version 1.6.1.
>
> Any advice on what I could try?
>
> Regards,
> Fabian
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform
> available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>

[Doxygen-users] Error in file XX.f90 line:3468, state 4

[Fabian N. <fab...@sc...>]

Hi everyone,

when trying to run doxygen on a large (Fortran-)project, I get the "Error in file XX.f90 line:3468, state 4" error. The interesting thing is that the file only has 3466 lines...
The file is in fixed format. Somewhere on the web it was said that enabling the C-preprocessor might help but it doesn't in my case. I also read that there was a bug which was fixed in version 1.5.6 (I think), however I'm using version 1.6.1.

Any advice on what I could try?

Regards,
Fabian

[Doxygen-users] Make mentions of formal parameter names more obvious

[John Y. <jo...@ya...>]

I use \p to mark mentions of formal parameters.  The manual suggests that
this is indeed \p's intented role ("You can use this command to refer to
member function parameters in the running text").  Unfortunately that same
manual also supplies an excessively specific operational description of
\p's effect ("Displays the parameter <word> using a typewriter font. ... To
have multiple words in typewriter font use <tt>multiple words</tt>").
 Worse, based on this operational description it asserts equivalence
between \p and \c ("Equivalent to \c").

My generated documentation uses sans serif fonts for both proportional and
fixed width.  Changing to typewriter is too subtle to clearly call out a
token as a formal parameter name.  I would like to see \p more strongly
tied to marking formal parameters.  In particular I suggest rendering
marked up parameter names using the same font, bolding and color as when
they appears in a function signature.

/john

Re: [Doxygen-users] Distinguish "variables" from "constants"

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

Hi John,

On 04 May 2014, at 17:45 , John Yates <jo...@ya...> wrote:

> I am using 1.8.7 for C++ code.
> 
> It is a sad C++ quirk that that it lacks true constants (say à la Pascal).  What it does have are initialized constant expressions.  Technically within the C++ grammar these are declarations of variables and Doxygen dutifully classifies them as such.  But from the programmer's perspective an initialized const variable is _very_ different from a modifiable variable.  So I would like to request a Doxygen feature that would allow initialized constant variables to be grouped separately from other variables.

I tend to agree. Can you file a bug report for this in the bug tracker with severity set to enhancement?
https://bugzilla.gnome.org/enter_bug.cgi?product=doxygen

Regards,
  Dimitri

[Doxygen-users] Distinguish "variables" from "constants"

[John Y. <jo...@ya...>]

I am using 1.8.7 for C++ code.

It is a sad C++ quirk that that it lacks true constants (say à la Pascal).
 What it does have are initialized constant expressions.  Technically
within the C++ grammar these are declarations of variables and Doxygen
dutifully classifies them as such.  But from the programmer's perspective
an initialized const variable is _very_ different from a modifiable
variable.  So I would like to request a Doxygen feature that would allow
initialized constant variables to be grouped separately from other
variables.

/john

Re: [Doxygen-users] How to customize header & footer in RTF output in DOxygen

[Albert <alb...@gm...>]

Hi Rajmohan,

Did you have a look at:
  doxygen  --help
  doxygen -w rtf styleSheetFile
  doxygen -e rtf extensionsFile
and the following items from the Doxyfile:
  RTF_STYLESHEET_FILE
  RTF_EXTENSIONS_FILE

Albert



On Sun, May 4, 2014 at 10:09 AM, Rajmohan <msr...@gm...> wrote:

> Hi,
>
> I request to know how specific header (with a company logo) & footer (with
> [page numbers) could be configured for a design document for an API written
> in C language.
>
> Greatly appreciate any help.
>
> Thanks and regards,
> Rajmohan
>
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>

[Doxygen-users] How to customize header & footer in RTF output in DOxygen

[Rajmohan <msr...@gm...>]

Hi,

I request to know how specific header (with a company logo) & footer (with 
[page numbers) could be configured for a design document for an API written 
in C language.

Greatly appreciate any help.

Thanks and regards,
Rajmohan

Re: [Doxygen-users] Inclusion of final period in \brief descriptions.

[MK <mk...@co...>]

On Sat, 3 May 2014 14:00:06 +0200
Albert <alb...@gm...> wrote:
> Tried to reproduce it but wasn't successful. Can you create a small
> example including (stripped with the -s option) Doxyfile?

Sure.  Use this as the only source file, "eg.c":

/**\file eg.c
\brief Example source.
*/

/**\defgroup testgrp Test Group
\brief This is sentence one.  This is sentence two. */

/**\ingroup testgrp
\brief Blah blah.
\details These are the details. */
void whatever (void) {
};

Place that in a directory with the attached Doxyfile (this is the
default produced by my 'doxygen -g -s').  Run 'doxygen' and look at 
'html/modules.html':

<td class="desc">This is sentence one. This is sentence two </td>

Notice the period after "two" has been removed. Again, if I place an
extra period in the source to compensate, that extra period will
reappear in other places where the brief description is reproduced
(e.g., together with the detailed description).


Sincerely, MK


-- 
"Enthusiasm is not the enemy of the intellect." (said of Irving Howe)

Re: [Doxygen-users] Get rid of "More..."

[Ken K. <kjk...@ya...>]

MK,

One other solution would be to write a script to remove the "more" link and have it run through your html files.

 

________________________________
 From: MK <mk...@co...>
To: dox...@li... 
Sent: 
Subject: Re: [Doxygen-users] Get rid of "More..."
  

On Fri, 2 May 2014 12:11:49 -0400
John Yates <jo...@ya...> wrote:
> On Fri, May 2, 2014 at 10:52 AM, Sebastien Loriot wrote:
> > I understood you want to get rid of the More link when there is only
> > a brief description. A fix was commited a few release back in this
> > direction.

No, I want to be able to get rid of the "More..." link unequivocally.
I do not want it to depend on anything other than me setting something
like:

USE_MORE_LINK = "no"

If there is no such feature, I guess I am out of luck -- the "More..."
will be there whether I like it or not.

> His earlier email in this thread made the point that the More... link
> _always_ points to the same place as the symbol being documented.
> Since that symbol is already a link the More... link adds no value.

That sums it up.  It also adds repetitive clutter:

[foo()] This is a brief description of foo. More...
[bar()] Something different about bar. More...

And again, "More..." in both cases links to the same place as "foo
()" or "bar()".  

MK

-- 
"Enthusiasm is not the enemy of the intellect." (said of Irving Howe)

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Doxygen-users mailing list
Dox...@li...
https://lists.sourceforge.net/lists/listinfo/doxygen-users

Re: [Doxygen-users] Inclusion of final period in \brief descriptions.

[Albert <alb...@gm...>]

Tried to reproduce it but wasn't successful. Can you create a small example
including (stripped with the -s option) Doxyfile?


On Fri, May 2, 2014 at 1:55 PM, MK <mk...@co...> wrote:

> I have a C library and am generating documentation with the following
> settings using doxygen 1.8.6:
>
> REPEAT_BRIEF           = YES
> JAVADOC_AUTOBRIEF      = NO
> QT_AUTOBRIEF           = NO
> MULTILINE_CPP_IS_BRIEF = YES
>
> The last is intended to include /// style comments although it seems to
> make no difference in this respect (they are included as briefs anyway).
>
> Consider:
>
> /brief This is sentence one.  This is sentence two.
> /details blah blah....
>
> When the /brief comments are included at the top of the page for the
> respective type, or as part of the "Detailed Description" (since
> REPEAT_BRIEF is set), the complete "\brief" comment appears.  But in
> the "Data Structures" list they appear with the last period removed:
>
> This is sentence one.  This is sentence two
>
> If I add an extra period to compensate, then this extra period appears
> in places where the complete brief does appear:
>
> This is sentence one.  This is sentence two.. blah blah
>
> This seems like a bug to me, but I thought I'd ask here first in case
> there is a quick work around.
>
> Sincerely, MK
>
> --
> "Enthusiasm is not the enemy of the intellect." (said of Irving Howe)
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>

Re: [Doxygen-users] Get rid of "More..."

[MK <mk...@co...>]

On Fri, 2 May 2014 12:11:49 -0400
John Yates <jo...@ya...> wrote:
> On Fri, May 2, 2014 at 10:52 AM, Sebastien Loriot wrote:
> > I understood you want to get rid of the More link when there is only
> > a brief description. A fix was commited a few release back in this
> > direction.

No, I want to be able to get rid of the "More..." link unequivocally.
I do not want it to depend on anything other than me setting something
like:

USE_MORE_LINK = "no"

If there is no such feature, I guess I am out of luck -- the "More..."
will be there whether I like it or not.

> His earlier email in this thread made the point that the More... link
> _always_ points to the same place as the symbol being documented.
> Since that symbol is already a link the More... link adds no value.

That sums it up.  It also adds repetitive clutter:

[foo()] This is a brief description of foo. More...
[bar()] Something different about bar. More...

And again, "More..." in both cases links to the same place as "foo
()" or "bar()".  

MK

-- 
"Enthusiasm is not the enemy of the intellect." (said of Irving Howe)

[Doxygen-users] How to document a function that does not exist but has the documentation block?

[Семенов П. <sem...@gm...>]

I want Doxygen to document the code written in C-like language (PARI/GP)
but having slightly different syntax. I believe Doxygen can document the
entities those do not exist. It seems to be the simplest way to do the job
while the programming language is not Doxygen-supported. I want something
like this:

/*!
 \fn foo(param,{option})
 \brief some brief description here
 \param[in](param) mandatory parameter description
 \param[in](option) optional parameter description
*/
/*! \cond DOXYGEN_SHOULD_SKIP_THIS */
foo(param, {option}) =
{
    ...
};
addhelp(foo, "help message for `foo` function");
/*! \endcond */

Unfortunately, Doxygen generates the warning "documented symbol 'foo' was
not declared or defined" and does not list the foo in an output HTML. Is
there any way to force the Doxygen to produce the proper HTML using only
the documentation blocks but not the code?

Thank you very much!

*With best regards, Piotr Semenov*

Re: [Doxygen-users] Get rid of "More..."

[John Y. <jo...@ya...>]

On Fri, May 2, 2014 at 10:52 AM, Sebastien Loriot <slo...@gm...>wrote:

> On 05/02/2014 04:31 PM, MK wrote:
> > I.e., I am asking how to TURN THIS OFF (toggle).   I DO NOT want the
> > "More..." link to appear.    I am asking if this can be DISABLED.
>
> I understood you want to get rid of the More link when there is only
> a brief description. A fix was commited a few release back in this
> direction.
>

I do not think that what he wants is suppression of More... when there is
only a brief description and inclusion of More... when there is additional
information.

If you are looking to remove any long description then it's another
> story.


His earlier email in this thread made the point that the More... link
_always_ points to the same place as the symbol being documented.  Since
that symbol is already a link the More... link adds no value.  Hence he
would like an unconditional means of suppressing that More... link.

/john

Re: [Doxygen-users] Get rid of "More..."

[Sebastien L. <slo...@gm...>]

On 05/02/2014 04:31 PM, MK wrote:
> On Fri, 02 May 2014 15:38:23 +0200
> "Sebastien Loriot (GeometryFactory)" <slo...@gm...> wrote:
>> This is the default, there is nothing to tune.
>
> I can tell it is the default to use it, yes.   But note the title of
> the thread here is 'Get rid of "More..."' and my original question was:
>
> 'Is there some way I can **toggle** the inclusion of the "More..." link
> at the end of brief descriptions?  It's come out in my docs as totally
> superfluous...'
>
> I.e., I am asking how to TURN THIS OFF (toggle).   I DO NOT want the
> "More..." link to appear.    I am asking if this can be DISABLED.
>
> MK
>
I understood you want to get rid of the More link when there is only
a brief description. A fix was commited a few release back in this
direction.

If you are looking to remove any long description then it's another
story.

Sebastien.

Re: [Doxygen-users] Get rid of "More..."

[MK <mk...@co...>]

On Fri, 02 May 2014 15:38:23 +0200
"Sebastien Loriot (GeometryFactory)" <slo...@gm...> wrote:
> This is the default, there is nothing to tune.

I can tell it is the default to use it, yes.   But note the title of
the thread here is 'Get rid of "More..."' and my original question was:

'Is there some way I can **toggle** the inclusion of the "More..." link
at the end of brief descriptions?  It's come out in my docs as totally
superfluous...'

I.e., I am asking how to TURN THIS OFF (toggle).   I DO NOT want the
"More..." link to appear.    I am asking if this can be DISABLED.

MK

-- 
"Enthusiasm is not the enemy of the intellect." (said of Irving Howe)

Re: [Doxygen-users] Get rid of "More..."

[Sebastien L. (GeometryFactory) <slo...@gm...>]

On 05/02/2014 03:14 PM, MK wrote:
> On Fri, 02 May 2014 14:42:25 +0200
> Sebastien Loriot <slo...@gm...> wrote:
>> On 05/02/2014 02:26 PM, MK wrote:
>>> Is there some way I can toggle the inclusion of the "More..." link
>>>
>> The fix has been included into doxygen for some releases now.
>> You can try 1.8.7 for example.
>
> Okay.  What am I looking for in order to do this?  Something in the
> Doxyfile configuration or in the .xml layout?
>
> I have tried searching the online manual for references to "More..."
> but unfortunately there are a lot of generated pages there that contain
> that.
>
> MK
>
This is the default, there is nothing to tune.



Sebastien.

Re: [Doxygen-users] Get rid of "More..."

[MK <mk...@co...>]

On Fri, 02 May 2014 14:42:25 +0200
Sebastien Loriot <slo...@gm...> wrote:
> On 05/02/2014 02:26 PM, MK wrote:
> > Is there some way I can toggle the inclusion of the "More..." link
> >
> The fix has been included into doxygen for some releases now.
> You can try 1.8.7 for example.

Okay.  What am I looking for in order to do this?  Something in the
Doxyfile configuration or in the .xml layout?

I have tried searching the online manual for references to "More..."
but unfortunately there are a lot of generated pages there that contain
that.

MK

-- 
"Enthusiasm is not the enemy of the intellect." (said of Irving Howe)

Re: [Doxygen-users] Get rid of "More..."

[Sebastien L. <slo...@gm...>]

On 05/02/2014 02:26 PM, MK wrote:
> Is there some way I can toggle the inclusion of the "More..." link at
> the end of brief descriptions?  It's come out in my docs as totally
> superfluous since it follows, e.g., the function or type name which is
> a link to the exact same place.
>
> Sincerely, MK
>
The fix has been included into doxygen for some releases now.
You can try 1.8.7 for example.

Sebastien.

[Doxygen-users] Inclusion of final period in \brief descriptions.

[MK <mk...@co...>]

I have a C library and am generating documentation with the following
settings using doxygen 1.8.6:

REPEAT_BRIEF           = YES
JAVADOC_AUTOBRIEF      = NO   
QT_AUTOBRIEF           = NO     
MULTILINE_CPP_IS_BRIEF = YES 

The last is intended to include /// style comments although it seems to
make no difference in this respect (they are included as briefs anyway).

Consider:

/brief This is sentence one.  This is sentence two.
/details blah blah....

When the /brief comments are included at the top of the page for the
respective type, or as part of the "Detailed Description" (since
REPEAT_BRIEF is set), the complete "\brief" comment appears.  But in
the "Data Structures" list they appear with the last period removed:

This is sentence one.  This is sentence two

If I add an extra period to compensate, then this extra period appears
in places where the complete brief does appear:

This is sentence one.  This is sentence two.. blah blah

This seems like a bug to me, but I thought I'd ask here first in case
there is a quick work around.

Sincerely, MK

-- 
"Enthusiasm is not the enemy of the intellect." (said of Irving Howe)

[Doxygen-users] Get rid of "More..."

[MK <mk...@co...>]

Is there some way I can toggle the inclusion of the "More..." link at
the end of brief descriptions?  It's come out in my docs as totally
superfluous since it follows, e.g., the function or type name which is
a link to the exact same place.

Sincerely, MK

-- 
"Enthusiasm is not the enemy of the intellect." (said of Irving Howe)

Re: [Doxygen-users] Hyperlink around PROJECT_LOGO

[Stefan P. <ste...@gm...>]

Am 25.04.2014 08:29, schrieb Marcus Stein:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi @all,
>
> I'm using PROJECT_LOGO to add a company logo in the top-left corner
> of the HTML documentation.
>
> Is it possible to add a hyperlink to such image so that the user may
> easily navigate back to e.g. a custom start page?

Generally, you would just change the HTML header file and use a custom 
one, that has the link specified.


--
Stefan P.

Top-posting:
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

[Doxygen-users] Hyperlink around PROJECT_LOGO

[Marcus S. <mar...@ho...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi @all,

I'm using PROJECT_LOGO to add a company logo in the top-left corner
of the HTML documentation.

Is it possible to add a hyperlink to such image so that the user may
easily navigate back to e.g. a custom start page?


And many thanks for doxygen itself! We're using it for ~2000 in-house
components, libraries and applications :-)


Best regards,
Marcus

- -- 
Marcus Stein

Honda Research Institute Europe GmbH
Carl-Legien-Str. 30
63073 Offenbach/Main
Germany

Phone: +49 (0)69 / 89011-762
E-Mail: mar...@ho...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlNaALIACgkQ2no6WRGAe0TbbgCgqPknRm3IyPaC5zdh+p58abmP
uXsAoIPXphNW+9UOkYO7B1adgDfQ/Iwo
=vkcT
-----END PGP SIGNATURE-----

Re: [Doxygen-users] influencing rerun loop of pdflatex build?

[Albert <alb...@gm...>]

In the current version of doxygen (1.8.7) the value is set to 8. Otherwise
I think the only way is to change the value by hand/script before running
make on the Makefile / running make.bat as it is hard coded in the code.


On Thu, Apr 24, 2014 at 6:23 PM, Albert <alb...@gm...> wrote:

> In the current version of doxygen (1.8.7) the value is set to 8. Otherwise
> I think the only way is to change the value by hand/script before running
> make on the Makefile / running make.bat as it is hard coded in the code.
>
>
> On Thu, Apr 24, 2014 at 5:21 PM, Peter Danecek <Pet...@bo...>wrote:
>
>>
>> Hi all,
>>
>> I have little experience in using doxygen, but came about a problem with
>> building globus_ftp_control, which uses it, during its build process.
>>
>> For the build of the PDF documentation, there is a Makefile created with
>> a loop to rerun pdflatex several times. If I understand the logic right, it
>> should rerun pdflates as often as necessary or if a maximum no. of rebuilds
>> is reached, which is set to 5. However, for in my special situation the
>> document requires exactly 5 runs until the document has converged. This
>> however caused the expr construct to exit with a non zero exit code, and as
>> a consequences the make command fails.
>>
>> One possibility would be to increase the no. of max. cycles. But I have
>> not found a way to influence this no. by a parameter in the Doxyfile. So is
>> there a way to influences this no., e.g set it to 6 or 8 or some other
>> arbitrary value? How exactly, this is done? Or, is there some other
>> solution to solve this issue?
>>
>> Thanks!
>> ~petr
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Start Your Social Network Today - Download eXo Platform
>> Build your Enterprise Intranet with eXo Platform Software
>> Java Based Open Source Intranet - Social, Extensible, Cloud Ready
>> Get Started Now And Turn Your Intranet Into A Collaboration Platform
>> http://p.sf.net/sfu/ExoPlatform
>> _______________________________________________
>> Doxygen-users mailing list
>> Dox...@li...
>> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>>
>>
>

[Doxygen-users] influencing rerun loop of pdflatex build?

[Peter D. <Pet...@bo...>]

Hi all,

I have little experience in using doxygen, but came about a problem with building globus_ftp_control, which uses it, during its build process.

For the build of the PDF documentation, there is a Makefile created with a loop to rerun pdflatex several times. If I understand the logic right, it should rerun pdflates as often as necessary or if a maximum no. of rebuilds is reached, which is set to 5. However, for in my special situation the document requires exactly 5 runs until the document has converged. This however caused the expr construct to exit with a non zero exit code, and as a consequences the make command fails. 

One possibility would be to increase the no. of max. cycles. But I have not found a way to influence this no. by a parameter in the Doxyfile. So is there a way to influences this no., e.g set it to 6 or 8 or some other arbitrary value? How exactly, this is done? Or, is there some other solution to solve this issue?

Thanks!
~petr

Re: [Doxygen-users] Tagfiles across network drives

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

On 15 Apr 2014, at 19:10 , Stephen Gerbrandt <Ste...@me...> wrote:

> I’m working on setting up Doxygen to run on our build machines every time we compile one of our projects, and one of the requirements I have to work around is moving all of our Doxygen output files to a shared network drive location that all users have access to. Most of the Doxygen generation works fine in this regard, however I am having a difficult time trying to understand how to link up a tagfile generated from our main engine in each of our various projects. I can get it to work fine when they are located on the same drive:
>  
> TAGFILES = "/SSIIIDocs/DoxygenFiles/$(ENGINE_NAME)/SharedSource/sharedsource.tag = /SSIIIDocs/DoxygenFiles/$(ENGINE_NAME)/SharedSource "
>  
> However no matter what I’ve tried to specify a network location it fails to find it. My most recent attempt is this:
>  
> TAGFILES  = \\networkDrive\SSIIIDocs\DoxygenFiles\$(ENGINE_NAME)\SharedSource\sharedsource.tag = \\networkDrive\SSIIIDocs\DoxygenFiles\$(ENGINE_NAME)\SharedSource
>  
> Am I missing something on how to properly set this up or is it not possible to link to a tagfile located on a network drive at the time of generation?

Doxygen doesn't work well with UNC style paths (http://en.wikipedia.org/wiki/Path_%28computing%29#UNC_in_Windows).
The best solution is to map the path to a drive letter first. 

Regards,
  Dimitri