Mirrored CBI TPD tool and eclipse collections to simantics.org

[simantics/platform.git] / releng / org.simantics.sdk.build.targetdefinition / README.md

diff --git a/releng/org.simantics.sdk.build.targetdefinition/README.md b/releng/org.simantics.sdk.build.targetdefinition/README.md
index f5b19fd7381fe0d49640efdfebb3c535d38b70ff..4b1730d71e06981d1219cee40409d653e0690a18 100644 (file)
--- a/releng/org.simantics.sdk.build.targetdefinition/README.md
+++ b/releng/org.simantics.sdk.build.targetdefinition/README.md
@@ -3,7 +3,9 @@
 Simantics 1.31.0 migrated to Eclipse 4.7 Oxygen platform.\r
 \r
 At the same time [Obeo's Target Platform Definition DSL and Generator tool](https://github.com/mbarbero/fr.obeo.releng.targetplatform)\r
-was taken into use for target platform definition.\r
+was taken into use for target platform definition. Later on the tool was moved to Eclipse\r
+CBI (Common Build Infrastructure) as [Target Platform Definition DSL and Generator](https://github.com/eclipse-cbi/targetplatform-dsl)\r
+which is what we are using right now.\r
 \r
 Please read the detailed installation and basic use instructions from the tool's website.\r
 \r
@@ -47,4 +49,11 @@ This greatly simplifies target definition by removing duplication from the their
 publishing them online per platform branch is also highly useful.\r
 \r
 On the other hand legacy Buckminster builds can source `.target` files from a URL, which is why publishing them online\r
-per platform branch is useful.
\ No newline at end of file
+per platform branch is useful.\r
+\r
+## Building .target files from the command line\r
+\r
+There is an example of how to do this with Maven at [build/pom.xml)(build/pom.xml).\r
+Essentially it sources the TPD tool and its required Eclipse parts from public P2\r
+repositories and uses `tycho-eclipserun-plugin` to run the *tpd converter application*\r
+to convert the `.tpd` file given as argument via `-Dtpd=tpd-path`.\r