-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
mayaplugin: maya 2018 needs namespace #265
Comments
Filed as internal issue #149756. |
Thanks for the hint, @takahito-tejima For us the compiler was not quite happy until we did this:
At least in the current devkit their namespace header does declare all classes with the proper namespaces. This seems to be the preferred way according to the docs: In case someone is doing the build and has issues with Ptex:
We do not have matching headers and since it probably is not a version usd expects we ended up rebuilding Ptex statically with -fPIC and linking the maya variant against the static lib. Other then this pxrUsd seems to run fine. Hope someone might find this helpful. |
Thanks for taking care. I would like to add some info to Ptex issue: It seems that the v2_2 namespace was introduced with Ptex 2.1.28. So as long as usd can be build with Ptex 2.1.28 you will be able to use Maya's PTex library. |
Commit af3c97b was just released in USD 0.8.1, closing this out. Thanks! |
Description of Issue
since maya 2018, OpenMaya API classes have a namespace prefixed such as OpenMaya20180000::MFnMesh
which results in a build error when compiling maya plugin.
Steps to Reproduce
System Information (OS, Hardware)
windows, linux
Package Versions
Build Flags
--maya
modifying forward declarations in usdMaya/meshUtil.h as
#include <maya/MTypes.h>
#if MAYA_API_VERSION >= 20180000
OPENMAYA_MAJOR_NAMESPACE_BEGIN
class MFnMesh;
class MString;
OPENMAYA_NAMESPACE_CLOSE
#else
class MFnMesh;
class MString;
#endif
fixes for me.
thanks!
The text was updated successfully, but these errors were encountered: