The Autotools build scripts require too much effort to use as a subdir package

[GoogleCodeExporter]

Leveraging Google Mock as a subdirectory package via Autotools (likely a
common configuration) requires quite a bit of manual setup for the client
project, the vast majority of which will be identical with every other
client project. We should provide a M4-based macro that not only can
leverage an installed copy of Google Mock, but can automate some (if not
all) of the process of configuring and building Google Mock as a subdir
package with Autotools.

Original issue reported on code.google.com by chandl...@gmail.com on 11 Dec 2008 at 6:45

[GoogleCodeExporter]

Original comment by zhanyong...@gmail.com on 4 Mar 2009 at 7:11

• Added labels: OpSys-Linux, OpSys-OSX, Usability

[GoogleCodeExporter]

Original comment by zhanyong...@gmail.com on 5 Jun 2009 at 5:25

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

We've decided to phase out the use of autotools.

Original comment by w...@google.com on 23 Dec 2009 at 6:52

• Changed state: WontFix