LIBGCRYPT(1)

πŸ“¦ version 1.10.3, in debian bookworm, ubuntu jammy, ubuntu noble

πŸ’– LIBGCRYPT(1) β€” libgcrypt-config, the little script bestie πŸ’–

ok so this is the manual for libgcrypt-config, from the libgcrypt fam (we're on version 1.4.1 btw), and it lives in section 1 of the manual. she's a config script, she's lowkey essential, and she's about to tell you everything ✨


🌸 NAME 🌸

libgcrypt-config β€” a script to get information about the installed version of libgcrypt. that's it, that's the job, and she does it flawlessly πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

libgcrypt-config [--prefix[=DIR]] [--exec-prefix[=DIR]] [--version]
[--libs] [--cflags] [LIBRARIES]

like. look at her. so simple. so iconic. πŸ¦‹


✨ DESCRIPTION ✨

okay so bestie, here's the tea πŸ“

libgcrypt-config is a tool that's used to configure β€” she figures out the compiler flags and the linker flags you need so you can actually compile and link programs that use libgcrypt. she's the one doing the detective work behind the scenes so your build just... works. no cap. πŸ”₯

she's also used internally by the .m4 macros for GNU autoconf that ship with libgcrypt. so yeah, she's not just out here for you β€” she's carrying the whole autoconf situation on her back too. main character energy fr fr πŸ‘‘


πŸ’œ OPTIONS πŸ’œ

libgcrypt-config accepts the following options, and every single one of them is here, don't worry, we're not skipping anybody:

  • --version β€” prints the currently installed version of libgcrypt to standard output. that's it! just the version! so clean πŸŽ€
  • --libs β€” prints the linker flags you need to link a libgcrypt program. these are the ones you hand to your linker so it stops crying 🫢
  • --cflags β€” prints the compiler flags you need to compile a libgcrypt program. feed these to your compiler and she'll be happy ✨
  • --prefix=PREFIX β€” if you specify this, then PREFIX gets used instead of the installation prefix that libgcrypt was built with, when computing the output for the --cflags and --libs options. this one also gets used for the exec prefix if --exec-prefix wasn't specified. ⚠️ and listen, this matters: this option must be specified before any --libs or --cflags options. order is everything, bestie, don't test her πŸ’€
  • --exec-prefix=PREFIX β€” if you specify this, then PREFIX gets used instead of the installation exec prefix that libgcrypt was built with, when computing the output for the --cflags and --libs options. same rule applies: ⚠️ this option must be specified before any --libs or --cflags options. put it first or it's giving chaos 😭
ok real talk: both of the prefix options are extremely "put me first or I will not work" coded. that's not me being dramatic, that's literally what the manual says. periodt. πŸ’…

🌈 SEE ALSO 🌈

  • libgnutls-config(1) β€” her cousin in the gnutls house, same vibe, different library πŸ¦‹

Copyright © 1998 Owen Taylor, modified for libgcrypt and gnutls by Ivo Timmermans, 2001. iconic lineage honestly 🫢

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation.

like. free to use, free to copy, free to modify, free to distribute β€” just keep the copyright notice in all the copies, and make sure both the copyright notice and this permission notice show up in the supporting documentation. that's the deal, and it's a pretty sweet deal 🌸


Version 26 April 2008 Β· libgcrypt 1.4.1 Β· manual section LIBGCRYPT(1)

and that's the whole page bestie, ty for reading, go compile something cute πŸ’–βœ¨πŸŽ€πŸ¦‹πŸ’