During my intense troubleshooting with my RPI GW I had to recompile MySensors GW code dozens of times.
There were some points where I didn't know what build options I had at that moment, so I had to rebuild again just to be sure.
My suggestion for feature would be to include the build flags defined somewhere so the user could remember what was defined by the compilation time. This could be either pasted as a comment in the mysensors.conf file or a printout when a special flag is indicated.
$sudo ./bin/mysgw Usage: mysgw [options] Options: -c, --config-file Config file. [/etc/mysensors.conf] -h, --help Display a short summary of all program options. -q, --quiet Quiet mode, disable log messages written to the terminal. --daemon Run as a daemon. --gen-soft-hmac-key Generate and print a soft hmac key. --gen-soft-serial-key Generate and print a soft serial key. --gen-aes-key Generate and print an aes encryption key. --compiled-flags Displays a short summary of the compiling flags when this binary was created $ $sudo ./bin/mysgw --complied-options My Sensors GW for RPI compiled at 2020-12-02 with the following flags: --my-gateway=mqtt --my-controller-ip-address=192.168.2.180 --my-mqtt-publish-topic-prefix=mysensors-out --my-mqtt-subscribe-topic-prefix=mysensors-in --my-mqtt-client-id=MySensorsGW --my-transport=rfm69 --my-signing=software --my-signing-request-signatures --my-rfm69-frequency=433 --my-is-rfm69hw --my-signing-debug --my-rfm69-encryption-enabled --my-mqtt-user=mysensorsuser --my-mqtt-password=mysensorspassword (Other options were default. Consult documentation for further information)
What do you think? Would it be useful? This could also be useful for OrangePI or any other *nix system.