2ed3236082
Currently the googletest internal tests build after the matching library. However, each of these is serialized at the top level makefile. Additionally some of the tests (e.g. the gmock-matches-test) take up to 90 seconds to build with clang -O2. Having to wait for this test to complete before continuing to the next directory seriously slows down the parllelism of a -j32 build. Before this change running `make -C lib/googletest -j32 -s` in buildenv took 202 seconds, now it's 153 due to improved parallelism. Reviewed By: emaste (no objection) Differential Revision: https://reviews.freebsd.org/D26748
21 lines
363 B
Makefile
21 lines
363 B
Makefile
# $FreeBSD$
|
|
|
|
.include <bsd.init.mk>
|
|
|
|
.PATH: ${GOOGLETEST_SRCROOT}/include ${GOOGLETEST_SRCROOT}/src
|
|
|
|
LIB_CXX= gtest_main
|
|
SHLIB_MAJOR= 0
|
|
PRIVATELIB= true
|
|
|
|
CXXFLAGS+= -I${GOOGLETEST_SRCROOT}/include
|
|
CXXFLAGS+= -I${GOOGLETEST_SRCROOT}
|
|
|
|
LIBADD+= gtest
|
|
# NB: LDFLAGS added for buildworld builds
|
|
LDFLAGS+= -L${LIBGTESTDIR}
|
|
|
|
SRCS+= gtest_main.cc
|
|
|
|
.include <bsd.lib.mk>
|