Kile

Kile is a mature LaTeX IDE developed by the KDE project. It is Qt-based and aimed primarily at Linux, though it runs on other operating systems too. Like other editors it drives a TeX distribution you install separately, but Kile’s character lies in its projects, a structure view that lets you survey a document, an array of wizards, and deep integration with the KDE desktop. This page focuses on two things: how its build mechanism works — the part people get stuck on — and the KDE integration that roots it in the Linux/KDE world.

What Kile is

Kile is a dedicated LaTeX editor written in C++, built on KDE Frameworks and Qt. It offers syntax highlighting, command auto-completion, quick insertion of symbols and tags, one-shot insertion of environments such as \begin…\end, and QuickPreview for trial-printing just a selection. The name is Norwegian for “wedge” or “tickle,” and its authors insist it is pronounced not “Kyle” but closer to /kiːlə/.

Like most editors, Kile does not bundle LaTeX itself: compilation works by having Kile launch commands already installed on your system — pdflatex, uplatex, latexmk, and so on. So the order of installation matters: install a TeX distribution first (on Linux, TeX Live is the usual choice), then Kile. Once a working setup is in place (e.g. TeX Live 2026), all that remains on the Kile side is to wire up how it builds your document.

A distinctive unit is the project. Group a multi-file document — several .tex files — into a single project, and Kile remembers which file is the master document (the parent that holds \documentclass). Press F5 while a child file is open and the build still starts from the master, so theses and books split into per-chapter files never lose their footing. Within a project, completion of \ref and \cite also works across all the files at once.

Build

Kile’s build is organized around the idea of Tools. Each piece — pdflatex, dvipdfmx, the PDF viewer — is a “tool,” and the menus sort them by purpose into Build → Compile, Build → Convert, and Build → View. What each tool actually is (the command it calls and its arguments) is specified entirely under Settings ▸ Configure Kile ▸ Tools ▸ Build.

For instance, the PDFLaTeX tool is configured with the command pdflatex and options like the following. %source is Kile’s placeholder, expanding to the file being processed; including -synctex=1 is what enables the forward/inverse search (SyncTeX) described below.

-interaction=nonstopmode -synctex=1 %source

On top of that, Kile’s centerpiece is QuickBuild. It is not a single tool but a chain of tools called in sequence, bound to one button. Assign the chain “LaTeX → DVItoPDF → ViewPDF” to QuickBuild, say, and a single press runs the whole sequence: compile, convert the DVI to PDF, then open it in the viewer. The contents of the chain are freely rearranged in the same configuration screen, so you can build a one-press workflow tailored to your document.

Kile also detects automatically whether additional tools are needed — bibliography (BibTeX), index (makeindex), Asymptote — and runs them when so (this behavior is toggled on the General tab of the LaTeX/PDFLaTeX tools in the configuration screen). Even so, to have rerun counts and dependencies handled more thoroughly, a common move is to add latexmk as a tool: create a new tool with the command latexmk and the options below.

-pdf -synctex=1 -interaction=nonstopmode %source

Configuring a tool for Japanese

The long-standing standard for Japanese is the upLaTeX + dvipdfmx combination. In Kile you prepare two tools. First, in the LaTeX-family tool, set the command to uplatex with the options below.

-synctex=1 -interaction=nonstopmode %source

Next, set the DVItoPDF tool — which turns the DVI into a PDF — to the command dvipdfmx with options %S.dvi (%S is the base name without extension). Finally, chain these into QuickBuild as “LaTeX → DVItoPDF → ViewPDF,” and Japanese documents build with a single press of F5. For completeness, point the bibliography and index tools at the Japanese-aware upbibtex and upmendex.

The cleanest arrangement is to describe the engine combination in a **.latexmkrc** and reduce the Kile side to a single tool that calls latexmk. Place the following file in the same folder as your .tex, and latexmk takes care of the upLaTeX → dvipdfmx flow, the bibliography, the index, and the rerun count. The advantage: the same result whether invoked from Kile, the command line, or another editor, with the configuration gathered in one place.

$latex = 'uplatex %O -synctex=1 -interaction=nonstopmode %S';
$bibtex = 'upbibtex %O %B';
$makeindex = 'upmendex %O -o %D %S';
$dvipdf = 'dvipdfmx %O -o %D %S';
$pdf_mode = 3;

Here $pdf_mode = 3 selects the mode “make a DVI, then turn it into a PDF with $dvipdf.” The tokens %O (extra options), %S (the source file), %B (the base name without extension), and %D (the output target) are latexmk’s placeholders — note that these belong to latexmk and are distinct from the %source and %S you use in Kile’s tool settings.

KDE integration and Okular

Kile is deeply rooted in the conventions of the KDE desktop. Its foundation is KDE Frameworks: where settings are stored and how it looks (theme, icons) ride directly on KDE’s machinery. The keystone is a technology called KParts — KDE’s mechanism for embedding one application’s component (a viewer or an editing feature) whole inside another. Kile uses it to bring an external PDF viewer right into its own window.

The component it embeds is KDE’s standard document viewer, Okular. Because Okular supports SyncTeX, it can map source lines to positions in the PDF and back. That gives you forward search — jumping from the line you are on in the editor to the matching place in the PDF — and inverse search, jumping from a spot in the PDF back to the source line. To enable forward search, set the View tool (Okular) to the command okular with options like --unique %absolute_target (%absolute_target expands to the absolute path of the output PDF).

Inverse search is configured on the Okular side: set Okular’s “editor” to Kile with the launch command kile --line %l, and Shift-clicking in the PDF jumps back to the corresponding line in Kile. Build a QuickBuild chain such as “LaTeX → DVItoPDF → ForwardPDF,” and Okular opens the page at your cursor on every compile. This two-way interplay feels seamless precisely because KParts has them sharing one window.

Kile targets Linux/KDE first, but because Qt and the KDE libraries are ported elsewhere, it also runs on macOS, BSD, and Windows (the Windows build is even distributed via the Microsoft Store). Still, it feels most at home on a Linux desktop, where the Okular pairing and the unity with KDE’s settings pay off most fully.