SC-CONFIG(1)

💅 SC-CONFIG(1) — like, the whole manual, but make it make sense 🎀

okay bestie, so this is page one of the General Commands Manual — the SC-CONFIG(1) one — and it's literally just about one tiny script that tells you how SC got built on your machine. that's it. that's the whole vibe. ✨

---

🌸 NAME 🌸

sc-config — a script that gives you the deets about the installed version of SC. that's the entire job. it's giving "personal assistant for your compiler flags." 💅

---

🦋 SYNOPSIS 🦋

sc-config [--prefix[=DIR] ] [--exec-prefix[=DIR] ] [--version] [--libs]
[--cppflags] [--cc] [--cflags] [--cxx] [--cxxflags] [--f77] [--f77flags]

like, you just run it with whatever flags you need and it hands you the info. no cap. 🫶

---

💖 DESCRIPTION 💖

the sc-config program is your little hookup for the compilers, the compiler options, and the libraries you need to actually use the SC (Scientific Computing) toolkit from your own program. that's it — it's the middleman between your code and SC, and honestly? the middleman ate. 🔥

---

✨ OPTIONS ✨

sc-config returns info about how SC was compiled and installed. here's everything that's available, no gatekeeping: 👑

• --prefix — the directory where SC is installed. the home base. the address. 🏠
• --version — the version of SC. so you know what you're working with. 💖
• --libdir — the directory where the libraries are found. (yes, the original page says "were" — we're keeping it, it's iconic. 😭) 📁
• --libs — the libraries and library paths you need to link. the whole link package, bestie. 🔗
• --cppflags — the include directories you need to build. 🛠️
• --cc — the C compiler. 🧚
• --cflags — the C compiler flags. 🚩
• --cxx — the C++ compiler. 💜
• --cxxflags — the C++ compiler flags. 🚩
• --f77 — the FORTRAN 77 compiler. (yes, FORTRAN 77. she's vintage and she's slaying. 👑) 🧓
• --f77flags — the FORTRAN 77 compiler flags. 🚩

heads up: the synopsis also lists --prefix[=DIR] and --exec-prefix[=DIR] with the optional =DIR bit — that's exactly how it's written up top, so if you saw those and wondered, no you didn't, they're right there in the synopsis. 🫶

---

🌈 EXAMPLES 🌈

okay so say you wanna link your executable to SC. use a Makefile for GNU make similar to this one and you're literally done:

SCCONFIG = /usr/bin/sc-config
CXX := $(shell $(SCCONFIG) --cxx)
CXXFLAGS := $(shell $(SCCONFIG) --cxxflags)
CPPFLAGS := $(shell $(SCCONFIG) --cppflags)
LIBS := $(shell $(SCCONFIG) --libs)

myprog: myprog.o
        $(CXX) $(CXXFLAGS) -o $@ $^ $(LIBS)

look at that. the $(shell ...) calls are just asking sc-config for the deets and dropping them straight into your variables. main character Makefile energy fr fr. 🎀

---

⭐ a lil sign-off ⭐

that's the page, bestie — Version 2, dated 15 Feb 2001, from the SC-CONFIG(1) manual. old? yes. iconic? also yes. now go compile something gorgeous. 💖✨🦋💅