mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2025-03-03 06:32:10 +01:00
Document gmodule-no-export-2.0
2005-10-05 Matthias Clasen <mclasen@redhat.com> * glib/compiling.sgml: Document gmodule-no-export-2.0
This commit is contained in:
parent
9414478982
commit
a8b39bf42b
@ -1,3 +1,7 @@
|
||||
2005-10-05 Matthias Clasen <mclasen@redhat.com>
|
||||
|
||||
* glib/compiling.sgml: Document gmodule-no-export-2.0
|
||||
|
||||
2005-10-01 Davyd Madeley <davyd@fugro-fsi.com.au>
|
||||
|
||||
* glib/tmpl/string_utils.sgml: Minor documentation improvements for
|
||||
|
@ -32,16 +32,25 @@ $ pkg-config --libs glib-2.0
|
||||
</programlisting>
|
||||
</para>
|
||||
<para>
|
||||
If your application uses modules, threads or <structname>GObject</structname>
|
||||
If your application uses threads or <structname>GObject</structname>
|
||||
features, it must be compiled and linked with the options returned by the
|
||||
following <application>pkg-config</application> invocations:
|
||||
<programlisting>
|
||||
$ pkg-config --cflags --libs gmodule-2.0
|
||||
$ pkg-config --cflags --libs gthread-2.0
|
||||
$ pkg-config --cflags --libs gobject-2.0
|
||||
</programlisting>
|
||||
</para>
|
||||
<para>
|
||||
If your application uses modules, it must be compiled and linked with the options
|
||||
returned by one of the following <application>pkg-config</application> invocations:
|
||||
<programlisting>
|
||||
$ pkg-config --cflags --libs gmodule-no-export-2.0
|
||||
$ pkg-config --cflags --libs gmodule-2.0
|
||||
</programlisting>
|
||||
The difference between the two is that gmodule-2.0 adds <option>--export-dynamic</option>
|
||||
to the linker flags, which is often not needed.
|
||||
</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
|
||||
|
Loading…
x
Reference in New Issue
Block a user