diff options
author | Utkarsh Singh <utkarsh190601@gmail.com> | 2021-06-09 10:13:27 +0000 |
---|---|---|
committer | Philip Withnall <philip@tecnocode.co.uk> | 2021-06-09 10:13:27 +0000 |
commit | 47e161d082ff194f95be1aa625e984a62ec97da6 (patch) | |
tree | 901fdc0071dba89140d694922e72401121296a38 | |
parent | 601ef3b6be457a6b0c15ab3a341a0e51f1d02ffd (diff) | |
download | glib-47e161d082ff194f95be1aa625e984a62ec97da6.tar.gz |
compiling.xml: Don't recommend backticks
-rw-r--r-- | docs/reference/glib/compiling.xml | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/reference/glib/compiling.xml b/docs/reference/glib/compiling.xml index 02971a60f..c7a058c5f 100644 --- a/docs/reference/glib/compiling.xml +++ b/docs/reference/glib/compiling.xml @@ -60,13 +60,13 @@ The difference between the two is that gmodule-2.0 adds 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 substituted into the command line before execution. So to -compile a GLib Hello, World, you would type the following: +The simplest way to compile a program is to use command substitution +feature of a shell. A command written in the format +<literal>$(command)</literal> gets substituted into the command line +before execution. So to compile a GLib Hello, World, you would type +the following: <programlisting> -$ cc hello.c `pkg-config --cflags --libs glib-2.0` -o hello +$ cc hello.c $(pkg-config --cflags --libs glib-2.0) -o hello </programlisting> </para> <note><para> |