Doxygen error: failed to run html help compiler on index.hhp
So I am having this problem where I get an error when trying to get a .chm file for doxygen.
sh: C:Program FilesHTML Help Workshophhc.exe: no se encontró la orden (command not found)
error: failed to run html help compiler on index.hhp
In my doxyfile I have the following set this way.
GENERATE_HTMLHELP = YES
CHM_FILE = index.chm
HHC_LOCATION = "C:Program Files (x86)HTML Help Workshophhc.exe"
It's seriously driving me nuts and I don't find anything anywhere. Please help.
doxygen
asked Nov 11 '15 at 19:44
CrueloCruelo
2815
add a comment |
So I am having this problem where I get an error when trying to get a .chm file for doxygen.
sh: C:Program FilesHTML Help Workshophhc.exe: no se encontró la orden (command not found)
error: failed to run html help compiler on index.hhp
In my doxyfile I have the following set this way.
GENERATE_HTMLHELP = YES
CHM_FILE = index.chm
HHC_LOCATION = "C:Program Files (x86)HTML Help Workshophhc.exe"
It's seriously driving me nuts and I don't find anything anywhere. Please help.
doxygen
asked Nov 11 '15 at 19:44
CrueloCruelo
2815
Which version of doxygen are we talking about?
– albert
Nov 12 '15 at 17:56
Try dir /x on the "Program Files (x86)" directory from the command line and use the short name instead. Probably the version of doxygen you used doesn't like (x86) junk in the name.
– doxygen
Nov 12 '15 at 18:39
A good setting might also beHHC_LOCATION = ""C:Program Files (x86)HTML Help Workshophhc.exe""
– albert
Sep 27 '18 at 8:23
add a comment |
So I am having this problem where I get an error when trying to get a .chm file for doxygen.
sh: C:Program FilesHTML Help Workshophhc.exe: no se encontró la orden (command not found)
error: failed to run html help compiler on index.hhp
In my doxyfile I have the following set this way.
GENERATE_HTMLHELP = YES
CHM_FILE = index.chm
HHC_LOCATION = "C:Program Files (x86)HTML Help Workshophhc.exe"
It's seriously driving me nuts and I don't find anything anywhere. Please help.
doxygen
asked Nov 11 '15 at 19:44
CrueloCruelo
2815
So I am having this problem where I get an error when trying to get a .chm file for doxygen.
sh: C:Program FilesHTML Help Workshophhc.exe: no se encontró la orden (command not found)
error: failed to run html help compiler on index.hhp
In my doxyfile I have the following set this way.
GENERATE_HTMLHELP = YES
CHM_FILE = index.chm
HHC_LOCATION = "C:Program Files (x86)HTML Help Workshophhc.exe"
It's seriously driving me nuts and I don't find anything anywhere. Please help.
doxygen
doxygen
asked Nov 11 '15 at 19:44
CrueloCruelo
2815
asked Nov 11 '15 at 19:44
CrueloCruelo
2815
asked Nov 11 '15 at 19:44
CrueloCruelo
2815
asked Nov 11 '15 at 19:44
CrueloCruelo
2815
asked Nov 11 '15 at 19:44
CrueloCruelo
2815
2815
Which version of doxygen are we talking about?
– albert
Nov 12 '15 at 17:56
Try dir /x on the "Program Files (x86)" directory from the command line and use the short name instead. Probably the version of doxygen you used doesn't like (x86) junk in the name.
– doxygen
Nov 12 '15 at 18:39
A good setting might also beHHC_LOCATION = ""C:Program Files (x86)HTML Help Workshophhc.exe""
– albert
Sep 27 '18 at 8:23
add a comment |
Which version of doxygen are we talking about?
– albert
Nov 12 '15 at 17:56
Try dir /x on the "Program Files (x86)" directory from the command line and use the short name instead. Probably the version of doxygen you used doesn't like (x86) junk in the name.
– doxygen
Nov 12 '15 at 18:39
A good setting might also beHHC_LOCATION = ""C:Program Files (x86)HTML Help Workshophhc.exe""
– albert
Sep 27 '18 at 8:23
Which version of doxygen are we talking about?
– albert
Nov 12 '15 at 17:56
Which version of doxygen are we talking about?
– albert
Nov 12 '15 at 17:56
Try dir /x on the "Program Files (x86)" directory from the command line and use the short name instead. Probably the version of doxygen you used doesn't like (x86) junk in the name.
– doxygen
Nov 12 '15 at 18:39
Try dir /x on the "Program Files (x86)" directory from the command line and use the short name instead. Probably the version of doxygen you used doesn't like (x86) junk in the name.
– doxygen
Nov 12 '15 at 18:39
A good setting might also be
HHC_LOCATION = ""C:Program Files (x86)HTML Help Workshophhc.exe""– albert
Sep 27 '18 at 8:23
A good setting might also be
HHC_LOCATION = ""C:Program Files (x86)HTML Help Workshophhc.exe""– albert
Sep 27 '18 at 8:23
add a comment |
5 Answers
5
active
oldest
votes
go to the html folder and run this command hhc index.hhp
make sure hhc is exported in the Environment variable or you can directly go to the location of hhc and run it from there.
It is in the C:Program Files (x86)HTML Help Workshop
answered Jul 7 '16 at 3:57
RaulpRaulp
3,17975299
add a comment |
Just found this thread (as I had the same issue), and another thing to check is whether you already have the destination .chm open in the help viewer - if so, close it as Windows can't write to an open file.
answered Mar 30 '18 at 6:06
MichaMicha
1112
add a comment |
This still is an issue with doxygen. I would think that the problem is that hhc returns 1 on a success, which is probably treated as an error result by doxygen. If the kind folks at doxygen could fix this, it would keep our logs cleaner :)
answered May 3 '18 at 8:33
user9734259user9734259
1
Please specify the version of doxygen you are using, the messages you get, the used settings (different ones compared to the default Doxyfile). Also of interest is the output when runningdoxygenwith the option-d extcmd.
– albert
May 3 '18 at 9:16
add a comment |
There is an other possibility for this error.
When a previous output *.chm file(old one) is in the output directory and is read-only and doxygen is trying to update the same file, this error will occur.
Check once the file is read-only or writable(It should be writable)
CHM_FILE = ../Design_Documentation.chm
OUTPUT_DIRECTORY = ....ComponentDetailed_Design
edited Sep 27 '18 at 8:25
albert
2,96931123
answered Sep 27 '18 at 4:40
Phani KumarPhani Kumar
1
The error will also occur when the file is "locked" i.e. still in use, e.g. when one is still reading it and tries to update it.
– albert
Sep 27 '18 at 8:26
add a comment |
The .chm file could also be write protected because it's still open in the help viewer. Just close it and rerun doxygen.
answered Nov 15 '18 at 10:20
WeeGeeWeeGee
1
In what differs this answer from the answer from Micha? or my comment with the answer of Phani Kumar?
– albert
Nov 15 '18 at 10:40
@albert the new contribution is the suggestion to close the file and rerun doxygen. So it's ok imo, but far from worth being upvoted, I think. :)
– colidyre
Nov 15 '18 at 10:45
@colidyre I think this is also implied in the 2 references I gave in my last comment.
– albert
Nov 15 '18 at 10:51
@albert - ... and now it's explicit. In Python-Language spoken: Explicit is better than implicit. Here you can see a good reason for that. Because it wasn't explicitely said, there is enough room for interpretation.
– colidyre
Nov 15 '18 at 10:57
@colidyre I stil don't see it as an answer, a comment would be better and Python with explicit? (especially the types...).
– albert
Nov 15 '18 at 11:42
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f33658612%2fdoxygen-error-failed-to-run-html-help-compiler-on-index-hhp%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
go to the html folder and run this command hhc index.hhp
make sure hhc is exported in the Environment variable or you can directly go to the location of hhc and run it from there.
It is in the C:Program Files (x86)HTML Help Workshop
answered Jul 7 '16 at 3:57
RaulpRaulp
3,17975299
add a comment |
go to the html folder and run this command hhc index.hhp
make sure hhc is exported in the Environment variable or you can directly go to the location of hhc and run it from there.
It is in the C:Program Files (x86)HTML Help Workshop
answered Jul 7 '16 at 3:57
RaulpRaulp
3,17975299
add a comment |
go to the html folder and run this command hhc index.hhp
make sure hhc is exported in the Environment variable or you can directly go to the location of hhc and run it from there.
It is in the C:Program Files (x86)HTML Help Workshop
answered Jul 7 '16 at 3:57
RaulpRaulp
3,17975299
go to the html folder and run this command hhc index.hhp
make sure hhc is exported in the Environment variable or you can directly go to the location of hhc and run it from there.
It is in the C:Program Files (x86)HTML Help Workshop
answered Jul 7 '16 at 3:57
RaulpRaulp
3,17975299
answered Jul 7 '16 at 3:57
RaulpRaulp
3,17975299
answered Jul 7 '16 at 3:57
RaulpRaulp
3,17975299
answered Jul 7 '16 at 3:57
RaulpRaulp
3,17975299
3,17975299
add a comment |
add a comment |
Just found this thread (as I had the same issue), and another thing to check is whether you already have the destination .chm open in the help viewer - if so, close it as Windows can't write to an open file.
answered Mar 30 '18 at 6:06
MichaMicha
1112
add a comment |
Just found this thread (as I had the same issue), and another thing to check is whether you already have the destination .chm open in the help viewer - if so, close it as Windows can't write to an open file.
answered Mar 30 '18 at 6:06
MichaMicha
1112
add a comment |
Just found this thread (as I had the same issue), and another thing to check is whether you already have the destination .chm open in the help viewer - if so, close it as Windows can't write to an open file.
answered Mar 30 '18 at 6:06
MichaMicha
1112
Just found this thread (as I had the same issue), and another thing to check is whether you already have the destination .chm open in the help viewer - if so, close it as Windows can't write to an open file.
answered Mar 30 '18 at 6:06
MichaMicha
1112
answered Mar 30 '18 at 6:06
MichaMicha
1112
answered Mar 30 '18 at 6:06
MichaMicha
1112
answered Mar 30 '18 at 6:06
MichaMicha
1112
1112
add a comment |
add a comment |
This still is an issue with doxygen. I would think that the problem is that hhc returns 1 on a success, which is probably treated as an error result by doxygen. If the kind folks at doxygen could fix this, it would keep our logs cleaner :)
answered May 3 '18 at 8:33
user9734259user9734259
1
Please specify the version of doxygen you are using, the messages you get, the used settings (different ones compared to the default Doxyfile). Also of interest is the output when runningdoxygenwith the option-d extcmd.
– albert
May 3 '18 at 9:16
add a comment |
This still is an issue with doxygen. I would think that the problem is that hhc returns 1 on a success, which is probably treated as an error result by doxygen. If the kind folks at doxygen could fix this, it would keep our logs cleaner :)
answered May 3 '18 at 8:33
user9734259user9734259
1
Please specify the version of doxygen you are using, the messages you get, the used settings (different ones compared to the default Doxyfile). Also of interest is the output when runningdoxygenwith the option-d extcmd.
– albert
May 3 '18 at 9:16
add a comment |
This still is an issue with doxygen. I would think that the problem is that hhc returns 1 on a success, which is probably treated as an error result by doxygen. If the kind folks at doxygen could fix this, it would keep our logs cleaner :)
answered May 3 '18 at 8:33
user9734259user9734259
1
This still is an issue with doxygen. I would think that the problem is that hhc returns 1 on a success, which is probably treated as an error result by doxygen. If the kind folks at doxygen could fix this, it would keep our logs cleaner :)
answered May 3 '18 at 8:33
user9734259user9734259
1
answered May 3 '18 at 8:33
user9734259user9734259
1
answered May 3 '18 at 8:33
user9734259user9734259
1
answered May 3 '18 at 8:33
user9734259user9734259
1
1
Please specify the version of doxygen you are using, the messages you get, the used settings (different ones compared to the default Doxyfile). Also of interest is the output when runningdoxygenwith the option-d extcmd.
– albert
May 3 '18 at 9:16
add a comment |
Please specify the version of doxygen you are using, the messages you get, the used settings (different ones compared to the default Doxyfile). Also of interest is the output when runningdoxygenwith the option-d extcmd.
– albert
May 3 '18 at 9:16
Please specify the version of doxygen you are using, the messages you get, the used settings (different ones compared to the default Doxyfile). Also of interest is the output when running
doxygen with the option -d extcmd.– albert
May 3 '18 at 9:16
Please specify the version of doxygen you are using, the messages you get, the used settings (different ones compared to the default Doxyfile). Also of interest is the output when running
doxygen with the option -d extcmd.– albert
May 3 '18 at 9:16
add a comment |
There is an other possibility for this error.
When a previous output *.chm file(old one) is in the output directory and is read-only and doxygen is trying to update the same file, this error will occur.
Check once the file is read-only or writable(It should be writable)
CHM_FILE = ../Design_Documentation.chm
OUTPUT_DIRECTORY = ....ComponentDetailed_Design
edited Sep 27 '18 at 8:25
albert
2,96931123
answered Sep 27 '18 at 4:40
Phani KumarPhani Kumar
1
The error will also occur when the file is "locked" i.e. still in use, e.g. when one is still reading it and tries to update it.
– albert
Sep 27 '18 at 8:26
add a comment |
There is an other possibility for this error.
When a previous output *.chm file(old one) is in the output directory and is read-only and doxygen is trying to update the same file, this error will occur.
Check once the file is read-only or writable(It should be writable)
CHM_FILE = ../Design_Documentation.chm
OUTPUT_DIRECTORY = ....ComponentDetailed_Design
edited Sep 27 '18 at 8:25
albert
2,96931123
answered Sep 27 '18 at 4:40
Phani KumarPhani Kumar
1
The error will also occur when the file is "locked" i.e. still in use, e.g. when one is still reading it and tries to update it.
– albert
Sep 27 '18 at 8:26
add a comment |
There is an other possibility for this error.
When a previous output *.chm file(old one) is in the output directory and is read-only and doxygen is trying to update the same file, this error will occur.
Check once the file is read-only or writable(It should be writable)
CHM_FILE = ../Design_Documentation.chm
OUTPUT_DIRECTORY = ....ComponentDetailed_Design
edited Sep 27 '18 at 8:25
albert
2,96931123
answered Sep 27 '18 at 4:40
Phani KumarPhani Kumar
1
There is an other possibility for this error.
When a previous output *.chm file(old one) is in the output directory and is read-only and doxygen is trying to update the same file, this error will occur.
Check once the file is read-only or writable(It should be writable)
CHM_FILE = ../Design_Documentation.chm
OUTPUT_DIRECTORY = ....ComponentDetailed_Design
edited Sep 27 '18 at 8:25
albert
2,96931123
answered Sep 27 '18 at 4:40
Phani KumarPhani Kumar
1
edited Sep 27 '18 at 8:25
albert
2,96931123
edited Sep 27 '18 at 8:25
albert
2,96931123
edited Sep 27 '18 at 8:25
albert
2,96931123
2,96931123
answered Sep 27 '18 at 4:40
Phani KumarPhani Kumar
1
answered Sep 27 '18 at 4:40
Phani KumarPhani Kumar
1
answered Sep 27 '18 at 4:40
Phani KumarPhani Kumar
1
1
The error will also occur when the file is "locked" i.e. still in use, e.g. when one is still reading it and tries to update it.
– albert
Sep 27 '18 at 8:26
add a comment |
The error will also occur when the file is "locked" i.e. still in use, e.g. when one is still reading it and tries to update it.
– albert
Sep 27 '18 at 8:26
The error will also occur when the file is "locked" i.e. still in use, e.g. when one is still reading it and tries to update it.
– albert
Sep 27 '18 at 8:26
The error will also occur when the file is "locked" i.e. still in use, e.g. when one is still reading it and tries to update it.
– albert
Sep 27 '18 at 8:26
add a comment |
The .chm file could also be write protected because it's still open in the help viewer. Just close it and rerun doxygen.
answered Nov 15 '18 at 10:20
WeeGeeWeeGee
1
In what differs this answer from the answer from Micha? or my comment with the answer of Phani Kumar?
– albert
Nov 15 '18 at 10:40
@albert the new contribution is the suggestion to close the file and rerun doxygen. So it's ok imo, but far from worth being upvoted, I think. :)
– colidyre
Nov 15 '18 at 10:45
@colidyre I think this is also implied in the 2 references I gave in my last comment.
– albert
Nov 15 '18 at 10:51
@albert - ... and now it's explicit. In Python-Language spoken: Explicit is better than implicit. Here you can see a good reason for that. Because it wasn't explicitely said, there is enough room for interpretation.
– colidyre
Nov 15 '18 at 10:57
@colidyre I stil don't see it as an answer, a comment would be better and Python with explicit? (especially the types...).
– albert
Nov 15 '18 at 11:42
add a comment |
The .chm file could also be write protected because it's still open in the help viewer. Just close it and rerun doxygen.
answered Nov 15 '18 at 10:20
WeeGeeWeeGee
1
In what differs this answer from the answer from Micha? or my comment with the answer of Phani Kumar?
– albert
Nov 15 '18 at 10:40
@albert the new contribution is the suggestion to close the file and rerun doxygen. So it's ok imo, but far from worth being upvoted, I think. :)
– colidyre
Nov 15 '18 at 10:45
@colidyre I think this is also implied in the 2 references I gave in my last comment.
– albert
Nov 15 '18 at 10:51
@albert - ... and now it's explicit. In Python-Language spoken: Explicit is better than implicit. Here you can see a good reason for that. Because it wasn't explicitely said, there is enough room for interpretation.
– colidyre
Nov 15 '18 at 10:57
@colidyre I stil don't see it as an answer, a comment would be better and Python with explicit? (especially the types...).
– albert
Nov 15 '18 at 11:42
add a comment |
The .chm file could also be write protected because it's still open in the help viewer. Just close it and rerun doxygen.
answered Nov 15 '18 at 10:20
WeeGeeWeeGee
1
The .chm file could also be write protected because it's still open in the help viewer. Just close it and rerun doxygen.
answered Nov 15 '18 at 10:20
WeeGeeWeeGee
1
answered Nov 15 '18 at 10:20
WeeGeeWeeGee
1
answered Nov 15 '18 at 10:20
WeeGeeWeeGee
1
answered Nov 15 '18 at 10:20
WeeGeeWeeGee
1
1
In what differs this answer from the answer from Micha? or my comment with the answer of Phani Kumar?
– albert
Nov 15 '18 at 10:40
@albert the new contribution is the suggestion to close the file and rerun doxygen. So it's ok imo, but far from worth being upvoted, I think. :)
– colidyre
Nov 15 '18 at 10:45
@colidyre I think this is also implied in the 2 references I gave in my last comment.
– albert
Nov 15 '18 at 10:51
@albert - ... and now it's explicit. In Python-Language spoken: Explicit is better than implicit. Here you can see a good reason for that. Because it wasn't explicitely said, there is enough room for interpretation.
– colidyre
Nov 15 '18 at 10:57
@colidyre I stil don't see it as an answer, a comment would be better and Python with explicit? (especially the types...).
– albert
Nov 15 '18 at 11:42
add a comment |
In what differs this answer from the answer from Micha? or my comment with the answer of Phani Kumar?
– albert
Nov 15 '18 at 10:40
@albert the new contribution is the suggestion to close the file and rerun doxygen. So it's ok imo, but far from worth being upvoted, I think. :)
– colidyre
Nov 15 '18 at 10:45
@colidyre I think this is also implied in the 2 references I gave in my last comment.
– albert
Nov 15 '18 at 10:51
@albert - ... and now it's explicit. In Python-Language spoken: Explicit is better than implicit. Here you can see a good reason for that. Because it wasn't explicitely said, there is enough room for interpretation.
– colidyre
Nov 15 '18 at 10:57
@colidyre I stil don't see it as an answer, a comment would be better and Python with explicit? (especially the types...).
– albert
Nov 15 '18 at 11:42
In what differs this answer from the answer from Micha? or my comment with the answer of Phani Kumar?
– albert
Nov 15 '18 at 10:40
In what differs this answer from the answer from Micha? or my comment with the answer of Phani Kumar?
– albert
Nov 15 '18 at 10:40
@albert the new contribution is the suggestion to close the file and rerun doxygen. So it's ok imo, but far from worth being upvoted, I think. :)
– colidyre
Nov 15 '18 at 10:45
@albert the new contribution is the suggestion to close the file and rerun doxygen. So it's ok imo, but far from worth being upvoted, I think. :)
– colidyre
Nov 15 '18 at 10:45
@colidyre I think this is also implied in the 2 references I gave in my last comment.
– albert
Nov 15 '18 at 10:51
@colidyre I think this is also implied in the 2 references I gave in my last comment.
– albert
Nov 15 '18 at 10:51
@albert - ... and now it's explicit. In Python-Language spoken: Explicit is better than implicit. Here you can see a good reason for that. Because it wasn't explicitely said, there is enough room for interpretation.
– colidyre
Nov 15 '18 at 10:57
@albert - ... and now it's explicit. In Python-Language spoken: Explicit is better than implicit. Here you can see a good reason for that. Because it wasn't explicitely said, there is enough room for interpretation.
– colidyre
Nov 15 '18 at 10:57
@colidyre I stil don't see it as an answer, a comment would be better and Python with explicit? (especially the types...).
– albert
Nov 15 '18 at 11:42
@colidyre I stil don't see it as an answer, a comment would be better and Python with explicit? (especially the types...).
– albert
Nov 15 '18 at 11:42
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f33658612%2fdoxygen-error-failed-to-run-html-help-compiler-on-index-hhp%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Which version of doxygen are we talking about?
– albert
Nov 12 '15 at 17:56
Try dir /x on the "Program Files (x86)" directory from the command line and use the short name instead. Probably the version of doxygen you used doesn't like (x86) junk in the name.
– doxygen
Nov 12 '15 at 18:39
A good setting might also be
HHC_LOCATION = ""C:Program Files (x86)HTML Help Workshophhc.exe""– albert
Sep 27 '18 at 8:23