1. 06 Dec, 2020 1 commit
  2. 17 Nov, 2020 2 commits
  3. 13 Nov, 2020 1 commit
  4. 11 Nov, 2020 2 commits
  5. 04 Oct, 2020 1 commit
  6. 02 Oct, 2020 1 commit
  7. 01 Sep, 2020 2 commits
  8. 31 Aug, 2020 1 commit
  9. 28 Aug, 2020 1 commit
  10. 03 Aug, 2020 1 commit
  11. 30 Jul, 2020 1 commit
  12. 27 Jul, 2020 1 commit
  13. 01 Jul, 2020 1 commit
  14. 10 Jun, 2020 1 commit
    • Maxime Perrotin's avatar
      Detect errors in the interface view · 0f729389
      Maxime Perrotin authored
      If the interface view defines context parameters that have no associated
      type (asn1 type or Timer) they are still silently saved by the GUI,
      resulting in a badly formed AADL file. It is now detected and reported
      by kazoo
      0f729389
  15. 21 May, 2020 1 commit
  16. 15 May, 2020 1 commit
  17. 12 May, 2020 1 commit
  18. 11 May, 2020 2 commits
  19. 10 May, 2020 1 commit
  20. 08 May, 2020 1 commit
  21. 07 May, 2020 1 commit
  22. 03 May, 2020 1 commit
  23. 02 May, 2020 1 commit
  24. 30 Apr, 2020 5 commits
  25. 29 Apr, 2020 2 commits
  26. 17 Apr, 2020 1 commit
  27. 14 Apr, 2020 2 commits
  28. 05 Mar, 2020 1 commit
  29. 04 Mar, 2020 1 commit
    • Maxime Perrotin's avatar
      Add parsing of arinc653.aadl · baf895f0
      Maxime Perrotin authored
      This is needed if user uses a custom AADL file in the command line
      For example if user set this flag: --no-stdlib then
      ocarina_components.aadl will not be parsed. User in that case has to
      provide a custom library of components, like the one used for the AIR
      plaform. But when an extra aadl file is passed in the command line,
      kazoo does not know if it references Interface or Deployment components
      so it parses it together with both Interface and Deployment views.
      The deployment view parser already parses arinc653.aadl, but by default
      the interface view parser did not (that is normally not needed)
      baf895f0
  30. 03 Mar, 2020 1 commit