Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need to bundle boost tr1/tuple #7

Closed
GoogleCodeExporter opened this issue Jun 25, 2015 · 4 comments
Closed

Need to bundle boost tr1/tuple #7

GoogleCodeExporter opened this issue Jun 25, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

Chandler Carruth wrote:

"This might actually feasible, and solves the problem below as well --
why don't we provide our own TR1 in the same manner as we provide
gtest? Specifically we could have the following preference:

 1) look for a compiler provided tr1
 2) look for a system installed boost
 2b) (I don't actually think this would be needed) expose a flag
indicating "boost is over here"
 3) add include paths which point into an internal snapshot of (for
instance) the boost tr1, potentially configuring gmock to #include it
out of an internal directory, so that once installed, it'll never be
used by some other project."

We can use bcp (http://www.boost.org/doc/libs/1_36_0/tools/bcp/bcp.html) to 
extract the subset of Boost needed by tr1/tuple, which can significantly 
reduce the size of boost files.

Original issue reported on code.google.com by shiq...@gmail.com on 16 Dec 2008 at 8:55

@GoogleCodeExporter
Copy link
Author

Not sure if we still want to bundle tr1/tuple now that it's a convenient 
download on
googlemock's server.  What do you think, Chandler?

Re-prioritizing it to low for now.

Original comment by zhanyong...@gmail.com on 14 Jan 2009 at 9:42

  • Changed state: Fixed
  • Added labels: Priority-Low
  • Removed labels: Priority-High

@GoogleCodeExporter
Copy link
Author

Original comment by zhanyong...@gmail.com on 14 Jan 2009 at 9:43

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

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

  • Added labels: Usability

@GoogleCodeExporter
Copy link
Author

This becomes obsolete now that we have our own tr1 tuple implementation.

Original comment by zhanyong...@gmail.com on 17 Jun 2009 at 11:17

  • Changed state: WontFix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant