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

[PATCH] #include does not work with absolute paths (Origin: bugzilla #711639) #5344

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.8.3.1 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2013-11-07 22:40:09 +0000, Matthew Woehlke wrote:

While trying to determine why preprocessor symbols I expected to be expanded were not being expanded, I discovered this:

#include /absolute/path/to/existing/header.h: not found! skipping...

AFAICT, doxygen's preprocessor is not able to handle #include directives when an absolute path is given for the include file name. Inspecting findFile() in pre.l seems to bear this out; the code there does indeed appear to only ever check the file name by appending it to the 'current' directory or one of the specified include directories, which will only work for relative file paths.

On 2013-11-07 22:48:57 +0000, Matthew Woehlke wrote:

Created attachment 259231
patch

On 2013-11-11 19:42:30 +0000, Dimitri van Heesch wrote:

Thanks, I'll include the patch in the next GIT update.

On 2013-12-24 18:59:32 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.6. 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 (preferrably in the form of a self-contained example).

@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.