Building MPS language plugins

Skip to end of metadata
Go to start of metadata

Distributing languages as plugins for MPS is very similar to packaging languages for IntelliJ IDEA.You follow the same instructions described in Building IntelliJ IDEA language plugins with two important differences:

  1. Your build script should depend on mps as you can see in the attached screen-shot.

    Additionally, by depending on mps your languages can leverage the whole MPS infrastructure and the whole set of languages, while mpsPlugin restricts IDEA plugins to only the subset of functionality that is available in IntelliJ IDEA.
  2. When running your Ant build script from the command line, you set an artifacts.mps property (instead of artifacts.mpsPlugin) and make it point to an MPS installation home directory.

    Note: Since in the example build script above we set the artifacts location for mps to $mps_home, we may set -Dmps_home instead (necessary only if the MPS location on the build machine differs from the path set in the build script).

The generated plugin can then be imported into MPS. You can install the plugin either manually or through the MPS plugin manager. If installing manually, the downloaded plugin zip file must be unzipped into the MPS plugin folder.

  • Windows and Linux: typically USER_HOME/MPS_version/config/plugins or MPS_HOME/plugins
  • MacOS: ~/Library/Application Support/MPS_version/ or MPS_HOME/plugins

After restart the imported languages will become available in MPS.

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.