glfs/xsoft/graphweb/falkon.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
   "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
  <!ENTITY % general-entities SYSTEM "../../general.ent">
  %general-entities;

  <!ENTITY falkon-download-http "&kf6apps-download-http;/falkon-&kf6apps-version;.tar.xz">
  <!ENTITY falkon-download-ftp  " ">
  <!ENTITY falkon-md5sum        "fffda993fe5cb540410d3a1d0e70015e">
  <!ENTITY falkon-size          "2.5 MB">
  <!ENTITY falkon-buildsize     "148 MB">
  <!ENTITY falkon-time          "1.8 SBU (Using parallelism=4; add 0.3 SBU for tests)">
]>

<sect1 id="falkon" xreflabel="falkon-&kf6apps-version;">
  <?dbhtml filename="falkon.html"?>


  <title>Falkon-&kf6apps-version;</title>

  <indexterm zone="falkon">
    <primary sortas="a-falkon">falkon</primary>
  </indexterm>

  <sect2 role="package">
    <title>Introduction to falkon</title>

    <para>
      <application>Falkon</application> is a KDE web browser using the QtWebEngine
      rendering engine. It was previously known as <application>QupZilla</application>.
      It aims to be a lightweight web browser available through all major platforms.
    </para>

    <para>
      Although <application>falkon</application> is now part of KDE, it can be
      installed without KDE (with the loss of <application>kwallet</application>
      functionality).
    </para>

    <warning>
      <para>
        Falkon relies on QtWebEngine. That uses a forked copy of chromium, and
        is therefore vulnerable to many issues found there. The Qt developers
        have always preferred to make releases at the same time as the rest of Qt
        (rather than adding emergency fixes). Now that they are keen to move to
        Qt6, the 5.15.3 and later Qt-5.15 releases are initially only available
        to paying customers. QtWebEngine is something of an exception because of
        its LGPL licence, but getting the git sources (with the forked chromium
        submodule) to a point where they will successfully build on a current
        BLFS system can take a lot of effort. Be aware that future fixes for
        vulnerabilities might be very delayed, to the extent that you might wish
        to consider using a different browser.
      </para>
    </warning>

    &lfs121_checked;

    <bridgehead renderas="sect3">Package Information</bridgehead>
    <itemizedlist spacing="compact">
      <listitem>
        <para>
          Download (HTTP): <ulink url="&falkon-download-http;"/>
        </para>
      </listitem>
      <listitem>
        <para>
          Download (FTP): <ulink url="&falkon-download-ftp;"/>
        </para>
      </listitem>
      <listitem>
        <para>
          Download MD5 sum: &falkon-md5sum;
        </para>
      </listitem>
      <listitem>
        <para>
          Download size: &falkon-size;
        </para>
      </listitem>
      <listitem>
        <para>
          Estimated disk space required: &falkon-buildsize;
        </para>
      </listitem>
      <listitem>
        <para>
          Estimated build time: &falkon-time;
        </para>
      </listitem>
    </itemizedlist>

    <bridgehead renderas="sect3">falkon Dependencies</bridgehead>

    <bridgehead renderas="sect4">Required</bridgehead>
    <para role="required">
      <xref linkend="extra-cmake-modules"/>,
      <xref linkend="kf6-frameworks"/> (for karchive), and
      <xref linkend="qtwebengine"/>
    </para>

    <note>
      <para>
        Strictly speaking, only karchive is required to build falkon, but
        several other packages in <xref linkend="kf6-frameworks"/> can be used
        if they are present. To build only karchive, download that package from
        the directory specified in <xref linkend="kf6-frameworks"/> and use the
        build instructions on that page changing the $KF6_PREFIX to /usr.
      </para>
    </note>

    <bridgehead renderas="sect4">Optional</bridgehead>
    <para role="optional">
      <xref linkend="gnome-keyring"/>,
      <ulink url="https://pypi.org/project/PySide2/">PySide2</ulink>, and
      <ulink url="https://pypi.org/project/shiboken2/">Shiboken2</ulink>
    </para>

    <para condition="html" role="usernotes">
      Editor Notes: <ulink url="&blfs-wiki;/falkon"/>
    </para>
  </sect2>

  <sect2 role="installation">
    <title>Installation of falkon</title>

    <para>
      Install <application>falkon</application> by running the following
      commands:
    </para>

<screen><userinput>mkdir build &amp;&amp;
cd    build &amp;&amp;

cmake -DCMAKE_INSTALL_PREFIX=/usr \
      -DCMAKE_BUILD_TYPE=Release  \
      .. &amp;&amp;

make</userinput></screen>

    <para>
      Tests should be run after installation.
    </para>

    <para>
      Now, as the <systemitem class="username">root</systemitem> user:
    </para>

<screen role="root"><userinput>make install &amp;&amp;
ldconfig</userinput></screen>

    <para>
      To test the results, issue: <command>make test</command>. All
      tests should pass. If any fail, the full results will be in
      <filename>Testing/Temporary/LastTest.log</filename>.
    </para>

    <note>
      <para>
        When upgrading this package, it is possible that the contents
        of the application will remain empty even though everything else
        appears to be working properly.  In this case try removing
        <filename>~/.cache/falkon</filename> and restarting the program.
      </para>
    </note>

    <para>
      If you have installed <application>Pyside2</application> you will want to
      examine <command>hellopython.py</command> which is in the <filename
      class="directory">scripts/</filename> directory, and perhaps copy it to
      your home directory.
    </para>

    <note>
      <para>
        If you are on a non-x86_64 architecture and run into problems with
        missing text, you may wish to export
        <envar>QTWEBENGINE_CHROMIUM_FLAGS="--no-sandbox"</envar> prior to
        running Falkon.
      </para>
    </note>

  </sect2>

  <sect2 role="commands">
    <title>Command Explanations</title>

    <para>
      <option>-DBUILD_TESTING=OFF</option>: This will save a little time and space by
      not building the test programs, use this if you do not wish to run the test.
    </para>

  </sect2>

  <sect2 role="content">
    <title>Contents</title>

    <segmentedlist>
      <segtitle>Installed Programs</segtitle>
      <segtitle>Installed Library</segtitle>
      <segtitle>Installed Directory</segtitle>

      <seglistitem>
        <seg>
          falkon
        </seg>
        <seg>
          libFalkonPrivate.so.3
        </seg>
        <seg>
          /usr/share/falkon
        </seg>
      </seglistitem>
    </segmentedlist>

    <variablelist>
      <bridgehead renderas="sect3">Short Descriptions</bridgehead>
      <?dbfo list-presentation="list"?>
      <?dbhtml list-presentation="table"?>

      <varlistentry id="falkon-prog">
        <term><command>falkon</command></term>
        <listitem>
          <para>
            is a web browser which uses qtwebengine
          </para>
          <indexterm zone="falkon falkon-prog">
            <primary sortas="b-falkon">falkon</primary>
          </indexterm>
        </listitem>
      </varlistentry>

      <varlistentry id="libFalkonPrivate.so.3">
        <term><filename class="libraryfile">libFalkonPrivate.so.3</filename></term>
        <listitem>
          <para>
            contains functions used by falkon
          </para>
          <indexterm zone="falkon libFalkonPrivate.so.3">
            <primary sortas="c-libFalkonPrivate.so.3">libFalkonPrivate.so.3</primary>
          </indexterm>
        </listitem>
      </varlistentry>
    </variablelist>
  </sect2>

</sect1>