On Fri, Apr 28, 2017 at 9:04 PM, David Yu <[email protected]> wrote:
> Any special reason for dropping gtest? It works well on windows like on > Unix platforms. > To be honest, this happened like two years ago and I don't remember all of the motivations anymore. But, IIRC there were a number of little frustrations around having this as an external dependency. For example, builds were broken when Google Code shut down. Also, various package maintainers would argue about whether gtest should be a dev package dependency vs. bundled. The people arguing for making it a dependency would then run into gtest's curious decision to outlaw installing it system-wide, leading to confusion. Meanwhile it took me a couple hours to add a fine unit test framework to KJ, so one day I did it... and I've been pretty happy with the results. -Kenton -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/capnproto.
