Ignore:
Timestamp:
06/30/2012 01:20:50 PM (12 years ago)
Author:
Krejzi <krejzi@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
4c796cf
Parents:
784ec394
Message:

D-Bus 1.6.2 and libquicktime 1.2.4

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@10378 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed

  • general/sysutils/dbus.xml

    r784ec394 r0b83a69  
    77  <!ENTITY dbus-download-http "http://dbus.freedesktop.org/releases/dbus/dbus-&dbus-version;.tar.gz">
    88  <!ENTITY dbus-download-ftp  " ">
    9   <!ENTITY dbus-md5sum        "16dcae2dd0c76e398381601ac9acdec4">
    10   <!ENTITY dbus-size          "1.8 MB">
    11   <!ENTITY dbus-buildsize     "29 MB">
     9  <!ENTITY dbus-md5sum        "7fbf877ed6ff7da6df90f07158373829">
     10  <!ENTITY dbus-size          "1.9 MB">
     11  <!ENTITY dbus-buildsize     "115 MB">
    1212  <!ENTITY dbus-time          "0.5 SBU">
    1313]>
    … …  
    3030    <title>Introduction to D-Bus</title>
    3131
    32     <para><application>D-Bus</application> is a message bus system, a simple
    33     way for applications to talk to one another.
    34     <application>D-Bus</application> supplies both a system daemon (for events
    35     such as <quote>new hardware device added</quote> or <quote>printer queue
    36     changed</quote>) and a per-user-login-session daemon (for general IPC needs
    37     among user applications). Also, the message bus is built on top of a
    38     general one-to-one message passing framework, which can be used by any two
    39     applications to communicate directly (without going through the message bus
    40     daemon).</para>
     32    <para>
     33      <application>D-Bus</application> is a message bus system, a simple
     34      way for applications to talk to one another.
     35      <application>D-Bus</application> supplies both a system daemon (for events
     36      such as <quote>new hardware device added</quote> or <quote>printer queue
     37      changed</quote>) and a per-user-login-session daemon (for general IPC needs
     38      among user applications). Also, the message bus is built on top of a
     39      general one-to-one message passing framework, which can be used by any two
     40      applications to communicate directly (without going through the message bus
     41      daemon).
     42    </para>
    4143
    4244    &lfs71_checked;
    … …  
    4547    <itemizedlist spacing="compact">
    4648      <listitem>
    47         <para>Download (HTTP): <ulink url="&dbus-download-http;"/></para>
     49        <para>
     50          Download (HTTP): <ulink url="&dbus-download-http;"/>
     51        </para>
    4852      </listitem>
    4953      <listitem>
    50         <para>Download (FTP): <ulink url="&dbus-download-ftp;"/></para>
     54        <para>
     55          Download (FTP): <ulink url="&dbus-download-ftp;"/>
     56        </para>
    5157      </listitem>
    5258      <listitem>
    53         <para>Download MD5 sum: &dbus-md5sum;</para>
     59        <para>
     60          Download MD5 sum: &dbus-md5sum;
     61        </para>
    5462      </listitem>
    5563      <listitem>
    56         <para>Download size: &dbus-size;</para>
     64        <para>
     65          Download size: &dbus-size;
     66        </para>
    5767      </listitem>
    5868      <listitem>
    59         <para>Estimated disk space required: &dbus-buildsize;</para>
     69        <para>
     70          Estimated disk space required: &dbus-buildsize;
     71        </para>
    6072      </listitem>
    6173      <listitem>
    62         <para>Estimated build time: &dbus-time;</para>
     74        <para>
     75          Estimated build time: &dbus-time;
     76        </para>
    6377      </listitem>
    6478    </itemizedlist>
    … …  
    7387
    7488    <bridgehead renderas="sect4">Recommended</bridgehead>
    75     <para role="recommended"><xref linkend="xorg7-lib"/>
    76     (for <command>dbus-launch</command> program)</para>
     89    <para role="recommended">
     90      <xref linkend="xorg7-lib"/>
     91      (for <command>dbus-launch</command> program)
     92    </para>
    7793
    7894    <bridgehead renderas="sect4">Optional</bridgehead>
    … …  
    8399    </para>
    84100
    85     <para>Note that the <command>configure</command> script will look for
    86     <xref linkend="xmlto"/> but it does nothing as the XML/HTML documentation is
    87     already shipped in the source tree.</para>
     101    <para>
     102      Note that the <command>configure</command> script will look for
     103      <xref linkend="xmlto"/> but it does nothing as the XML/HTML documentation is
     104      already shipped in the source tree.
     105    </para>
    88106
    89107    <para condition="html" role="usernotes">User Notes:
    90     <ulink url="&blfs-wiki;/dbus"/></para>
    91 
    92   </sect2>
    93 
    94   <sect2 role="kernel" id='dbus-kernel'>
    95     <title>Kernel Configuration</title>
    96 
    97     <para>Ensure the following option is enabled in the kernel configuration
    98     and recompile the kernel if necessary:</para>
    99 
    100 <screen><literal>General Setup
    101   System V IPC</literal></screen>
    102 
    103     <indexterm zone="dbus dbus-kernel">
    104       <primary sortas="d-dbus">dbus</primary>
    105     </indexterm>
    106 
     108      <ulink url="&blfs-wiki;/dbus"/>
     109    </para>
    107110  </sect2>
    108111
    … …  
    110113    <title>Installation of D-Bus</title>
    111114
    112     <para>As the <systemitem class="username">root</systemitem> user, create a
    113     system user and group to handle the system message bus activity:</para>
     115    <para>
     116      As the <systemitem class="username">root</systemitem> user, create a
     117      system user and group to handle the system message bus activity:
     118    </para>
    114119
    115120<screen role="root"><userinput>groupadd -g 18 messagebus &amp;&amp;
    … …  
    117122        -u 18 -g messagebus -s /bin/false messagebus</userinput></screen>
    118123
    119     <para>Install <application>D-Bus</application> by running the following
    120     commands (you may wish to review the output from
    121     <command>./configure --help</command> first and add any desired parameters
    122     to the <command>configure</command> command shown below):</para>
     124    <para>
     125      Install <application>D-Bus</application> by running the following
     126      commands (you may wish to review the output from
     127      <command>./configure --help</command> first and add any desired parameters
     128      to the <command>configure</command> command shown below):
     129    </para>
    123130
    124131<screen><userinput>./configure --prefix=/usr \
    125132            --sysconfdir=/etc \
     133            --localstatedir=/var \
    126134            --libexecdir=/usr/lib/dbus-1.0 \
    127             --localstatedir=/var \
     135            --with-console-auth-dir=/run/console/ \
     136            --without-systemdsystemunitdir \
     137            --disable-systemd \
    128138            --disable-static &amp;&amp;
    129139make</userinput></screen>
    130140
    131     <para>See below for test instructions.</para>
    132 
    133     <para>Now, as the <systemitem class="username">root</systemitem>
    134     user:</para>
     141    <para>
     142      See below for test instructions.
     143    </para>
     144
     145    <para>
     146      Now, as the <systemitem class="username">root</systemitem> user:
     147    </para>
    135148
    136149<screen role="root"><userinput>make install &amp;&amp;
    137150mv -v /usr/share/doc/dbus /usr/share/doc/dbus-&dbus-version;</userinput></screen>
    138151
    139     <para>The dbus tests cannot be run until after <xref linkend="dbus-glib"/>
    140     has been installed.  The tests require passing additional parameters to
    141     <command>configure</command> and exposing additional functionality in the
    142     binaries. These interfaces are not intended to be used in a production
    143     build of <application>D-Bus</application>.  If you would like to run the
    144     unit tests, issue the following commands:</para>
     152    <para>
     153      The dbus tests cannot be run until after <xref linkend="dbus-glib"/>
     154      has been installed. The tests require passing additional parameters to
     155      <command>configure</command> and exposing additional functionality in the
     156      binaries. These interfaces are not intended to be used in a production
     157      build of <application>D-Bus</application>.  If you would like to run the
     158      unit tests, issue the following commands:
     159    </para>
    145160   
    146161<screen><userinput>make distclean &amp;&amp;
    … …  
    150165make distclean</userinput></screen>
    151166
    152     <para>Note there has been a report that the tests may fail if running
    153     inside a Midnight Commander shell.
    154     You may get out-of-memory error messages when running the tests.
    155     These are normal and can be safely ignored.</para>
     167    <para>
     168      Note there has been a report that the tests may fail if running
     169      inside a Midnight Commander shell.
     170      You may get out-of-memory error messages when running the tests.
     171      These are normal and can be safely ignored.
     172    </para>
    156173
    157174  </sect2>
    … …  
    160177    <title>Command Explanations</title>
    161178
    162     <para><parameter>--libexecdir=/usr/lib/dbus-1.0</parameter>: This will
    163     install binaries meant to be only used internally by
    164     <application>D-Bus</application>, and the directory
    165     <filename class="directory">dbus-1</filename> into
    166     <filename class="directory">/usr/lib/dbus-1.0</filename> instead of
    167     into <filename class="directory">/usr/libexec</filename>.</para>
    168 
    169     <para><parameter>--localstatedir=/var</parameter>: This parameter causes
    170     the daemon PID file, system bus socket and machine uuid file to be
    171     created in the <filename class="directory">/var</filename> directory
    172     instead of the <filename class="directory">/usr/var</filename>
    173     directory.</para>
    174 
    175     <para><parameter>--enable-tests</parameter>: Build extra parts of the code
    176     to support testing. Configure will end with a NOTE warning about this.</para>
    177 
    178     <para><parameter>--enable-asserts</parameter>: Enable debugging code to run
    179     assertions for statements normally assumed to be true. This prevents a
    180     warning that '<parameter>--enable-tests</parameter>' on its own is only useful
    181     for profiling and might not give true results for all tests, but adds its own
    182     NOTE that this should not be used in a production build.
     179    <para>
     180      <parameter>--libexecdir=/usr/lib/dbus-1.0</parameter>: This will
     181      ensure that <application>D-Bus</application> internal support
     182      program is installed in the prefered directory
     183      <filename class="directory">/usr/lib/dbus-1.0</filename> instead of
     184      <filename class="directory">/usr/libexec</filename>.
     185    </para>
     186
     187    <para>
     188      <parameter>--with-console-auth-dir=/run/console/</parameter>: This
     189      parameter specifies location of the
     190      <application>ConsoleKit</application>  auth dir.
     191    </para>
     192
     193    <para>
     194      <option>--without-systemdsystemunitdir</option>: This switch prevents
     195      installation of systemd unit files.
     196    </para>
     197
     198    <para>
     199      <option>--disable-systemd</option>: This switch disables systemd
     200      support in <application>D-Bus</application>
    183201    </para>
    184202
    185203    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    186     href="../../xincludes/static-libraries.xml"/>   
     204      href="../../xincludes/static-libraries.xml"/>
     205
     206    <para>
     207      <option>--enable-tests</option>: Build extra parts of the code to support
     208      testing. Configure will end with a NOTE warning about this.
     209    </para>
     210
     211    <para>
     212      <option>--enable-asserts</option>: Enable debugging code to run assertions for
     213      statements normally assumed to be true. This prevents a warning that
     214      '<parameter>--enable-tests</parameter>' on its own is only useful for profiling
     215      and might not give true results for all tests, but adds its own NOTE that this
     216      should not be used in a production build.
     217    </para>
    187218
    188219  </sect2>
    … …  
    193224    <sect3 id="dbus-config">
    194225      <title>Config Files</title>
    195       <para><filename>/etc/dbus-1/session.conf</filename>,
    196       <filename>/etc/dbus-1/system.conf</filename> and
    197       <filename>/etc/dbus-1/system.d/*</filename></para>
     226
     227      <para>
     228        <filename>/etc/dbus-1/session.conf</filename>,
     229        <filename>/etc/dbus-1/system.conf</filename> and
     230        <filename>/etc/dbus-1/system.d/*</filename>
     231      </para>
    198232
    199233      <indexterm zone="dbus dbus-config">
    … …  
    214248      <title>Configuration Information</title>
    215249
    216       <para>The configuration files listed above should probably not be
    217       modified. If changes are required, you should create
    218       <filename>/etc/dbus-1/session-local.conf</filename> and/or
    219       <filename>/etc/dbus-1/system-local.conf</filename> and make any
    220       desired changes to these files.</para>
    221 
    222       <para>If any packages install a
    223       <application>D-Bus</application> <filename>.service</filename>
    224       file outside of the standard <filename
    225       class="directory">/usr/share/dbus-1/services</filename> directory,
    226       that directory should be added to the local session configuration.
    227       For instance, <filename
    228       class="directory">/usr/local/share/dbus-1/services</filename> can
    229       be added by performing the following commands as the
    230       <systemitem class="username">root</systemitem> user:</para>
     250      <para>
     251        The configuration files listed above should probably not be
     252        modified. If changes are required, you should create
     253        <filename>/etc/dbus-1/session-local.conf</filename> and/or
     254        <filename>/etc/dbus-1/system-local.conf</filename> and make any
     255        desired changes to these files.
     256     </para>
     257
     258      <para>
     259        If any packages install a
     260        <application>D-Bus</application> <filename>.service</filename>
     261        file outside of the standard <filename
     262        class="directory">/usr/share/dbus-1/services</filename> directory,
     263        that directory should be added to the local session configuration.
     264        For instance, <filename
     265        class="directory">/usr/local/share/dbus-1/services</filename> can
     266        be added by performing the following commands as the
     267        <systemitem class="username">root</systemitem> user:
     268      </para>
    231269
    232270<screen role="root"><userinput>cat &gt; /etc/dbus-1/session-local.conf &lt;&lt; "EOF"
    … …  
    247285      <title>Boot Script</title>
    248286
    249       <para>To automatically start <command>dbus-daemon</command> when the
    250       system is rebooted, install the
    251       <filename>/etc/rc.d/init.d/dbus</filename> bootscript from the
    252       <xref linkend="bootscripts"/> package.</para>
     287      <para>
     288        To automatically start <command>dbus-daemon</command> when the
     289        system is rebooted, install the
     290        <filename>/etc/rc.d/init.d/dbus</filename> bootscript from the
     291        <xref linkend="bootscripts"/> package.
     292      </para>
    253293
    254294      <indexterm zone="dbus dbus-init">
    … …  
    258298<screen role="root"><userinput>make install-dbus</userinput></screen>
    259299
    260       <para>Note that this boot script only starts the system-wide
    261       <application>D-Bus</application> daemon. Each user requiring access to
    262       <application>D-Bus</application> services will also need to run a
    263       session daemon as well. There are many methods you can use to start a
    264       session daemon using the <command>dbus-launch</command> command. Review
    265       the <command>dbus-launch</command> man page for details about the
    266       available parameters and options. Here are some suggestions and
    267       examples:</para>
     300      <para>
     301        Note that this boot script only starts the system-wide
     302        <application>D-Bus</application> daemon. Each user requiring access to
     303        <application>D-Bus</application> services will also need to run a
     304        session daemon as well. There are many methods you can use to start a
     305        session daemon using the <command>dbus-launch</command> command. Review
     306        the <command>dbus-launch</command> man page for details about the
     307        available parameters and options. Here are some suggestions and
     308        examples:
     309      </para>
    268310
    269311      <itemizedlist spacing="compact">
    270312        <listitem>
    271           <para>Add <command>dbus-launch</command> to the line in the
    272           <filename>~/.xinitrc</filename> file that starts your graphical
    273           desktop environment<!-- as shown in <xref linkend="gnome-config"/>-->.</para>
    274         </listitem>
    275         <listitem>
    276           <para>If you use <command>xdm</command> or some other display manager
    277           that calls the <filename>~/.xsession</filename> file, you can add
    278           <command>dbus-launch</command> to the line in your
    279           <filename>~/.xsession</filename> file that starts your graphical
    280           desktop environment. The syntax would be similar to the example in
    281           the <filename>~/.xinitrc</filename> file.</para>
    282         </listitem>
    283 <!-- Enabled by default.
    284         <listitem>
    285           <para>If you use <command>gdm</command> or some other display manager
    286           that utilizes custom files to initiate sessions, use the example in
    287           <xref linkend="gdm-config-dbus"/> of the
    288           <application>GDM</application> instructions to create a file
    289           containing <command>dbus-launch</command>.</para>
    290         </listitem>-->
    291         <listitem>
    292           <para>The examples shown previously use
    293           <command>dbus-launch</command> to specify a program to be run. This
    294           has the benefit (when also using the
    295           <parameter>--exit-with-session</parameter> parameter) of stopping the
    296           session daemon when the specified program is stopped. You can also
    297           start the session daemon in your system or personal startup scripts
    298           by adding the following lines:</para>
     313          <para>
     314            Add <command>dbus-launch</command> to the line in the
     315            <filename>~/.xinitrc</filename> file that starts your graphical
     316            desktop environment.
     317          </para>
     318        </listitem>
     319        <listitem>
     320          <para>
     321            If you use <command>xdm</command> or some other display manager
     322            that calls the <filename>~/.xsession</filename> file, you can add
     323            <command>dbus-launch</command> to the line in your
     324            <filename>~/.xsession</filename> file that starts your graphical
     325            desktop environment. The syntax would be similar to the example in
     326            the <filename>~/.xinitrc</filename> file.
     327          </para>
     328        </listitem>
     329        <listitem>
     330          <para>
     331            The examples shown previously use
     332            <command>dbus-launch</command> to specify a program to be run. This
     333            has the benefit (when also using the
     334            <parameter>--exit-with-session</parameter> parameter) of stopping the
     335            session daemon when the specified program is stopped. You can also
     336            start the session daemon in your system or personal startup scripts
     337            by adding the following lines:
     338          </para>
    299339
    300340<screen><userinput><literal># Start the D-Bus session daemon
    … …  
    302342export DBUS_SESSION_BUS_ADDRESS</literal></userinput></screen>
    303343
    304           <para>This method will not stop the session daemon when you exit
    305           your shell, therefore you should add the following line to your
    306           <filename>~/.bash_logout</filename> file:</para>
     344          <para>
     345            This method will not stop the session daemon when you exit
     346            your shell, therefore you should add the following line to your
     347            <filename>~/.bash_logout</filename> file:
     348          </para>
    307349
    308350<screen><userinput><literal># Kill the D-Bus session daemon
    … …  
    311353
    312354        <listitem>
    313           <para>A hint has been written that provides ways to start scripts
    314           using the KDM session manager of KDE. The concepts in this hint could
    315           possibly be used with other session managers as well. The hint is
    316           located at <ulink
    317           url="&hints-root;/downloads/files/execute-session-scripts-using-kdm.txt"/>.
     355          <para>
     356            A hint has been written that provides ways to start scripts
     357            using the KDM session manager of KDE. The concepts in this hint could
     358            possibly be used with other session managers as well. The hint is
     359            located at <ulink
     360            url="&hints-root;/downloads/files/execute-session-scripts-using-kdm.txt"/>.
    318361          </para>
    319362        </listitem>
    … …  
    330373    <segmentedlist>
    331374      <segtitle>Installed Programs</segtitle>
    332       <segtitle>Installed Libraries</segtitle>
     375      <segtitle>Installed Library</segtitle>
    333376      <segtitle>Installed Directories</segtitle>
    334377
    335378      <seglistitem>
    336         <seg>dbus-cleanup-sockets, dbus-daemon, dbus-launch, dbus-monitor,
    337         dbus-send and dbus-uuidgen</seg>
    338         <seg>libdbus-1.so</seg>
    339         <seg>/etc/dbus-1, /usr/include/dbus-1.0, /usr/lib/dbus-1.0,
    340         /usr/share/dbus-1, /usr/share/doc/dbus-1.6.0 and /var/run/dbus</seg>
     379        <seg>
     380          dbus-cleanup-sockets, dbus-daemon, dbus-launch, dbus-monitor,
     381          dbus-send and dbus-uuidgen
     382        </seg>
     383        <seg>
     384           libdbus-1.so
     385        </seg>
     386        <seg>
     387          /etc/dbus-1,
     388          /usr/include/dbus-1.0,
     389          /usr/lib/dbus-1.0,
     390          /usr/share/dbus-1,
     391          /usr/share/doc/dbus-&dbus-version; and
     392          /var/lib/dbus
     393        </seg>
    341394      </seglistitem>
    342395    </segmentedlist>
    … …  
    350403        <term><command>dbus-cleanup-sockets</command></term>
    351404        <listitem>
    352           <para>is used to clean up leftover sockets in a directory.</para>
     405          <para>
     406            is used to clean up leftover sockets in a directory.
     407          </para>
    353408          <indexterm zone="dbus dbus-cleanup-sockets">
    354409            <primary sortas="b-dbus-cleanup-sockets">dbus-cleanup-sockets</primary>
    … …  
    360415        <term><command>dbus-daemon</command></term>
    361416        <listitem>
    362           <para>is the <application>D-Bus</application> message bus
    363           daemon.</para>
     417          <para>
     418            is the <application>D-Bus</application> message bus daemon.
     419          </para>
    364420          <indexterm zone="dbus dbus-daemon">
    365421            <primary sortas="b-dbus-daemon">dbus-daemon</primary>
    … …  
    371427        <term><command>dbus-launch</command></term>
    372428        <listitem>
    373           <para>is used to start <command>dbus-daemon</command> from a shell
    374           script. It  would  normally be called from a user's login
    375           scripts.</para>
     429          <para>
     430            is used to start <command>dbus-daemon</command> from a shell
     431            script. It  would  normally be called from a user's login
     432            scripts.
     433          </para>
    376434          <indexterm zone="dbus dbus-launch">
    377435            <primary sortas="b-dbus-launch">dbus-launch</primary>
    … …  
    383441        <term><command>dbus-monitor</command></term>
    384442        <listitem>
    385           <para>is used to monitor messages going through a
    386           <application>D-Bus</application> message bus.</para>
     443          <para>
     444            is used to monitor messages going through a
     445            <application>D-Bus</application> message bus.
     446          </para>
    387447          <indexterm zone="dbus dbus-monitor">
    388448            <primary sortas="b-dbus-monitor">dbus-monitor</primary>
    … …  
    394454        <term><command>dbus-send</command></term>
    395455        <listitem>
    396           <para>is used to send a message to a <application>D-Bus</application>
    397           message bus.</para>
     456          <para>
     457            is used to send a message to a <application>D-Bus</application>
     458            message bus.
     459          </para>
    398460          <indexterm zone="dbus dbus-send">
    399461            <primary sortas="b-dbus-send">dbus-send</primary>
    … …  
    405467        <term><command>dbus-uuidgen</command></term>
    406468        <listitem>
    407           <para>is used to generate or read a universally unique ID.</para>
     469          <para>
     470            is used to generate a universally unique ID.
     471          </para>
    408472          <indexterm zone="dbus dbus-uuidgen">
    409473            <primary sortas="b-dbus-uuidgen">dbus-uuidgen</primary>
    … …  
    415479        <term><filename class='libraryfile'>libdbus-1.so</filename></term>
    416480        <listitem>
    417           <para>contains the API functions used by the
    418           <application>D-Bus</application> message daemon.
    419           <application>D-Bus</application> is first a library that provides
    420           one-to-one communication between any two applications;
    421           <command>dbus-daemon</command> is an application that uses this
    422           library to implement a message bus daemon.</para>
     481          <para>
     482            contains the API functions used by the
     483            <application>D-Bus</application> message daemon.
     484            <application>D-Bus</application> is first a library that provides
     485            one-to-one communication between any two applications;
     486            <command>dbus-daemon</command> is an application that uses this
     487            library to implement a message bus daemon.
     488          </para>
    423489          <indexterm zone="dbus libdbus-1">
    424490            <primary sortas="c-libdbus-1">libdbus-1.so</primary>
    … …  
    432498
    433499</sect1>
     500 
Note: See TracChangeset for help on using the changeset viewer.