![]() This then allowed MikTex/TexLive to pop-up the install window and install any missing software. Some users have been able to install the missing packages by clicking on the Debug checkbox in the IguanaTex window. Q: When pressing the Generate button in IguanaTex, compilation does not complete and the LaTeX window appears with no particular error message.Ī: This may be due to missing LaTeX packages. If all else fails, reinstall MikTex/TexLive and choose the "Complete" setting during installation this will install dvipng and the packages it requires, but will take some time.After doing this successfully, you should be able to use IguanaTex with no problems. You should now see dvipng installing whatever missing packages were required during the creation of the IguanaTex image. The directory should contain the file addin_tmp.dvi. If this does not work, switch to the temporary directory you chose when installing IguanaTex (usually c:\temp).Some users have been able to install the missing packages by clicking on the Debug checkbox in the IguanaTex window.There are three ways to solve this problem: If dvipng or some of its component packages are missing, you will see a tex file containing your LaTeX code, and a dvi file, but no png file. To verify that this is the problem, generate the above error message and then check the contents of the temporary directory which you specified when installing IguanaTex. dvipng is usually installed with MikTex/TexLive, but some 'minimal' or 'custom' MikTex/TexLive installation options do not include it. I can see that the TexStudio ppa "recommends" textlive, which if I understand correctly, will be the repo version.A: This problem is usually caused when the program dvipng, or other MikTex/TexLive components, are not installed correctly. unless TexStudio itself is the culprit? Does TexStudio have a dependency on the repo version of texlive? I updated from the ppa. Curious that the problem manifested itself at the same time as I updated TextStudio. But this has clearly sneaked past me at some point. I have absolutely definitely not installed the repo version of texlive myself because I know having two simultaneous versions causes problems. This has happened before where a package has added a dependence on latex which usually results in an update of the package trying to install the repo version of texlive. I'll continue to work on this because it is a nuisance.Īre there any paths (which might apply) to bst files set anywhere in TexStudio's many options?Īh! Great spot! In fact, thinking back I have a similar problem before.Īfter investigation, it seems that the 2019 version of texlive, which comes in the Ubuntu repo, has become installed. (I posted the log file from this build previously.) I can still build the pdf from the shell, which implies that my texlive is still working properly.I was halfway through writing the paper when I upgraded to v4.3.1.(In my experience, things can sometimes reconfigure themselves spontaneously on Linux.) In particular: I suppose it is possible that my tex installation threw some strange aberration at just the same time as I upgraded to v4.3.1 of TexStudio - stranger things happen at sea! But all the evidence seems to point at something has gone wrong with my TexStudio configuration. I am not so sure about the "it's a tex issue" explanation. When I copy the bst file into the same directory, it works, which suggests the issue lies solely with finding the bst file. Is bibtex failing to find the bib file (which is in the same directory) or is it failing to find the bst file? I am not clear from the log files. the important point is why bibtex does not find the bib and there I can only speculate. but this is not very elegant since it already exists in the default texlive tree (which, of course, is why I can build from the shell!). ![]() ![]() Maybe somebody with a deeper understanding of Latex can spot what is going wrong from the log files?Īs I have pointed out, simply copying the IEEEtran.bst file into the directory allows TexStudio to work properly. Running these two log files through diff shows differences starting around 359 indicating some issues with the two references. The second log file "shell-New." is what results from successfully building the pdf from the shell by invoking pdltatex, bibtex, and pdflatex twice more. ![]() I also include two log files: the one named "New." is what is generated by building within TexStudio this build fails by not resolving the references. I have also had to hack the extension for the minimal bib file for the same reason. Note that I have had to rename the tex file as 'txt' because github does seem to allow the upload of tex files. Herewith an MWE based on an edited down version of the IEEE Transactions template example.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |