paparazzi-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[paparazzi-commits] [paparazzi/paparazzi] eceffb: [ocaml] apply a second


From: Gautier Hattenberger
Subject: [paparazzi-commits] [paparazzi/paparazzi] eceffb: [ocaml] apply a second topological sort to modules...
Date: Tue, 09 Nov 2021 07:04:16 -0800

  Branch: refs/heads/master
  Home:   https://github.com/paparazzi/paparazzi
  Commit: eceffb8bd535e233e0a0640a0f6547521562ef30
      
https://github.com/paparazzi/paparazzi/commit/eceffb8bd535e233e0a0640a0f6547521562ef30
  Author: Gautier Hattenberger <gautier.hattenberger@enac.fr>
  Date:   2021-11-09 (Tue, 09 Nov 2021)

  Changed paths:
    M conf/modules/ahrs_common.xml
    M conf/modules/firmwares/rotorcraft.xml
    M conf/modules/guidance_rotorcraft.xml
    M conf/modules/nav_basic_rotorcraft.xml
    M conf/modules/stabilization_rotorcraft.xml
    M conf/modules/targets/fbw.xml
    M sw/lib/ocaml/aircraft.ml

  Log Message:
  -----------
  [ocaml] apply a second topological sort to modules (#2793)

* [ocaml] apply a second topological sort to modules

After the first one, all functionalities are checked, but corresponding
modules are not ordered with the other one.
This second sorting algorithm (simpler) is just checking that final
selection of modules is correctly ordered and check for possible cyclic
dependencies not yet found.
ahrs_common dep node is fixed to avoid such a situation.

* [modules] trying to fix cyclic dependency in rotorcraft gnc modules

the main issue is that the rotorcraft navigation is not explicitely
included by the user but automagically included, which is not a good
idea, same goes for guidance.

* [modules] fix dep

system_core is already provided by firmware module and @no_settings
was making a cyclic dep for fbw





reply via email to

[Prev in Thread] Current Thread [Next in Thread]