1. 08 Jan, 2020 2 commits
  2. 31 Dec, 2019 3 commits
  3. 19 Dec, 2019 2 commits
  4. 16 Dec, 2019 1 commit
  5. 13 Dec, 2019 3 commits
  6. 11 Dec, 2019 2 commits
  7. 06 Dec, 2019 1 commit
  8. 04 Dec, 2019 1 commit
  9. 28 Nov, 2019 3 commits
  10. 27 Nov, 2019 1 commit
    • Cristian Maglie's avatar
      Added library dependency support (#351) · b544181e
      Cristian Maglie authored
      * Added infrastructure to handle 'dependency' field in library index
      
      * Added globals.ParseLibraryReferenceArgs method
      
      * Added check for missing library version/name in args
      
      * Added check for missing core/arch/version in core arg parsing
      
      * 100% test coverage for librariesindexer module
      
      * Added grpc call LibraryResolveDependencies (WIP)
      
      This is just the body of the call, no implementation yet.
      
      * Use semver.Dependency interface to represent a library dependency
      
      * Added library-dep resolution function in core modules
      
      * Added implementation for LibraryResolveDependency grpc call
      
      * Implementation of deps install in 'lib install' command
      
      * Added no-deps flag in lib install command
      
      * Added lib deps command
      b544181e
  11. 26 Nov, 2019 1 commit
  12. 21 Nov, 2019 1 commit
  13. 20 Nov, 2019 1 commit
    • Cristian Maglie's avatar
      Terminate daemon command when parent process exits; added "--daemonize" flag... · c30151b0
      Cristian Maglie authored
      Terminate daemon command when parent process exits; added "--daemonize" flag to keep old behaviour (#488)
      
      * daemon: terminate on parent process ending; added --daemonize flag
      
      This is useful when the cli daemon is launched from an external process
      to avoid leaving zombie process if the parent process unexpectedly dies.
      
      If daemonization (so no stdin/stdout) is the intended behaviour the
      --daemonize flag must be used.
      
      * (cosmetic) reorganized runDaemonCommand in a more straighforward way
      c30151b0
  14. 19 Nov, 2019 1 commit
  15. 13 Nov, 2019 2 commits
  16. 11 Nov, 2019 2 commits
  17. 08 Nov, 2019 2 commits
  18. 07 Nov, 2019 1 commit
  19. 05 Nov, 2019 3 commits
  20. 04 Nov, 2019 3 commits
    • Cristian Maglie's avatar
      Board identification: always check vid.1/pid.1 (#463) · 007b5819
      Cristian Maglie authored
      * Board identification: always check vid.1/pid.1
      
      Even if vid.0/pid.0 is missing.
      
      Fix #456
      
      * Renamed 'again'->'present' and 'found'->'matched' for clarity
      007b5819
    • Cristian Maglie's avatar
      temporarily disable CI tests on macosx (#470) · 5e2203bd
      Cristian Maglie authored
      It seems that the package bou.ke/monkey is no longer supported with the
      lastest macosx (it fails with a Permission denied error).
      5e2203bd
    • Matthijs Kooijman's avatar
      Fix handling of referenced cores (#467) · ef63c623
      Matthijs Kooijman authored
      * Add tests for ResolveFQBN
      
      This adds tests for ResolveFQBN (which returns more details than the
      FindBoardWithFQBN that was already tested), but also adds an extra
      boards.txt with boards that are derived from another platform/core (i.e.
      have `build.core=package:core`.
      
      These new tests are currently failing, because of a bug and insufficient
      error handling, which will be fixed in subsequent commits.
      
      * Fix resolution of referenced cores
      
      A core is referenced by specifying `build.core=package:core` in board
      properties. However, the code used the second part (core) both for
      looking up the the package, as well as for the core to use from that
      package. The most commonly used core reference is `arduino:arduino`
      which works because both parts are identical, which is probably why this
      bug has not shown up before.
      
      This commit fixes the bug by simply using the right part to look up the
      package.
      
      * Improve error message when referencing missing package
      
      This used to say e.g.
      
      	missing platform adafruit:referenced:avr required for build
      
      where two packagenames (adafruit and referenced) were joined together
      which makes no sense. Now, it just mentions the missing package, and the
      fqbn that references it.
      
      * Fix segfault when referenced platform is missing
      
      Before, when a platform was referenced through a `build.core` and the
      package was present by the platform/architecure was missing, a
      nullpointer was passed to GetInstalledPlatformRelease, which would
      segfault.
      
      Now, a proper error message is returned.
      ef63c623
  21. 30 Oct, 2019 1 commit
  22. 29 Oct, 2019 3 commits