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

Makefile for Docsets does not honor DESTDIR (Origin: bugzilla #597518) #3551

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

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

On 2009-10-06 07:53:13 +0000, Jens Miltner wrote:

When creating Xcode Docsets with doxygen (which, BTW, is a very nice addition), the generated Makefile will always install into ~/Library/Developer/Shared/Documentation/DocSets.

We have an Xcode project that builds documentation for our frameworks and I would like to have the documentation not being installed in ~/Library/Developer/Shared/Documentation/DocSets, but rather in a location defined by me (in this case the project's output location). I therefore tried to run make with DESTDIR=$ouputDir, but found that the Makefile that doxygen generates will ignore the DESTDIR environment variable and use the hardcoded installation path instead.

It would be very nice if the generated Makefile would honor the DESTDIR variable, like most other standard Makefiles do for installation.

On 2009-10-25 08:46:41 +0000, Dimitri van Heesch wrote:

This is already possible if you use DOCSET_INSTALL instead of DESTDIR, but it makes sense to use DESTDIR indeed.

On 2009-12-30 13:38:49 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.2. Please verify if this is indeed the case and reopen the
bug if you think it is not fixed (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