Page MenuHomeFreeBSD

share/mk: improve CFLAGS description
Needs ReviewPublic

Authored by brooks on May 22 2025, 10:34 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Oct 7, 5:36 PM
Unknown Object (File)
Fri, Oct 3, 4:41 PM
Unknown Object (File)
Fri, Sep 26, 12:51 PM
Unknown Object (File)
Thu, Sep 25, 7:22 PM
Unknown Object (File)
Thu, Sep 25, 1:09 AM
Unknown Object (File)
Wed, Sep 24, 5:12 AM
Unknown Object (File)
Thu, Sep 18, 7:18 AM
Unknown Object (File)
Thu, Sep 18, 3:33 AM
Subscribers

Details

Reviewers
emaste
jhb
Summary

Also document CXXFLAGS.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 64397
Build 61281: arc lint + arc unit

Event Timeline

share/mk/bsd.README
136–139

Should we (in an ideal world, absent legacy and backwards compatibility considerations) really have CPPFLAGS and reserve CFLAGS specifically for C?

share/mk/bsd.README
136–139

Certainly something C specific would be good, but we also need something to pass all the common flags. We've got a lot of ABI stuff in CFLAGS via bsd.cpu.mk. Likewise we add -target and --sysroot to XCFLAGS so they end up in CFLAGS.

share/mk/bsd.README
136–139

Maybe either "things that are run though the C preprocessor" or "Flags to the compiler when compiling most things processed by the C preprocessor."?

152–153

This seems more consistent with the wording used for AFLAGS and CFLAGS?

  • Rephrased with some help from @jhb