This is a boilerplate for creating Maya plugins in C++. You will find various CMake Find* files (from @chadmv who I can't recommend enough! He has great repositories and his blog is full of great content) for finding not only Maya's devkit but other common libraries such as GLEW and Kinect. I'm hoping to add more boilerplates for different types of plugins. The next step I'm looking at getting setup is a basic plugin that allows you to jump into development making DAG and Shape plugins.
- Maya
- Maya devkit
- CMake
- I recommend:
- Visual Studio / Visual Code or CLion for Windows
- Vim, CLion or Code::Blocks for *nix
- XCode or CLion for MacOS
Feel free to make pull requests or contact me on any social media platform @newyork167 if you think another CMake Find* file should be added or have any boilerplate additions that you feel would help make the base project better!
You will need to set the following variables in the CMakeLists.txt file
- MAYA_PLUGIN_OUTPUT_DIR => To a directory where you will load your custom Maya plugins. It is advised not to make this the plugins directory inside the Maya installation as the file/Maya can become corrupted
- MAYA_VERSION => Set this to the version of Maya you have installed and want to use the devkit of
-
For windows I suggest using either an IDE or the CMake GUI if you are new to CMake
-
For *nix you can run the following for an in-place build (files are built in the same directory):
cd maya-plugin-cmake-boilerplate ccmake . make
or you can make a build directory and have the files output there
cd maya-plugin-cmake-boilerplate mkdir build && cd build ccmake ../maya-plugin-cmake-boilerplate make
-
For MacOS you can use the GUI installed with brew
brew cask install cmake
(or if using port:port install cmake +gui
) and then build similar to *nixcd maya-plugin-cmake-boilerplate mkdir build && cd build cmake ../maya-plugin-cmake-boilerplate cmake --build .
I've learned so much through these individuals in the past few months (amongst many others that I'm not remembering at the moment of course!)
@chadmv for the CMake find files and amazing online info!
@KostasAAA / KostasAAA (Hopefully crediting the right github) for all his work on Twitter spreading information about graphics development.
Hugo Guerra who through my constant annoyance of questions still takes the time to answer them and for introducing me to the notion of pipeline technical director as a potential career. He also has great VFX content for both artists and developers.