Problems with custom MPS build
Hello,
I'm using MPS 2.0.1 and trying to create the custom MPS build for my language.
I've created "Custom MPS Build Script" according to the user guide, selected buildTools.zip. The first issue is here:
Error marker is here: "Error: Path to MPS-buildTools.zip is not valid".
Okay, I've copied it to my project directory and specified
Next step: Run->Edit Configurations, added Ant->Custom MPS Application, specified Name and build script. Than I've run it.
Build failed after (during) target "macos.dist":
However some artifacts were created: MPS folder, Info.plist, MPS-20.7609.zip and MPS-20.7609-linux.tar.gz.
I've tried to unpack the MPS-20.7609.zip and run it. There are two files with the same names in the archive: "MPS 2.0/bin/mps.exe.vmoptions". It's allowed for archive, but confusing when being unpacked.
Finally I've run mps.bat and nothing's happened.
BTW, I'm running on MS Win7.
Can anybody help me?
Thanks,
Alexey
I'm using MPS 2.0.1 and trying to create the custom MPS build for my language.
I've created "Custom MPS Build Script" according to the user guide, selected buildTools.zip. The first issue is here:
build tools no macro/E:/Distr/.../MPS-2.0.1-buildTools.zip
Error marker is here: "Error: Path to MPS-buildTools.zip is not valid".
Okay, I've copied it to my project directory and specified
base_dir/MPS-2.0.1-buildTools.zip
Next step: Run->Edit Configurations, added Ant->Custom MPS Application, specified Name and build script. Than I've run it.
Build failed after (during) target "macos.dist":
macos.dist: [copy] Copying 1 file to .../artifacts BUILD FAILED C:\Users\<...the rest of the base dir...>\build\ProjectName-default-dist.xml:15: The following error occured while executing this line: C:\Users\<...the rest of the base dir...>\build\ProjectName-default-dist.xml:93: <...base_dir...>\build\${build_tools}\resources does not exist.
However some artifacts were created: MPS folder, Info.plist, MPS-20.7609.zip and MPS-20.7609-linux.tar.gz.
I've tried to unpack the MPS-20.7609.zip and run it. There are two files with the same names in the archive: "MPS 2.0/bin/mps.exe.vmoptions". It's allowed for archive, but confusing when being unpacked.
Finally I've run mps.bat and nothing's happened.
BTW, I'm running on MS Win7.
Can anybody help me?
Thanks,
Alexey
Please sign in to leave a comment.
1. create a path variable projectname_home -> /local/path/to/project
2. click on the Project -> New -> Build Script
3. rebuild created solution
On a build server:
cd /path/to/project/build
ant -f ProjectName-default.xml -Dmps_home=/path/to/MPS
-Dprojectname_home=/path/to/project
Path variables are used to avoid absolute paths within the project files.
My current goal is not to build my language, but create a custom MPS application for my language. So I use the custom application build script. Build still failed, but artifacts folder contains some MPS application. This application contains MyLanuage/MyLanguage.jar, but there are two troubles with it. It's about 350Mb (as original MPS, I expected that custom build should be smaller) and I can't run it (the javaw process has started indeed, but there is no application window).
1. create a Build Script, build all your languages
2. in the same root where you list all the languages to build, create a branding.jar definition. Specify the name of your IDE, all the icons, splash screen, about and welcome images.
3. regenerate and execute build script to get your own branding.jar archive
4. create minified versions of MPS for all required platforms: delete unnecessary languages and plug-ins (because of the dependencies you cannot delete all the languages, but /languages/util folder can be deleted for sure)
5. replace lib/branding.jar in each minified MPS with your own archive
6. create a plug-in containing your languages
/plugins/
/myLanguagesPlugin/
/languages
lang1.jar
lang1-src.jar (language sources are required yet)
lang2.jar
.....
/META-INF
plugin.xml (see below)
7. put the plug-in into each distribution
Here is the simplest content for plugin.xml, contributing languages folder as a library:
You have to unpack the archive, delete languages from the languages folder (respecting the dependencies) and delete unnecessary stuff from the plugins folder.