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
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
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
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
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
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
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
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
from googletest.
Related Issues (20)
- Project home summary says wiki links are on right, but they are on the left
- With 32-bit target, icc generates remarks about cast of void * to 64-bit integer in PrintTo
- [deleted issue]
- Unable to determine if a test should run before calling RUN_ALL_TESTS HOT 2
- My assert is not caught and the test fails HOT 2
- Throwing an exception as default breaks call count expectation HOT 3
- I put my tests in a library and Google Test doesn't run them - GCC 4.8 HOT 3
- Unknown option specified: gtest_output
- error:SEH exception with code 0xc0000005 thrown in auxiliary test code<environment or event listeners>
- Compilation errors on MinGW
- Duplicate Symbols adding Samples (Xcode)
- PATCH: Fix ‘make check’ in separate build directory
- SEGV on 4 or more test cases with Address Sanitizer HOT 5
- Add the ability to specify parameterized test names
- moving to GITHUB ?
- Plase add a way to skip/disable some tests during runtime.
- README CMake section missing step of putting built libraries into lib subdirectory
- New release
- memory leak when gtest are printing
- Include BUILD for building with bazel
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.