That package also ships CMakeLists.txt files, so you can just build it with their CMake rules.
You can just grab all of the source and have it build a library with that.
OK, looking into this a little further, it seems that there is a
Debian package libgtest-dev, which contains the Googletest source
code, and a google-mock package, which provides the gmock binaries.
It may be possible to adapt the CMake builds to allow us to use these
packages. I'll look into it!
AV
On 7 June 2016 at 18:11, Alex Valavanis <valavanisalex@...400...> wrote:
Summary: If we want to run tests in the PPA, we probably need to
include a copy of gtest source in our repo. Any objections?
Hi All,
Are there any objections to bundling a copy of the Google test
framework source code into our trunk repo? At the moment, we provide
the download-gtest.sh script for grabbing the gtest source from
upstream. However, this presents a couple of issues:
1. It's obviously dependent on a network connection to the upstream
packages being available
2. We can't run the wget download in the Ubuntu builder
Can I suggest that we simply adopt a copy of the gtest source? Are
there any good reasons (e.g. licensing) not to do this? I'm generally
not keen on repo bloat but AFAIU it's generally considered good
practice to bundle test frameworks with project source code.
AV
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...1794...s.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel