Comments (10)
Original comment by [email protected]
on 31 Jul 2008 at 6:38
- Added labels: OpSys-Linux, OpSys-OSX, Type-Enhancement
- Removed labels: Type-Defect
from googletest.
Chandler, what do you think of this suggestion?
Original comment by [email protected]
on 17 Sep 2008 at 9:46
- Changed state: Accepted
- Added labels: ****
- Removed labels: ****
from googletest.
Alternatively one could use the autoconf macro AX_CXX_CHECK_LIB (http://ac-
archive.sourceforge.net/guidod/ax_cxx_check_lib.html)
i.e.
AX_CXX_CHECK_LIB( gtest, [testing::TestInfo::name() const] )
Original comment by housemaister
on 3 Nov 2008 at 8:30
- Added labels: ****
- Removed labels: ****
from googletest.
Certainly, projects using can use AX_CXX_CHECK_LIB to test for the presence of
gtest.
However, that macro is not part of the standard autoconf library, and many projects
may not be setup to use local macros.
The inclusion of gtest_version_cstr would be very simple, and shouldn't break
anything.
Original comment by [email protected]
on 5 Feb 2009 at 5:34
- Added labels: ****
- Removed labels: ****
from googletest.
r.w.johnstone, I don't have experience with autotools - would you like to
submit a
patch for me to review? Thanks.
Original comment by [email protected]
on 5 Jun 2009 at 6:27
- Added labels: ****
- Removed labels: ****
from googletest.
zhanyong.wan, the patch is more or less outlined in the original post that
opened
this issue. The goal is to simply provide a function with C linkage, which can
be
found by autotools. A new source file, simply version.c, with the following
function:
extern "C" char const* gtest_version_cstr()
{
static char const msg[] = "googletest 1.0.0";
return msg;
}
The exact body of the function is actually secondary.
Original comment by [email protected]
on 5 Jun 2009 at 7:49
- Added labels: ****
- Removed labels: ****
from googletest.
Lower the priority since autotools is being phased out.
Original comment by [email protected]
on 23 Dec 2009 at 6:59
- Added labels: Priority-Low, Usability
- Removed labels: Priority-Medium
from googletest.
@[email protected]
The version function is an improvement for uses of gtest that use autotools (or
other build tools like scons). As I
see it, it is not related to the build system used by gtest itself.
Original comment by [email protected]
on 23 Dec 2009 at 7:27
- Added labels: ****
- Removed labels: ****
from googletest.
@dirk.mst, you are right that the two are different things. That's why I didn't
close the issue as "won't fix". Some users of gtest choose autotools because
gtest
uses it. After we switch away from autotools, such users won't have a reason
to use
autotools any more. Therefore the priority of this is lowered.
Original comment by [email protected]
on 23 Dec 2009 at 3:54
- Added labels: ****
- Removed labels: ****
from googletest.
We now consider it a bad practice to install pre-compiled gtest -- see
http://code.google.com/p/googletest/wiki/FAQ?ts=1285613232&updated=FAQ#Why_is_it
_not_recommended_to_install_a_pre-compiled_copy_of_Goog
Therefore I'm closing this as "won't fix".
Original comment by [email protected]
on 27 Sep 2010 at 6:49
- Changed state: WontFix
- Added labels: ****
- Removed labels: ****
from googletest.
Related Issues (20)
- need EXPECT_THAT and matchers from googlemock HOT 2
- need to get rid of the use of UnitTestAccessor in the event API samples before releasing 1.4.0 HOT 1
- ParseGoogleTestFlagsOnlyImpl implementation issue HOT 2
- Assertion messages printed twice on Windows CE HOT 2
- Long assertion messages don't show up on Windows CE HOT 3
- Elapsed time on Windows CE does not work correctly HOT 3
- Patch to fix MinGW compilation HOT 3
- Using RecordProperty without XML output HOT 1
- RecordProperty support for double/bool/char/etc HOT 1
- need to check whether our uses of GTEST_SUPPRESS_UNREACHABLE_CODE_WARNING_BELOW_ are OK HOT 2
- GCC compilation error "error: conversion from `void' to non-scalar type" HOT 4
- Even if all tests using a fixture class are DISABLED_ SetUp() still seems to be run. HOT 7
- Gtests run under Visual Studio but not under Team Build HOT 4
- Build Issues in VS2005 HOT 2
- Ehance upload_gtest.py to support http proxy HOT 1
- Adding Symbian Project Definition File HOT 7
- Extended SCOPED_TRACE HOT 4
- ASSERT_DOUBLE_EQ(0.0, x) fails for 0 < x < std::numeric_limits<double>::epsilon() HOT 1
- ASSERT_STRCASEEQ and ASSERT_STRCASENE macros should compare strings consistently across platforms
- Should report the source file location of the TEST that throws an exception
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from googletest.