Build failure due to AppleClang 12 (I thought the latest version addressed this, but looks like I was testing with AppleClang 11). The project is actively working on it: envoyproxy/envoy#13364

@ankane Would it make sense to also include the envoy build config option --config=sizeopt? In my testing that brought down the size of the static binary from ~400MB to ~80MB. Not sure if there might also be any other build options that would make sense for standard production usage.

@timsutton Do you know if/how that affects portability?

@timsutton Do you know if/how that affects portability?

Sadly I do not, besides it looking like this maps to c compiler optimizations. It didn't seem to change at all which frameworks were linked in, though I didn't check to see if any features changed.

@SMillerDev Updated to the newly released 1.16.0, which fixes the tests.

@timsutton I think it's better to go with the default build options (unless someone from the project can confirm the size optimizations don't affect portability).

I think it's better to go with the default build options (unless someone from the project can confirm the size optimizations don't affect portability).

We generally prefer to only use default options unless there's a strong case for adding more. I'd say 300mb storage space isn't that strong a case in a time of 1TB micro-SD cards.

👍 makes sense to me to keep the default options unless there's a very strong argument to run the size optimization. @ankane Thanks for writing this formula!

@SMillerDev has triggered a merge.

Thanks!