On 30 January 2013 23:02, Adam Stokes <email address hidden> wrote:
> The google-mock package does provide the source under /usr/src/gmock,
They are not listed in the manifest of
google-mock_1.6.0-0ubuntu3_i386.deb? Instead there are some shared
libraries that, at upstreams request, the Debian package no longer
provides.
> I
> am just having a hard time figuring out why aptitude is not building
> those shared libs in order to run the tests. On Debian, however, those
> shared libs from both gtest and gmock are built and the testsuite is
> executed as expected.
Rather, aptitude builds a single /static/ library if the google-mock
package does not contain the shared library. The build system,
between configure.ac and tests/Makefile.am, is only prepared for the
Debian google-mock packages, so the significant divergance in Ubuntu
may require a minor patch to the these files.
On 30 January 2013 23:02, Adam Stokes <email address hidden> wrote:
> The google-mock package does provide the source under /usr/src/gmock,
They are not listed in the manifest of mock_1. 6.0-0ubuntu3_ i386.deb? Instead there are some shared
google-
libraries that, at upstreams request, the Debian package no longer
provides.
> I
> am just having a hard time figuring out why aptitude is not building
> those shared libs in order to run the tests. On Debian, however, those
> shared libs from both gtest and gmock are built and the testsuite is
> executed as expected.
Rather, aptitude builds a single /static/ library if the google-mock
package does not contain the shared library. The build system,
between configure.ac and tests/Makefile.am, is only prepared for the
Debian google-mock packages, so the significant divergance in Ubuntu
may require a minor patch to the these files.