Defining custom message - headers issue

[msadowski]

Hi!

I've just been following the wiki on creating custom messages.

I think exactly the same issue as described here happens when you strictly follow the tutorials. Every generated mavlink.h file defines a header guard as follows:

#pragma once
#ifndef MAVLINK_H
#define MAVLINK_H

This makes it impossible to correctly import a message that is defined in custom_messages.

Let me know if I'm missing something but I feel I've been very thorough when following the wiki!

[hamishwillee]

@msadowski I think you're probably right.

You can only import a header once, so if mavlink.h already included somewhere else in the module this won't work.

I'm not certain, but the first place I can see this being included is https://github.com/PX4/Firmware/blob/master/src/modules/mavlink/mavlink_bridge_header.h#L89
Could you try this replacing the include from standard to custom_messages version in that file?

@julianoes Can you advise?