Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MSCFILE_DIRS doxyfile property does not work for multiple paths (Origin: bugzilla #646463) #4228

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

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

On 2011-04-01 17:40:24 +0000, Aaron wrote:

I have tried to place 2 paths in the MSCFILE_DIRS property and it appears only the first path is used.

I have tried both of the following formats in my doxyfile:

MSCFILE_DIRS = path1
path2

MSCFILE_DIRS = path1
MSCFILE_DIRS += path2

My corresponding \mscfile tags then only find the files located under path1.

Although I have not tried it, I suspect the DOTFILE_DIRS property may have the same limitation, however the comments indicate they should support more than one directory.

'The MSCFILE_DIRS tag can be used to specify one or more directories that contain dot files that are included in the documentation (see the \dotfile command).'
'The DOTFILE_DIRS tag can be used to specify one or more directories that contain dot files that are included in the documentation (see the \dotfile command).'

On 2011-04-01 17:56:18 +0000, Dimitri van Heesch wrote:

Hi Aaron,

Turns out to be a copy-paste error:
In src/doxygen.cpp the following is used to iterate over the directories:

s=mscFileList.first();
while (s)
{
readFileOrDirectory(s,0,Doxygen::mscFileNameDict,0,0,
0,0,0,
alwaysRecursive);
s=dotFileList.next();
}

the dotFileList.next() should have been mscFileList.next()

Should be fixed in the next subversion update.

On 2011-08-14 14:05:21 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.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.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.