PTH-CONFIG(1)

💖 PTH-CONFIG(1) — the GNU Portable Threads build-bestie 💖

okay so bestie, welcome to pth-config, a lil' helper from the GNU Portable Threads fam, chilling in section 1 of the manual. she's tiny, she's useful, she's literally just here to make your life easier. 🫶

---

✨ VERSION ✨

GNU Pth 2.0.7 — dated 08-Jun-2006. vintage! iconic! 💅

---

🌸 SYNOPSIS 🌸

pth-config [--help] [--version] [--all] [--prefix] [--exec-prefix]
[--bindir] [--libdir] [--includedir] [--mandir] [--datadir] [--acdir]
[--cflags] [--ldflags] [--libs]

---

🦋 DESCRIPTION 🦋

so pth-config is this adorable little helper utility 💖 whose whole job is making it easy to configure and build applications based on the pth(3) library. that's it. that's the girl's purpose.

what she actually does: you ask her questions, and she tells you the C compiler and linker flags you need so your app compiles and links correctly against pth(3). no cap. she's giving "personal assistant who only speaks in flags." 👑

---

💅 OPTIONS 💅

pth-config accepts the following options:

• --help — prints the short usage information. your girl is being helpful, obviously. 🙈
• --version — prints the version number and date of the installed pth(3) library. receipts! 📅
• --all — forces the output of all flags, that is, including extra flags which are not Pth specific. the full unhinged dump, basically. ✨
• --prefix — prints the installation prefix of architecture independent files.
• --exec-prefix — prints the installation prefix of architecture dependent files.
• --bindir — prints the installation directory of binaries.
• --libdir — prints the installation directory of libraries.
• --includedir — prints the installation directory of include headers.
• --mandir — prints the installation directory of manual pages. (hi, that's this one 🎀)
• --datadir — prints the installation directory of shared data.
• --acdir — prints the installation directory of autoconf data.
• --cflags — prints the C compiler flags needed to compile the pth(3)-based application. the output is usually added to the "CFLAGS" variable of the application's "Makefile". 🛠️
• --ldflags — prints the linker flags (-L) needed to link the application with the pth(3) library. the output is usually added to the "LDFLAGS" variable of the application's "Makefile". 🔗
• --libs — prints the library flags (-l) needed to link the application with the pth(3) library. the output is usually added to the "LIBS" variable of the application's "Makefile". 📚

---

🔥 EXAMPLE 🔥

here's the whole vibe in one Makefile, bestie. look how clean:

CC      = cc
CFLAGS  = -O `pth-config --cflags`
LDFLAGS = `pth-config --ldflags`
LIBS    = -lm `pth-config --libs`

all: foo
foo: foo.o
    $(CC) $(LDFLAGS) -o foo foo.o $(LIBS)
foo.o: foo.c
    $(CC) $(CFLAGS) -c foo.c

she ATE. the backticks do the talking and pth-config does the rest. 💅✨

---

🌈 SEE ALSO 🌈

pth(3), cc(1).

like, go read those too. iykyk. 👑

---

👑 AUTHOR 👑

Ralf S. Engelschall
rse@engelschall.com
www.engelschall.com

---

and that's the whole page, bestie!! 🎀 this version was living inside GNU Pth 2.0.7, dated 08-Jun-2006 — so like, shoutout to the archives for keeping her safe. mwah. 💖✨🦋