Download raw body.
mention MAKE_FLAGS in the Porting Guide
Apparently, over 900 ports use MAKE_FLAGS, so I think it is worth it mentioning MAKE_FLAGS in the guide. Currently it is mentioned among the Special Topics: overriding lib names with SO_VERSION is the major use case it seems, but one might also need it for a simple BUILD_TLS=yes or BUILD_OS=openbsd etc. Jan Index: guide.html =================================================================== RCS file: /cvs/www/faq/ports/guide.html,v diff -u -p -r1.117 guide.html --- guide.html 20 Sep 2026 23:31:32 -0000 1.117 +++ guide.html 15 Oct 2026 12:40:20 -0000 @@ -414,6 +414,15 @@ Use <code>CONFIGURE_ARGS+=</code> to app </ul> <br><li> +Specify a target or variables for the software's <code>Makefile</code>. +<p> +Once configured, most software's build system needs nothing more +than a simple <code>make</code> command. In some cases, however, +it needs to be provided with extra arguments or variable assigments +such as <code>BUILD_TLS=yes</code>. These can be specified +in the port's <code>Makefile</code> using <code>MAKE_FLAGS</code>. + +<br><li> Try building the port with <code>make build</code>. <ul><li>
mention MAKE_FLAGS in the Porting Guide