- sitl_gazebo in PX4/Firmware (560a9b45): https://github.com/PX4/sitl_gazebo/commit/3d80f63562c24c1537e1f8423ce649c99ebc15ea
    - sitl_gazebo current upstream: https://github.com/PX4/sitl_gazebo/commit/2adc86b5bf84543091470966caf33c3b4f3ee666
    - Changes: https://github.com/PX4/sitl_gazebo/compare/3d80f63562c24c1537e1f8423ce649c99ebc15ea...2adc86b5bf84543091470966caf33c3b4f3ee666

    2adc86b 2018-11-14 Elia Tarasov - add max value for wind and wind gust means
fb20a36 2018-11-14 Elia Tarasov - add normal gaussian distribution to wind gust force and direction
bd5ce12 2018-11-14 Elia Tarasov - add normal gaussian distribution to wind force and direction
913c094 2018-11-07 Jacob Schloss - reverse order of test
7d08ef5 2018-11-07 Jacob Schloss - fall back to only enabling up to c++14 on old cmake
0fd93b0 2018-11-07 Jacob Schloss - set CMAKE_CXX_STANDARD so cmake does not append a defualt language standard

The open flag `U` causes a deprecation warning starting with Python 3.4.
The option to open all kinds of newlines as `\n` has been replaced with
the argument `newline=None`. However, this argument is not available for
Python 2 unless we use `io.open` instead of `open`.

    Define the logical LED that are uses on sitl

    Define the logical LED that are uses on px4nucleoF767ZI-v1

    Define the logical LED that are uses on px4fmu-v5

    Define the logical LED that are uses on px4fmu-v4pro

    Define the logical LED that are uses on px4fmu-v4

    Define the logical LED that are uses on px4fmu-v2

    Define the logical LED that are uses on px4-stm32f4discovery

    Define the logical LED that are uses on px4-same70xplained-v1

    Define the logical LED that are uses on omnibus-f4sd

    Define the logical LED that are uses on nxphlite-v3

    Define the logical LED that are uses on mindpx-v2

    Define the logical LED that are uses on crazyflie

    Define the logical LED that are uses on auav-x21

    Define the logical LED that are uses on aerofc-v1

   add support for all the LEDS to support
   BOARD_HAS_CONTROL_STATUS_LEDS

   This commit is the groundwork to fix the power LED
   blinking on V5

   Background:
   ----------
   Early boards only had an AMBER LED that was used to
   indicate a High Load condition.

   This change defines the new logical inteface
   the LED_<color> should not be used in application
   code moving forward, only the minipulator macros
   should be used.

       Logical usage             Legacy default
      ------------------------+-------------
       BOARD_OVERLOAD_LED     | LED_RED

   Later boards defined BOARD_HAS_CONTROL_STATUS_LEDS
   and added the use of a BLUE and GREEN LED that were
   used as follows:

   Logical usage             Legacy default
      ------------------------+-------------
       BOARD_ARMED_LED        | LED_BLUE
       BOARD_ARMED_STATE_LED  | LED_GREEN

   With this PR a board may now define _only_ a subset
   the leds and map them at the board level to the
   color LED it wants to use.

       Logical usage             Legacy default
      ------------------------+-------------
       BOARD_OVERLOAD_LED     | LED_RED
    when BOARD_HAS_CONTROL_STATUS_LEDS is defined
       BOARD_ARMED_LED        | LED_BLUE
       BOARD_ARMED_STATE_LED  | LED_GREEN

   If any of the BOARD_{OVERLOAD|ARMED|ARMED_STATE}_LED are not
   defined. The code output generates a null action for that
   LED.

Fixes bugs causing learned or GEO lookup declination to not be used in some circumstances.

https://github.com/PX4/ecl/pull/518
https://github.com/PX4/ecl/pull/520

to save the time running the installer for every build
which was necessary before because the folder exceedes
the maximum of 1GB cache of the appveyor free plan