1. 19 Sep, 2017 4 commits
  2. 13 Sep, 2017 1 commit
  3. 08 Sep, 2017 1 commit
  4. 06 Sep, 2017 4 commits
  5. 30 Aug, 2017 1 commit
  6. 25 Aug, 2017 1 commit
  7. 24 Aug, 2017 5 commits
  8. 23 Aug, 2017 1 commit
  9. 18 Aug, 2017 1 commit
  10. 13 Jul, 2017 1 commit
  11. 12 Jul, 2017 1 commit
  12. 10 Jul, 2017 1 commit
  13. 06 Jul, 2017 1 commit
  14. 30 Jun, 2017 2 commits
  15. 28 Jun, 2017 1 commit
  16. 27 Jun, 2017 1 commit
  17. 22 Jun, 2017 1 commit
  18. 21 Jun, 2017 1 commit
  19. 20 Jun, 2017 1 commit
  20. 18 Jun, 2017 2 commits
  21. 16 Jun, 2017 1 commit
  22. 12 Jun, 2017 1 commit
  23. 08 Jun, 2017 1 commit
  24. 24 May, 2017 1 commit
    • MARCHE Claude's avatar
      allow relative pathnames for drivers stored in the Why3 config file · eb751c1b
      MARCHE Claude authored
      If drivers in why3.conf are simple names like "alt_ergo", then the driver file
      is search as <datadir>/drivers/alt_ergo.drv
      
      This behavior is now the same as when a driver is given with option -D on the
      command line for why3prove, why3replay or why3extract
      
      Reminder: the datadir is either given as
      1) the environment variable WHY3DATA
      2) the field "datadir" of the [main] section of the
         why3 config file if exists
      3) or by default the compile-time datadir
      eb751c1b
  25. 22 May, 2017 1 commit
  26. 19 May, 2017 3 commits