You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As stated, compiling MAVROS on Mac will result in an fatal error: 'endian.h' file not found error in include/mavlink/v2.0/common/../msgmap.hpp:4:10:. Technically this is a mavlink issue, but mavlink actually compiles fine, it's just the generated header points to a file that doesn't exist and this error only pops up when you compile something else that uses mavlink, like mavros.
This is actually a long standing error on Mac, I've found the workaround to be found here. Basically create /usr/include/endian.h from this. However this messing around with system header files is highly unsatisfactory and unsafe so I'm seeing if anyone can take a look at the included file and maybe come up with a solution.
The text was updated successfully, but these errors were encountered:
@eric1221bday this is not something that can be solved on our side. Some type of workaround can possibly be added to cmake, but we currently try to solve problems on supported platforms. Mac is not the case. So if you find a way that we can integrate this into the build system, great. Otherwise we don't have the bandwidth to help you out. Besides, I personally don't have a Mac to do the development.
As stated, compiling MAVROS on Mac will result in an
fatal error: 'endian.h' file not found
error ininclude/mavlink/v2.0/common/../msgmap.hpp:4:10:
. Technically this is a mavlink issue, but mavlink actually compiles fine, it's just the generated header points to a file that doesn't exist and this error only pops up when you compile something else that uses mavlink, like mavros.This is actually a long standing error on Mac, I've found the workaround to be found here. Basically create
/usr/include/endian.h
from this. However this messing around with system header files is highly unsatisfactory and unsafe so I'm seeing if anyone can take a look at the included file and maybe come up with a solution.The text was updated successfully, but these errors were encountered: