simfqt-config(1)

πŸ“¦
version 1.00.13 Β· 3 versions
, in fedora 44

πŸ’– simfqt-config πŸ’–

okay bestie, so this is the simfqt-config page from the General Commands Manual section, and it's literally the little helper script that keeps the whole build situation from falling apart. let's get into it 🫢


✨ NAME ✨

simfqt-config β€” the Configuration Script for the C++ Simulated Fare Quote System Library

like... it's the glow-up assistant for the SimFQT library's build setup. that's the whole job. πŸ’…


🌸 SYNOPSIS 🌸

simfqt-config [--prefix] [--version] [--libs] [--cflags]

no cap, that's the whole vibe. you run it, you pass it a flag, it tells you a thing. 😌


πŸ¦‹ DESCRIPTION πŸ¦‹

so simfqt-config is the tool that configure uses to figure out which compiler flags and linker flags you need to actually compile and link programs that use SimFQT. it's giving backstage crew energy β€” nobody claps for it, but nothing works without it. πŸ’€

it's also used internally by the .m4 macros that ship with SimFQT, for GNU autoconf. so yeah, it's pulling double duty. main character behavior tbh. πŸ‘‘


πŸŽ€ OPTIONS πŸŽ€

simfqt-config accepts the following options, and honestly? each one ate:

  • --help β€” displays this help and exits. it's the "just tell me what's going on" option and we respect her for it. πŸ’–
  • --prefix β€” shows the SimFQT installation prefix. like, where did you even put this thing, bestie.
  • --version β€” prints the currently installed version of SimFQT on the standard output. the receipts. the origin story. πŸ”₯
  • --libs β€” prints the linker flags that are necessary to link with the SimFQT library. these are the flags you need, not the flags you want. periodt.
  • --cflags β€” prints the compiler flags that are necessary to compile with the SimFQT library. compiler said "give me the right flags or I'm not doing it" and honestly? fair. ✨
  • --sampledir β€” shows where the (StdAir CSV) sample files are located. sample files, but make it CSV. πŸ“
  • --mandir β€” shows where the manual pages are located. yes, the very pages like this one. meta. πŸ¦‹
  • --infodir β€” shows where the information pages are located. not the man pages, the info pages. they're different and they know it. πŸ’œ
  • --docdir β€” shows the documentation base directory. the mothership of docs. 🌈
  • --htmldocpath β€” shows where the HTML documentation is located. web-friendly docs, slay. ⭐
  • --refmanpath β€” shows where the PDF documentation is located. for the girlies who like a reference manual they can scroll through like a magazine. 🧚

πŸ’œ SEE ALSO πŸ’œ

go read those too, they're all part of the same little friend group. 🫢


Copyright Β© 2009-2011 Denis Arnaud

see the COPYING file for more info on the (LGPLv2+) license, or just go straight to the internet at:

http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html

πŸ’€ reminder bestie: the license info lives in COPYING, and the (LGPLv2+) is the one you're working with here. don't skip the paperwork, iykyk.

and that's the whole page, no notes. this was SimFQT, Version 1.00.13 β€” mwah, take care of her πŸ’…πŸŽ€πŸ’–

πŸ“¦ where this page comes from