Doxygen error: failed to run html help compiler on index.hhp - doxygen

So I am having this problem where I get an error when trying to get a .chm file for doxygen.
sh: C:\Program Files\HTML Help Workshop\hhc.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 Workshop\hhc.exe"
It's seriously driving me nuts and I don't find anything anywhere. Please help.

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 :)

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

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.

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 = ..\..\Component\Detailed_Design

The .chm file could also be write protected because it's still open in the help viewer. Just close it and rerun doxygen.

As already mentioned by me in the comment (Doxygen error: failed to run html help compiler on index.hhp), the setting of the HHC_LOCATION should be like:
HHC_LOCATION = "\"C:\Program Files (x86)\HTML Help Workshop\hhc.exe\""
so the hhc compiler is called like: "C:\Program Files (x86)\HTML Help Workshop\hhc.exe".

Related

VSCode Cannot Execute Julia FIles

I've scoured other forums that talk about this problem and have tried all of the recommendations I've found, but I cannot seem to get VSCode to recognize my Julia.exe path and execute commands in a .jl file. Every time I run even a simple .jl file, I get /bin/sh: julia: command not found (pictured below).
I have ensured that the executable path is set properly in the .json file, and have tried moving the executable to other locations (using an M1 Mac), but it seems it still cannot find/recognize the Julia.exe:
I have even tried just pointing to the binary folder /bin, and /bin/julia.exe (with the extension), and though VSCode does not generate the error when it cannot confirm the .exe path, the actual code still generates the error above.
I'm at my wits end here. I'm sure it's a simple answer that someone could spot in a second, or know the troubleshooting for, but I've never had this issue to this degree before with installing other languages like Kotlin. Any help is greatly appreciated.
Problem was fixed by the MacOS recommendation found here:
julialang.org/downloads/platform/#optional_add_julia_to_path
Copying the binary .exe elsewhere (outside of /Applications) and changing the executable path in VSCode fixed the issue.

Doxygen failed to run html help compiler, hhc.exe error HHC5010 when running from folder that has a parent folder that starts with "."

I am using Conan package manager on Windows to create a package. The conan command to create the package copies files to a folder within %USERPROFILE%\.conan (or C:\Users\xxxxxxx\.conan). Then from this location it builds a Visual Studio project and ultimately calls doxygen.exe to create a .chm help file in a post-build command. The doxygen command fails with:
error : failed to run html help compiler on index.hhp
Further investigation reveals the hhc.exe command executed by doxygen is failing with:
C:\Users\xxxxxxx\.conan\data\Module\1.0.0\user\channel\build\524dc97e4a3dd1f774ea3897f9e4faf26c5457d2\Documentation>"C:/Program Files (x86)/HTML Help Workshop/hhc.exe" html\index.hhp
HHC5010: Error: Cannot open "C:\Users\xxxxxxx\data\Module\1.0.0\user\channel\build\524dc97e4a3dd1f774ea3897f9e4faf26c5457d2\Documentation\html\Module.chm". Compilation stopped.
Close inspection reveals that in the error message, the ".conan" folder is missing. Sure enough, I confirmed that hhc.exe fails when the index.hpp resides in a folder that has a parent folder that starts with a ".".
Attempts to resolve this:
changing the Doxyfile setting OUTPUT_DIRECTORY to "$(TMP)/DoxygenModule" resolves the error, but creates the .chm file in another location, which I do not prefer.
navigating to the 8DOT3 name of the ".conan" folder, which is "CONAN~1", to run the hhc.exe command, succeeds, but unfortunately I have no way of getting conan to use this 8DOT3 path for creating the package. E.g. C:\Users\xxxxxxx\CONAN~1\...
I can live with the using the %TMP% folder but would prefer generating the .chm in the current folder. Anyone have any ideas?
HTML Help Workshop v1.31 is installed on my machine at C:\Program Files (x86)\HTML Help Workshop, probably from a Visual Studio installation (not sure). I attempted using a version downloaded from Microsoft website (v1.30) as well, which made no difference.
Other info: Conan version 1.18.0, Doxygen version 1.8.14, Windows 10 Version 1809
Unfortunately not a solution, but this is a known limitation in the hhc.exe, see: https://social.msdn.microsoft.com/Forums/en-US/0681145c-223b-498c-b7bf-be83209cbf4e/issue-with-html-workshop-in-a-windows-container?forum=visualstudiogeneral
HTML Help 1.x command line compiler hhc.exe cannot compile CHM file to folder whose full path contains folder name starting with dot. If you have that problem, you probably specified output path with folder starting with dot, e.g. "d:\My files.NET\documentation". You can use dots in folder names but not at the beginning.
Edit 2019-11-15:
I've just pushed a proposed patch to github (pull request 7402, https://github.com/doxygen/doxygen/pull/7402).
This proposed patch changes inside doxygen from the current directory to the short named current directory, but just for the HTML Help compilation.
Edit 2019-11-16:
Code has been integrated in the master version on github.
This is not an answer either. Actually, you found the answer and workaround[s] yourself.
Use OUTPUT_DIRECTORY to specify a directory containing no folder names beginning with periods.
The error you described is a known issue of the MS HTML Help compiler. More general, the HTML Help compiler does not like some folder and file names. Try and stick with these characters _, a..z, A..Z, 0..9. Do not use these signs in particular ., -, # .
Please note that the proprietary CHM file format is about 20 years old (Windows 95, ...). HTML Help is in maintenance mode, which means no new features and bug fixes are expected for either the runtime or the compiler. All mainstream development on HH has stopped.
There is no way to avoid this error if a directory name above begins with a period. Not even if only the necessary files are written by Doxygen and compiling of the index.hhp is done by a third-party tool like FAR HTML using your path that contains .conan. This is because all applications are using the faulty HHA.dll.
The above applies of course to the entire workflow you have described. Maybe you can interrupt it.
Doxygen can be configured not to call the HTMLHelp compiler. Just uncheck the GENERATE_HTMLHELP option (DoxyWizard: Experts > Topics > HTML). You have all files generated by Doxygen in your preferred output directory - but of course without the CHM file. This can be imported later e.g. by HelpNDoc and compiled as a CHM file in another location.
If you can interrupt the workflow and can also make changes to Doxygen's settings, then a preference setting of OUTPUT_DIRECTORY to e.g. C:/CacheMenu/CONAN~1/DOXYGE~1 also works as expected (here used as test case).
No matter what you do, your workaround and copy and paste from another directory outside is a quick solution at this stage. Please note the EDIT in #albert's answer.

Does universal-ctags support exuberant-ctags config files?

I've got a $HOME/.ctags file from exuberant-tags, but universal-tags doesn't seem to be picking up my options from it. Does universal-tags support these config files?
See this documentation for details. The quick answer is:
mkdir $HOME/.ctags.d
mv $HOME/.ctags $HOME/.ctags.d/default.ctags
As an added bonus, you can now add comments to the file.
Apparently the file must have a name. at least in windows. so
.ctags will never work. As soon as I renamed my file to defaults.ctags the executable started reading it, if you enter bad syntax in the ctags file you will see errors output on the command line.

LibreOffice Headless

I am trying to convert .docx file to .pdf using the pdfgear as described in https://github.com/phpgearbox/pdf. This component defaults to libre-office-headless. I installed LibreOffice5 in my computer at
C:\Program Files (x86)\LibreOffice 5
with its binary lying at
C:\Program Files (x86)\LibreOffice 5\program.
Then in my Controller method i have:
$pdf = Gears\Pdf::convert($temp_filename);
shell_exec('libreoffice --headless --convert-to pdf $temp_filename');
The first statement is resulting to the error:
An uncaught Exception was encountered
Type: RuntimeException
Message: The libreoffice command ("/usr/bin/libreoffice") was not
found or is not executable by the current user!
While the next line is resulting to nothing (no error and no pdf document)!
How can i install libre-office-headless to ensure that the first line of code runs successfully? I hope you understand my question. Thank you.
Looking through the pdfgear source code there are a number of locations hard coded that you might need to adapt. They seem to be written with a normal Linux distro installation of LibreOffice in mind.
One case that seems related to your problem is https://github.com/phpgearbox/pdf/blob/master/src/Pdf/Docx/Converter/LibreOffice.php#L73

php_warning on installing ext

I want to intstall the ext "my_redirects". On my local machine it does what it should. But now, on the live site, i got this error:
1: PHP Warning: file_get_contents(/kunden/homepages/28/d574274134/htdocs/update7/typo3/sysext/core/Resources/Private/Sql/Cache/Backend/Typo3DatabaseBackendCache.sql): failed to open stream: No such file or directory in /homepages/28/d574274134/htdocs/update7/typo3_src-7.6.14/typo3/sysext/core/Classes/Cache/Backend/Typo3DatabaseBackend.php line 441
I got a hint to delete the typo3temp/autoload/ files. Then the installation works, but if i after that go into the install tool, i get this error again. Can someone give a hint?
This file is part of the core and must exist. Look into the src-tar/zip file. Maybe the file wasn't transferred to the server.
I don't think it's an autoload issue, because the .sql file is missing, not the PHP class.
Please verify that the sql file does exist. If it's missing, check the hash of your downloaded TYPO3 core. Make sure you compare the correct path on the server.
But I guess you got an access restriction. Maybe bad ownhership of that .sql file? Perhaps you ran into some security problems with file_get_contents() and at least sql files? So please also check your security settings.