-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Can we eliminate the use of boost shared pointers? (BOOST_SP_USE_STD_ATOMIC problem) #170
Comments
Filed as internal issue #143729. |
I have a branch that seems to do this. It is currently, without all of the requisite cleanup, modifying about 170 files. To avoid repeatedly rebasing this ... is there a good time to submit it as a pull request? |
I just wanted to check in and say that this is still an issue. |
waywardmonkeys
added a commit
to waywardmonkeys/USD
that referenced
this issue
Feb 1, 2018
This converts from using `boost::shared_ptr` and friends (like `weak_ptr`) over to using the `std` equivalents. Fixes issue PixarAnimationStudios#170.
@meshula @jesschimein I think this issue can be closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is a difficult USD configuration issue around the use of boost shared pointers.
This flag
exists as a preprocessor directive, and it is impossible to tell if a compiled version of boost was made with it set to 1 or not.
If you are trying to build USD against a supplied version of boost, instead of one built specifically for USD, it's extremely difficult to narrow the issues down to this flag, and then to work out how to set it.
I would request that we don't use boost shared pointers at all, since for the most part the functionality is covered by std or tbb.
The text was updated successfully, but these errors were encountered: