I need some hel regarding doxygen. I have a c++ code and i want to generate the pdf documentation using doxygen. The problem is that doxygen runs, produces the html output as expected, but the refman.tex file isnt generated (it generates the "d" folders and the doxygen.sty file). I have activated the "GENERATE_LATEX" option on the configuration file and there is no visible error on the console...
Im running doxygen 1.8.1.2 on ubuntu 12.10 x64 and i have texlive 2012/Debian (latest available).
Any help will be very much appreciated.
Related
I installed google drive to Linux Mint 20 via gnome-control-accounts following instructions from here: https://www.fosslinux.com/1954/how-to-install-google-drive-on-linux-mint-18-1-18-2.htm
I have some Latex files in google drive. When I open them via gnome-control-accounts, the paths look very odd: instead of my original "myfile.tex" it is some abracadabra like this:
"/run/user/1000/gvfs/google-drive:host=gmail.com,user=myname/12ZSQjF4pmvwGE0bZzXwgxSrRS-lPD2ML".
When I open the file with TexMaker, it gives an error
Could not start the command.
pdfLatex-synctex=1 -interaction=nonstopmode %.tex
I believe this happens because of the odd path name under which my tex files are saved.
How to solve this?
Merci beaucoup.
P.S. I also installed google-drive via ocamlfuse following instructions from here:
https://www.techrepublic.com/article/how-to-mount-your-google-drive-on-linux-with-google-drive-ocamlfuse/ .
It does run the latex files, but it works only in online mode, and you have to mount the disk manually each time you start your computer.
In OpenCV source dir, there is a doc dir. But, this dir contains no pdf files. How can I get files like "opencv_tutorials.pdf", "opencv_cheatsheet.pdf"?
Thanks!
You need doxygen for this. You can install it from http://www.doxygen.nl and then run the doxygen executable on the doxyfile.in. This should generate documentation files in html, pdf (if you have latex installed), etc.
Note that you'll probably find all the tutorials and PDFs you'll need online as well. Using these generated files have the risk of being outdated very soon.
When doing Ctrl+B on SublimeText3, the following error is output:
[Compiling first.tex]
TraditionalBuilder: Invoking latexmk...
COULD NOT COMPILE!
Attempted command:latexmk -cd -e $pdflatex='pdflatex -interaction=nonstopmode -synctex=1 %S %O' -f -pdf first.tex
Build engine: Traditional Builder
Running the exact same command compiles a pdf file just fine.
This answer does not solve the problem, as I've
Removed spaces around "="
Done a "Reconfigure LaTeXTools and migrate settings".
Made sure pdflatex is installed.
Made sure the path for texpath is correct.
If your command runs on terminal then most likely there is an issue either with the path or with the command itself (in the file). There has been some update to the README file by the developer:
some distros do not want a space before and after the = in $pdflatex = %E. But some do want the space there (sigh!)
sometimes latexmk is not on the PATH, or the path is not correctly picked up by ST. In this case, instead of "latexmk", use "/usr/bin/latexmk" or wherever latexmk is in your system.
some distros require quoting the $pdflatex assignment, as in "$pdflatex = \"'%E -interaction=nonstopmode -synctex=1 %S %O'\""
So it might take a while but you'll find it eventually in the settings or the traditionalbuilder.py file.
Also when I tried putting /usr/bin/latexmk, latex did not produce the correct pdf (I checked it with few changes and it just opened the old pdf) but in your case it might work.
Also, at least in Arch Linux I can't run sublime with sublime-text but instead with subl so I changed that too in the settings (I don't know if it actually matters) and I needed to change the permissions for the files because user-run sublime could not access my settings files!
As the title says, how to use luadoc in ubuntu/linux? I generated documentation in windows using batch file but no success in ubuntu. Any ideas?
luadoc
Usage: /usr/bin/luadoc [options|files]
Generate documentation from files. Available options are:
-d path output directory path
-t path template directory path
-h, --help print this help and exit
--noindexpage do not generate global index page
--nofiles do not generate documentation for files
--nomodules do not generate documentation for modules
--doclet doclet_module doclet module to generate output
--taglet taglet_module taglet module to parse input code
-q, --quiet suppress all normal output
-v, --version print version information
First off, I have little experience with Luadoc, but a lot of experience with Ubuntu and Lua, so I'm basing all my points off of that knowledge and a quick install that I've just done of luadoc. Luadoc, as far as I can see, is a Lua library (so can also be used in Lua scripts as well as bash). To make documentation (in bash), you just run
luadoc file.lua
(where file is the name of your file that you want to create documentation for)
The options -d and -t are there to choose where you want to put the file and what template you want to use (which I have no clue about, I'm afraid :P). For example (for -d):
luadoc file.lua -d ~/Docs
As far as I can see, there is little else to explain about the actual options (as your code snippet explains what they do well enough).
Now, looking at the errors you obtained when running (lua5.1: ... could not open "index.html" for writing), I'd suggest a few things. One, if you compiled the source code, then you may have made a mistake somewhere, such as not installing dependencies (which I'd be surprised about, because otherwise you wouldn't have been able to make it at all). If you did, you could try getting it from the repos with
sudo apt-get install luadoc
which will install the dependencies too. This is probably the problem, as my working copy of luadoc runs fine from /usr/bin with the command
./luadoc
which means that your luadoc is odd, or you're doing something funny (which I cannot work out from what you've said). I presume that you have lua5.1 installed (considering the errors), so it's not to do with that.
My advice to you is to try running
luadoc file.lua
in the directory of file.lua with any old lua file (although preferably one with at least a little data in) and see if it generates an index.html in the same folder (don't change the directory with -d, for testing purposes). If that DOESN'T work, then reinstall it from the repos with apt-get. If doing that and trying luadoc file.lua doesn't work, then reply with the errors, as something bigger is going wrong (probably).
I'm going through the railstutorial.org Chapter 3 tutorial and the instructor asked us to create a new html file with the command:
$ mate public/hello.html
However, I'm not using Textmate in this case, but rather Smultron as my text editor. That said, I receive the error message:
-bash: mate: command not found
Do you know what word I should replace "mate" with to properly communicate with Smultron?
When Textmate is installed, it puts a mate executable in /usr/local/bin/. If you're not using Textmate, you won't have that command.
Older versions of Smultron placed a smultron executable in the path. I don't imagine that's changed, but I don't have the lastest version of Smultron to confirm that. I also don't remember if you have to provide any kind of command line switches when creating a new file.
Edit: To get command-line support in Smultron 4, download this: http://www.peterborgapps.com/wp-content/uploads/2011/07/smultron-commandlineutility4.zip