Packaging Overview
Meco™ uses packages to provide scripts, plug-ins, applications and more. A package essentially is a folder structure, which contains source code, additional files and images, which builds a environment whether it's for development, testing or production.
However, with the provided comprehensive Meco™ Package API, a package in Meco™ is more than a folder structure. You can customize packages, the way it would fit in your production pipeline and operate on them easily. Transitioning a tool, plug-in or an application from one system to Meco™, or other way around is straightforward since Meco™ uses environment variables to operate.
Please check mMecoPackage built-in package documentation for more information.
Built-in Python Modules & Files
When you create a Meco™ package by provided command or the API, the folder structure you see blow along with additional files are created automatically. The folders and files are provided to you right out of the bat for consistency and speed up your development work.
Name | Description |
---|---|
packageEnvLib.py | Package based environment customizations and initialization |
packageInfoLib.py | Information about the package |
.gitignore | Git ignore file of the package |
README.md | Readme file of the package |
Folder and File Structure
A typical folder and file structure of a Meco™ package is given below.
PACKAGE_NAME
- bin (Executable folder for each platform)
- darwin
- linux
- windows
- build (Build files)
- darwin
- linux
- windows
- config (Configuration files)
- data (Data files)
- doc (Data files)
- developer
- cppAPIReference
- pythonAPIReference
- reference
- user
- reference
- developer
- houdini
- katana
- lib
- darwin
- linux
- windows
- mari
- maya
VERSION
- mel
- plugin
- darwin
- linux
- windows
- python
- shelves
- xbm
- nuke
- python
PACKAGE_NAME
- tests
- resources
- files
- icons
- source
- cpp
- doc
- developer
- reference
- user
- reference
- developer
- temp
- test
- .gitignore
- README.md
- bin (Executable folder for each platform)