I am trying to migrate from TeXworks to Texmaker (just for the fact that it is better for handling multi-files projects). I am using portable versions of both MiKTeX and Texmaker, so, in Texmaker I went to Options > Configure Texmaker > Commands and point every command available to the current path of MiKTeX. And it works just fine with PDFLaTeX, but at the moment I try to compile some XeLaTeX document it just do not generate any PDF output.
For a brief moment, in the log frame says that it can not recognize xdvipdfmx as a program or a command. So I figure that it is trying to find it in the default installed MiKTeX directory (because xdvipdfmx.exe indeed exist in the same folder than xelatex.exe and TeXworks never has a problem finding it). There is an option to set the path to dvipdfm (which —I am guessing— works with PDFLaTeX), but not for xdvipdfmx.
So, a concise question would be, Is there a way to change (or add) the default directory for Texmaker to look for? Or is the problem another?
[Addendum] [edited] So, I decided to put a xdvipdfmx.bat file into the Windows folder (which only contains one line: E:\LaTeX\MiKTeX\miktex\bin\xdvipdfmx.exe), and now it appears that compiles as it should, BUT it does not produce any PDF file, even tho the log file ends saying “Output written on satre-merleau-ponty-levinas.pdf (175 pages)” or, if I add an \includeonly sentence, “Output written on satre-merleau-ponty-levinas.pdf (9 pages)”. Every auxiliar file is also created, just not the PDF. Any thoughts?
A minimal example (not PDF output generated) is
\documentclass[11pt,twoside,book]{memoir}
\usepackage{lipsum}
\usepackage{fontspec}
\begin{document}
\lipsum
\end{document}
Under this conditions: MiKTeX portable 2.9, Texmaker portable 3.5.2 (or TeXstudio portable 2.5)
It indeed generates a PDF output if I compile it from TeXworks OR if I comment out the \usepackage{fontspec} line and compile it with pdfLaTeX.
[miktex] +portable +texmaker. – Speravir Nov 10 '12 at 00:09xdvipdfmx.exebecause it can’t find it; I just want to know how to point Texmaker to it… or whether that’s possible or not. – marlonob Nov 10 '12 at 22:12pdflatexwouldn’t have worked, too, I would have thought, it was a system path issue, and suggested to read the answers in texmaker 3.5 miktex portable 2.9 and epstopdf, but so unfortunately I cannot help. – Speravir Nov 10 '12 at 22:32batfile. Also try out the direct command line call of thexdvipdfmx.exe. And I think, it is time for you to provide a minimal (not) working example (MWE) that illustrates your problem. It is considered a lot better to put in some code that will (not) compile, as it makes it a lot easier for us to copy it into our text editor and work with it, and see exactly what it is you are trying to do. – Speravir Nov 11 '12 at 00:46