miniconda is the main bootstrap for "conda", so that's why I prefer it.Anaconda, which is conda + a lot of extra utilities.Note: "conda" environment manager comes in two flavours: Suggested steps on how to reproduce conda buildĪ bit more info can be found on this blog post which started as an experiment.Īlso, I do not know how to accomplish the first three steps from a terminal, sorry! I tried a build from the current dev branch and it successfully completed after commenting these lines: I use conda to manage environments, so when building I use python from that environment instead of the "global" system one. I wonder if this is the reason why it's been working on my side. We weren't able to discover how to accommodate this new behavior in time for the release in common cases such as doing a build for a global python install. I have not played too much with it other than loading stages in USD View and a bit of USD API calls, though. I'm asking because I was able to build succesfully (it seems) USD 20.5 on Windows with Python-3.8 via conda and was keen on building again for 20.8 I see the build script references this python what's new entry:ĭid things change since 20.5 that will cause an issue now? or is the 20.5 release not expected to build properly on Windows with python 3.8 either? I was wondering what the changes compared to 20.5 are to make the build fail when attempting Windows + Python-3.8. Python 3.8 on Windows now causes an error, as USD does not support this version on Windows. I've just read that the changelog for the 20.8 release has this entry: Thanks for this amazing project! It's always exciting to see the upcoming release changelog.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |