Use abspath for doxyfile to stop failure #163
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This simple change use an absolute path rather than a relative path to locate the Doxyfile.
Generally the absolute vs relative path decisions in rosdoc2 are all over the map, and really need a thorough review.
In the current case, a problem occurred on my local build farm, where the locations of files were set using NFS to locations, with soft links to the actual disk storage locations. The error message in Doxygen reported the actual disk location (that is, with the soft link resolved). That caused a mismatch of the '..' count in the relative link. Perhaps somewhere Doxygen is resolving soft links. Really relative paths do not make sense in calls like this to Doxygen, as we are using relative directories on files that could be on completely separate file systems.
I could live without this change as the problem is only occurring locally for me, but I really think the absolute call is the correct way to do this, hence this change in the core code.