Hello, On Wed, Jun 29, 2011 at 11:43:11AM -0400, Yaroslav Halchenko wrote:
> Could you please comment on this issue with libgtest-dev and
> gtest-config? I have not spotted anything obvious among
> changelogs.
While preparing the latest upload, I found out that the Google Test
authors recommend against distributing the compiled libgtest library.
Instead, users are expected to directly use the sources, located in
/usr/src/test.
I expect to remove the compiled libgtest in a subsequent upload.
Removal of gtest-config was a side-effect of switching from the
now-deprecated autoconf-based build to the upstream-supported
cmake-based build. Because I expected to remove libgtest in future, I
did not worry about this loss. So, yes, the removal was intentional.
I do apologize for breaking the build. I should have alerted
maintainers of packages using libgtest-dev.
Regards,
-Steve
P.S. Here is the contents of gtest's README.Debian, which attempts to
explain this. Let me know if it needs clarifying.
Use of precompiled libgtest Not Recommended
-------------------------------------------
The Google C++ Testing Framework uses conditional compilation for some
things. Because of the C++ "One Definition Rule", gtest must be
compiled with exactly the same flags as your C++ code under test.
Because this is hard to manage, upstream no longer recommends using
precompiled libraries [1]. This release still contains a precompiled
libgtest, but it will be removed in a future upload.
Using GTest with your project
-----------------------------
See the upsream README for instructions on using gtest with your
project. The sources for libgtest are installed into /usr/src/gtest.
See /usr/share/doc/libgtest-dev/examples for a complete example
including a sample makefile.
[1]
http://groups.google.com/group/googletestframework/browse_thread/thread/668eff1cebf5309d
-- Steve M. Robbins <[email protected]>, Sun, 12 Jun 2011 12:27:48 -0500
signature.asc
Description: Digital signature
