@LorenzMeier he has a good point here

Indeed. Let’s get this closed.

UPDATED @LorenzMeier Confirmed offline that the following need to be documented (these allow you to configure the library for your needs and e.g. make it more efficient and less standalone).

• MAVLINK_USE_CONVENIENCE_FUNCTIONS
• MAVLINK_COMM_NUM_BUFFERS
• MAVLINK_SIGNING_FLAG_SIGN_OUTGOING
• MAVLINK_SIGNING_FLAG_NO_TIMESTAMPS
• MAVLINK_EXTERNAL_RX_STATUS
• MAVLINK_EXTERNAL_RX_BUFFER
• NATIVE_BIG_ENDIAN - Set to use MAVLink on a system that is native big-endian (MAVLINK_LITTLE_ENDIAN true by default)
• MAVLINK_SEPARATE_HELPERS - option to provide alternative implementation of mavlink_helpers.h

The following do not need to be documented - they are internal/not intended to be tuned:

• MAVLINK_STACK_BUFFER - ? Default is 0
• MAVLINK_NEED_BYTE_SWAP
• MAVLINK_MAX_SIGNING_STREAMS
• MAVLINK_MESSAGE_CRCS
• MAVLINK_MAX_PAYLOAD_LEN ///< Maximum payload length // it is possible to override this, but be careful! Default 255
• MAVLINK_SIGNATURE_BLOCK_LEN
• MAVLINK_MAX_FIELDS 64 //Any benefit to changing number of fields in message
• Do we need these - don't appear to be used?
  • MAV_MSG_ENTRY_FLAG_HAVE_TARGET_SYSTEM 1
  • MAV_MSG_ENTRY_FLAG_HAVE_TARGET_COMPONENT 2
• MAVLINK_ALIGNED_FIELDS
• MAVLINK_CRC_EXTRA - This enables MAVLink 2 checking that message is supported via CRC. Would you ever disable it.
• MAVLINK_ASSERT

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions.

This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions.

This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions.