[
https://issues.apache.org/jira/browse/KUDU-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin resolved KUDU-2696.
---------------------------------
Fix Version/s: 1.18.0
Resolution: Fixed
The kudu CLI tool can now be built without libgmock linked in. To do so, it's
necessary to run cmake with {{NO_TESTS=1}} and {{KUDU_CLI_TEST_TOOL_ENABLED=0}}
extra flags.
For details, see the following changelists:
*
[7f9b74ff6|https://github.com/apache/kudu/commit/7f9b74ff665d3593e005e31a50d0029f4f2e2619]
*
[83cec9c1e|https://github.com/apache/kudu/commit/83cec9c1ecdd17967bef39f9d990c9c31dc4302c]
For example, to have such a build in DEBUG configuration, configure the project
with the following command line from the build directory:
{noformat}
../../build-support/enable_devtoolset.sh \
../../thirdparty/installed/common/bin/cmake \
-DCMAKE_BUILD_TYPE=debug \
-DNO_TESTS=1 \
-DKUDU_CLI_TEST_TOOL_ENABLED=0 \
../..
{noformat}
> libgmock is linked into the kudu cli binary
> -------------------------------------------
>
> Key: KUDU-2696
> URL: https://issues.apache.org/jira/browse/KUDU-2696
> Project: Kudu
> Issue Type: Bug
> Components: build
> Affects Versions: 1.8.0
> Reporter: Mike Percy
> Priority: Minor
> Fix For: 1.18.0
>
>
> libgmock is linked into the kudu cli binary, even though we consider it a
> test-only dependency. Possibly a configuration problem in our cmake files?
> {code:java}
> $ ldd build/dynclang/bin/kudu | grep mock
> libgmock.so =>
> /home/mpercy/src/kudu/thirdparty/installed/uninstrumented/lib/libgmock.so
> (0x00007f01f1495000)
> {code}
> The gmock dependency does not appear in the server binaries, as expected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
