1. 29 Mar, 2016 1 commit
  2. 20 Mar, 2016 1 commit
  3. 19 Mar, 2016 2 commits
  4. 14 Mar, 2016 2 commits
  5. 10 Mar, 2016 1 commit
  6. 04 Mar, 2016 4 commits
  7. 03 Mar, 2016 2 commits
    • Kenton Varda's avatar
      Merge pull request #289 from zarvox/pkg-config-exec-prefix · b260dd17
      Kenton Varda authored
      *.pc.in: add exec_prefix lines
      b260dd17
    • Drew Fisher's avatar
      *.pc.in: add exec_prefix lines · 34dcf746
      Drew Fisher authored
      The removal of exec_prefix in a900f200
      caused the generated .pc files to be unusable when built with autotools.
      
      The generated libdir value would read:
      
        libdir=${exec_prefix}/lib
      
      but since exec_prefix was unspecified, pkg-config would choke:
      
        zarvox@localhost $ pkg-config capnp-rpc --cflags --libs
        Variable 'exec_prefix' not defined in '/usr/local/lib/pkgconfig/capnp-rpc.pc'
      34dcf746
  8. 26 Feb, 2016 1 commit
  9. 22 Feb, 2016 1 commit
  10. 16 Feb, 2016 2 commits
  11. 15 Feb, 2016 1 commit
  12. 06 Feb, 2016 1 commit
  13. 01 Feb, 2016 1 commit
  14. 29 Jan, 2016 4 commits
  15. 26 Jan, 2016 1 commit
  16. 13 Jan, 2016 2 commits
    • Kenton Varda's avatar
      ceb38966
    • Kenton Varda's avatar
      Fix message corruption bug introduced in 2c9c5c83. · 4d4f831a
      Kenton Varda authored
      As of that change, adopting an empty struct into a pointer that already had some other value fails to overwrite the upper 32 bits of the pointer, thus resulting in a struct pointer with totally bogus bounds. Normally this will either cause a bounds check exception to be thrown when that pointer is later accessed, or lead to a struct containing bogus data (but if teh struct was expected to be empty, probably that data is never accessed).
      4d4f831a
  17. 09 Jan, 2016 2 commits
  18. 07 Jan, 2016 6 commits
  19. 04 Jan, 2016 1 commit
  20. 26 Dec, 2015 1 commit
  21. 24 Dec, 2015 1 commit
  22. 17 Dec, 2015 1 commit
  23. 16 Dec, 2015 1 commit