Confusing use of GENERATE_TAGFILE (Origin: bugzilla #706236)

[doxygen]

status VERIFIED severity normal in component general for ---
Reported in version 1.8.4 on platform Other
Assigned to: Dimitri van Heesch

On 2013-08-18 12:25:27 +0000, albert wrote:

The GENERATE_... tags are all of the type 'bool' (YES / NO) with the exception of GENERATE_TAGFILE. The later one is of type 'string' and when set the value is used as file name. In case of the usage of the value 'No' this results in a tag file with the name 'No'

Proposed change:

• GENERATE_TAGFILE = -> as it is at the moment
• GENERATE_TAGFILE = -> as it is at the moment
• GENERATE_TAGFILE = NO -> warning an there will be no tag file generated
• GENERATE_TAGFILE = YES -> warning an there will be no tag file generated

On 2013-08-18 13:24:33 +0000, albert wrote:

Resolution has been pushed to git repository and a pull request has been emitted.

On 2013-08-22 12:38:19 +0000, Dimitri van Heesch wrote:

Thanks, I'll include a modified version of the patch in the next GIT update.

On 2013-08-22 16:40:55 +0000, albert wrote:

The chosen solution with overwriting the option value is indeed an easier way.
Checked with my example and there is no tagfile generated when I set GENERATE_TAGFILE to NO

On 2013-08-23 15:04:16 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.5. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.

On 2013-08-23 17:12:00 +0000, albert wrote:

Works as expected