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

#define in included file in different directory not handled properly (Origin: bugzilla #627371) #3907

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

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2010-08-19 14:55:27 +0000, Lukas Middendorf wrote:

I have a very simple test case where I have a source file which includes a header with some defines from a different directory.

All defines made in the header are not used by doxygen. The header is processed which I can see from the fact that every define in the header can not be overwritten by a new define in the source file.

The doxygen documentation for the attached testcase only shows the typedef "blubbla" and not the other two typedefs. It should show all three.

To reproduce extract the archive and run "doxygen" in doxytest/source.

I'm using doxygen 1.7.1 from fedora 13.

On 2010-08-21 14:33:02 +0000, Dimitri van Heesch wrote:

Can you please attach the example you mentioned?

On 2010-08-21 14:43:25 +0000, Lukas Middendorf wrote:

Created attachment 168453
Test case

Sorry for the missing attachment. I guess I forgot to fill in the description field for the attachment in the original report and it just got dropped silently.

On 2010-08-21 17:09:56 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

As a workaround you could add the include directory to the INPUT list.

On 2010-10-09 08:19:33 +0000, Dimitri van Heesch wrote:

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