Re: Scalable way to manage configuration flags

That's how I would do it; yes. Though, I would use 'default-if-blank'
and 'error-if-blank'
heavily to keep myself sane.

- https://github.com/bahmanm/bmakelib/blob/main/doc/error-if-blank.md
- https://github.com/bahmanm/bmakelib/blob/main/doc/default-if-blank.md


--
Bahman Movaqar   (he/him)

Problem solver =E2=97=8F Software engineer =E2=97=8F Hands-on leader
https://linktr.ee/bahmanm


On Fri, 19 Jun 2026 at 16:28, Heime <[email protected]> wrote:

>
> To pass set makeinfo options using a makefile, I have included
> the css and split variables in my makefile.
>
> For html there exist other makeinfo options, like --css-ref=3DURL,
> --internal-links=3DFILE, --transliterate-file-names, and --node-files.
>
> To add these as user otpions, would I similarly add a corresponding
> variable for each?
>
> ifneq ($(css),)
>         css =3D --css-include=3D$(css)
> endif
>
> ifneq ($(split),)
>         split =3D --split=3D$(split)
> endif
>
>
> .PHONY: split-chapter split-section split-node
>
> split-chapter: split=3D--split=3Dchapter
> split-section: split=3D--split=3Dsection
> split-node: split=3D--split=3Dnode
>
> split-chapter split-section split-node: $(hmldir)/antares.html
>
> .SECONDEXPANSION:  # Enable second expansion of $(@D)
>
> $(hmldir)/antares.html: $(srcs) | $$(@D)
>         makeinfo $(opts) --html $(split) -o $@ $<
>
>
>
>
>