File: compiling.sgml

package info (click to toggle)
gmime 3.2.13%2Bdfsg-2
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 6,208 kB
  • sloc: ansic: 46,569; makefile: 574; sh: 300; python: 8; perl: 6
file content (46 lines) | stat: -rw-r--r-- 1,393 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
<refentry id="gmime-compiling" revision="23 May 2008">
<refmeta>
<refentrytitle>Compiling GMime Applications</refentrytitle>
<manvolnum>3</manvolnum>
<refmiscinfo>GMime Library</refmiscinfo>
</refmeta>

<refnamediv>
<refname>Compiling GMime Applications</refname>
<refpurpose>
How to compile your GMime application
</refpurpose>
</refnamediv>

<refsect1>
<title>Compiling GMime Applications on UNIX</title>

<para>
To compile a GMime application, you need to tell the compiler where to 
find the GMime header files and libraries. This is done with the
<literal>pkg-config</literal> utility.
</para>
<para>
The following interactive shell session demonstrates how
<literal>pkg-config</literal> is used:
<programlisting>
$ pkg-config --cflags gmime-3.0
 -I/usr/include/gmime-3.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include 
$ pkg-config --libs gmime-3.0
 -L/opt/gnome2/lib -lgmime-3.0 -lnsl -lgobject-2.0 -lglib-2.0
</programlisting>
</para>
<para>
The simplest way to compile a program is to use the "backticks"
feature of the shell. If you enclose a command in backticks
(<emphasis>not single quotes</emphasis>), then its output will be
substituted into the command line before execution. So to compile 
a GTK+ Hello, World, you would type the following:
<programlisting>
$ cc `pkg-config --cflags --libs gmime-3.0` hello.c -o hello
</programlisting>
</para>

</refsect1>

</refentry>