I would try to find out what that reason is. Kile is IMHO a superior editor to TXC, and if the choice is between troubleshooting one problem, or troubleshooting another, it just seems to make more sense to stick with the linux-native software. Can you compile the document from the commandline? (E.g., with "pdflatex filename.tex" from a terminal?)I understand that migrating to tex-live and kile is the logical thing to do but I cannot compile my pdf with kile either for some reason, even though it works with miktex/texniccenter on windows.
MiKTeX and proTeXt ⇒ MikTeX on Linux
MikTeX on Linux
NEW: TikZ book now 40% off at Amazon.com for a short time.
And: Currently, Packt sells ebooks for $4.99 each if you buy 5 of their over 1000 ebooks. If you choose only a single one, $9.99. How about combining 3 LaTeX books with Python, gnuplot, mathplotlib, Matlab, ChatGPT or other AI books? Epub and PDF. Bundle (3 books, add more for higher discount): https://packt.link/MDH5p
Re: MikTeX on Linux
\graphicspath{{Figures//}}
MikTeX on Linux
No. Did you only install the minimal TeXlive packages which are dependency for Kile? If so, then you'll probably need to install some more to get the packages you need.Does kile/tex-live auto install packages?
If you're not hurting for disk space, then consider going ahead and installing a full TeXlive installation. Then you'll have a local repository containing all the TeXlive packages (or at least all those which existed when the Debian/Ubuntu packages were created in 2009):
Code: Select all
sudo apt-get install texlive-full
If you're hurting for diskspace, then you might just want to install the package bundles you need. siunitx is included in the texlive-science package:
Code: Select all
sudo apt-get install texlive-science
If you'd rather go with an even more up to date TeXlive system (TeXlive 2010), with finer-grained control, it's possible to bypass Ubuntu's packages and install directly from CTAN/TUG. The trick then is satisfing the dependencies for installing Kile the usual way. There are some tips on that here, but the above might be easier if you don't mind your packages being a bit older.
As for the graphicspath problem, I don't really understand why you have it the way you do, but maybe try changing \graphicspath{{Figures//}} to simply \graphicspath{Figures/}.
Re: MikTeX on Linux
With miktex/windows using graphicspath, with the double forwardslash.
\graphicspath{{Figures//}}
would search recursively the subdirectories of Figures for the figures used in \includegraphics. This does not seem to work with texlive/linux. Is there a way of changing this line to make my tex file compile in both miktex/windows and texlive/linux without specifying each subdirectory individually?
\graphicspath{Figures/}
does not work because it does not look in the subdirectories of Figures to find them.
MikTeX on Linux
Code: Select all
\graphicspath{{Figures/}{Figures/sub/}{Figures/sub2/}}
In any case, it doesn't seem as if MikTeX would do any better here.
Re: MikTeX on Linux
Thanks again for your help frabjous.
P.S. are you the same frabjous from {TeX} SE?
MikTeX on Linux
Code: Select all
\graphicspath{{Figures//}{~/Figures/}}
If it does, would using the ifplatform package help to set the \graphicspath conditionally?
Code: Select all
\usepackage{ifplatform}\iflinux \graphicspath{{~/Figures/}} \fi\ifwindows \graphicspath{{Figures//}} \fi
Finally, one radical solution you might consider would be to symlink your Figures directory into one your texmf directories. E.g., on Ubuntu I think this would work (from a terminal):
Code: Select all
mkdir -p ~/texmf/tex/generic/ln -s ~/Figures ~/texmf/tex/generic/Figuressudo texhash
Yep, that's me.P.S. are you the same frabjous from {TEX} SE?
