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

Allow user to specify boost version #347

Closed
wants to merge 3 commits into from
Closed

Allow user to specify boost version #347

wants to merge 3 commits into from

Conversation

meshula
Copy link
Member

@meshula meshula commented Dec 10, 2017

Description of Change(s)

I'm using boost 1.65.1, and like the convenience of using the standard build script. This modification doesn't change the default behavior, but if boost version is specified on the command line, USD will build with the specified version.

Also handles toolset version for VS2015 and VS2017, because boost 1.65.1 insists on toolset 141 for VS2017.

OpenImageIO 1.7.17 is the minimum compatible with boost 1.65.1

Fixes Issue(s)

build script is hard coded to boost 1.61 and using the 140 toolset with VS2015 and VS2017

@jtran56
Copy link

jtran56 commented Dec 13, 2017

Filed as internal issue #154998.

if Windows():
# .0 versions of boost don't end in _0.
boost_version = "_".join(context.boost.split("."))
if boost_version[-2:] == ".0":
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo - this should be == "_0":

@sunyab
Copy link
Contributor

sunyab commented Mar 31, 2020

We'd prefer to keep build_usd.py to a curated set of dependencies for easier testing and validation, especially given the relationships between dependencies like the one between boost and OpenImageIO identified in this PR. This sort of customization (even at an "at-your-own-risk" level) opens us up to more support load; if users want to use different versions they can edit the build script locally, which should make it clear they're in unguarded waters. :)

So, I'm going to close this PR out. Thanks!

@sunyab sunyab closed this Mar 31, 2020
@meshula
Copy link
Member Author

meshula commented Mar 31, 2020

Makes sense to me, the curated build environment today works for me very well in all the configurations I'm dealing with!

AdamFelt pushed a commit to autodesk-forks/USD that referenced this pull request Apr 16, 2024
…lve/adsk/internal-only/feature/depth-priority

OGSMOD-2801: Merge depth priority fix into adsk/dev
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants