subversion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Branko ─îibej <br...@wandisco.com>
Subject Re: [PATCH] OPW 2013: Build System Gtest Addition
Date Sat, 02 Feb 2013 10:31:42 GMT
On 01.02.2013 19:34, Gabriela Gibson wrote:
> On 22/01/13 12:03, Stefan Sperling wrote:
>> On Tue, Jan 22, 2013 at 11:15:30AM +0000, Gabriela Gibson wrote:
>>> Part of my 2013 OPW Project for Subversion is to add the Googletest
> First of all thanks to Ben for rescuing my messy post =)
>
> Also thanks to everyone who gave me hints!
>
> ---
>
> At this point I have ./configure --enable-gtest working but the show
> stops here:
>
> [[[
> g++ -std=c++98  -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE   -g
> -O2  -I./subversion/include -I./subversion -I/home/g/trunk/\
> apr/include   -I/home/g/trunk/apr-util/include
> -I/home/g/trunk/sqlite-amalgamation  gtest/src/gtest-all.cc
> gtest/src/gtest-all.cc:39:25: fatal error: gtest/gtest.h: No such file
> or directory
> (...snip...)
> gtest/src/gtest-all.cc:39:25: fatal error: gtest/gtest.h: No such file
> or directory
> compilation terminated.
> make: *** [gtest/src/gtest-all.lo] Error 1
> ]]]
>
> Looking at the file in question I find:
>
> [[[
> // This line ensures that gtest.h can be compiled on its own, even
> // when it's fused.
> #include "gtest/gtest.h"
> ]]]
>
> The file in question is located here: /trunk/gtest/include/gtest/gtest.h
>
> also a similar problem exists when using autogen.sh:
>
> [[[
> Creating build-outputs.mk...
> WARNING: "gtest/internal/gtest-port.h" header not found, file
> gtest/src/gtest-internal-inl.h
> WARNING: "gtest/gtest.h" header not found, file gtest/src/gtest-internal-inl.h
> WARNING: "gtest/gtest-spi.h" header not found, file
> gtest/src/gtest-internal-inl.h
> Creating svn_private_config.h.in...
> ]]]
>
> again, the files exist, but not where gtest thinks they should be.
>
> What can I do about that, if anything?
You could try adding ${abs_srcdir}/gtest/include to the include path. :)
Also, you'll get rid of those warnings by adding appropriate paths to
the private-includes list in build.conf.

-- Brane

-- 
Branko ─îibej
Director of Subversion | WANdisco | www.wandisco.com


Mime
View raw message