BGLMAKE(1)

💖 BGLMAKE — bestie edition 💖

okay so this is bglmake, a General Commands Manual page, and it's literally the makefile generator for Bigloo and I'm obsessed. sit down, hydrate, let's go 🫶

---

✨ NAME ✨

bglmake — create or update Bigloo makefiles 💅

---

🌸 SYNOPSIS 🌸

bglmake [ options ] [ sourcefile ]

---

🦋 DESCRIPTION 🦋

so basically bglmake reads sourcefile, computes the transitive closure of the import relationship (yes bestie, the whole dependency web, all of it), and then generates a makefile file. what's that makefile for? it gets used by the glmake(1) program to compile your application or your library. main character behavior fr fr 👑

and if you don't hand it a sourcefile? no worries. bglmake will just display the template file for generating Makefile. it's giving "here's the blueprint, you do the rest" 🎀

---

💅 OPTIONS 💅

• -v — Verbose mode. she talks. a lot. 😭
• -q — Prevent loading the ~/.bglmakerc user configuration file. no outside opinions today, thanks 🙈
• -suffix <suf> — Adds suf to the bglmake source file suffixes list. the default suffixes are "scm", "sch" and "bgl". iconic trio ⭐
• file — is the name of the "main" file for an application, or the name of the "heap" file for a library. yep, same slot, two jobs, she's flexible 💁
• -I<path> — Add path to the directory list read for searching Bigloo source files. go look here too bestie 🔍
• -X<path> — Exclude path from the directory list read for searching Bigloo source files. not here though. blocked. 🚫
• -o <makefile> — The name of the makefile file to be updated. name your baby 🍼
• -p <name> — The name of the project. This name is used in backup and versionning entries. yes it's spelled "versionning" in the original and I respect it 💜
• -t <name> — The name of the target binary file or the name of the library. 🎯
• -f<template> — Set an alternative template file. bring your own fit ✨
• -object <obj> — Update the makefile for adding obj to the object list. one more for the roster 📋
• -source <src> — Update the makefile for adding src to the source file list. and one more 🧚
• -main <file> — Set the initial main file and tells bglmake that the project is an "application" (by opposition to libraries). This File is the starting point of the transitive closure of the imported modules. she's the origin story 🌈
• -heap <file> — Set the initial heap file and tells bglmake that the project is a "library" (by opposition to applications). This File is the starting point of the transitive closure of the imported modules. library era, let's go 📚

---

🎀 TEMPLATES 🎀

when bglmake generates a makefile, it uses templates. these templates may be specified with some option, or they can just be printed out — for that it is enough to call bglmake without any parameter. no args, just vibes 🫶

template files use some extra "macro". they are:

🌟 $[PROJECT]

this macro is replaced with the project name (option -p). If no -p option is used, the default project name is the name of the current directory that contains the sourcefile. default slay ✨

🌟 $[TARGET_NAME]

this macro is replaced with the target name (option -t). If no -t option is used, the default target name is the name of the current directory that contains the sourcefile. same energy, different macro 💖

🌟 $[MAKEFILE]

this macro is replaced with the makefile name (-o option). 🗂️

---

🔥 EXAMPLE 🔥

A Makefile is created by `bglmake foo.scm -o Makefile`. Then it may be updated with `make updatemakefile`.

bglmake foo.scm -o Makefile
make updatemakefile

look at her go 😭💖

---

👑 SEE ALSO 👑

bigloo(1), bglafile(1), bgldepend(1), bgltags(1), make(1), bglmco(1)

(the whole friend group, go say hi 🫶)

---

💜 AUTHOR 💜

Manuel SERRANO, Manuel.Serrano@inria.fr

---

no cap, that's the whole page. every flag, every macro, every default, all of it, untouched. the facts stayed, only the vibe got a glow up 💅

---

and that's the tea, bestie — this was BGLMAKE(1), a General Commands Manual page, dated Aug 15 1998. iconic since the nineties, periodt. 🎀✨💖