luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-04-01 05:13:06 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'utkarsh181-main-patch-34260' into 'main'

Browse Source 
compiling.xml: Don't recommend backticks

See merge request GNOME/glib!2143
This commit is contained in:
Philip Withnall 2021-06-09 10:13:27 +00:00
commit 78d43a0502
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/reference/glib/compiling.xml
View File

@ -60,13 +60,13 @@ The difference between the two is that gmodule-2.0 adds
which is often not needed. which is often not needed.
</para> </para>
<para> <para>
The simplest way to compile a program is to use the "backticks" The simplest way to compile a program is to use command substitution
feature of the shell. If you enclose a command in backticks feature of a shell. A command written in the format
(<emphasis>not single quotes</emphasis>), then its output will <literal>$(command)</literal> gets substituted into the command line
be substituted into the command line before execution. So to before execution. So to compile a GLib Hello, World, you would type
compile a GLib Hello, World, you would type the following: the following:
<programlisting> <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> </programlisting>
</para> </para>
<note><para> <note><para>