Difference between revisions of "Target Platform"
Jump to navigation
Jump to search
Line 37: | Line 37: | ||
#** '''Members:''' Select '''Simantics SDK 1.6''' for source code access instead. Use the SVN credentials available in the members wiki when Eclipse asks for the credentials to the target platform. | #** '''Members:''' Select '''Simantics SDK 1.6''' for source code access instead. Use the SVN credentials available in the members wiki when Eclipse asks for the credentials to the target platform. | ||
#** This will make Eclipse download the target platform components from '''simantics.org''' and install them as your target platform. | #** This will make Eclipse download the target platform components from '''simantics.org''' and install them as your target platform. | ||
− | #** If your internet access has an HTTP proxy that causes problems while downloading, try using ''Simantics 1. | + | #** If your internet access has an HTTP proxy that causes problems while downloading, try using ''Simantics 1.6 (HTTPS)''. |
− | |||
# '''Keep your platform up-to-date''' | # '''Keep your platform up-to-date''' | ||
#* Updating is as easy as reloading the target platform from Target Platform preference page. Select your target from the list and then press the '''Reload''' button. | #* Updating is as easy as reloading the target platform from Target Platform preference page. Select your target from the list and then press the '''Reload''' button. |
Revision as of 19:32, 7 June 2012
The target platform is a composition of OSGi bundles, i.e. Eclipse plug-ins and features. This is the platform on top of which Simantics and its applications are developed. It consists roughly of:
Contents
Maintenance
Simantics target platform maintainer is Tuukka Lehtonen.
See Deploying plug-ins for the target platform for instructions on contributing to the target platform.
P2 deployments
P2 is a technology for provisioning software components for OSGi applications (e.g. anything Eclipse-based) originating from the Eclipse/Equinox project.
Register to access source code
Simantics is an open source software platform, licensed under Eclipse Public License EPL (more information in section Licensing). The source code for both semantic database engine Simantics Core and the client Simantics Workbench is available to registered users. To gain access to the complete Simantics SDK source code, go to the Simantics Members Wiki and request an account.
Simantics 1.6
- Get the target platform definitions
- Installing without SVN (recommended approach)
- Select menu item File/New/Project to create a new empty project.
- Download the following files and copy them into the new project:
- For members, source code access is available through these alternative target definitions:
- Installing through SVN
- Checkout svn:target/branches/1.6 project from the Simantics SVN into your workspace.
- Installing without SVN (recommended approach)
- Activate the target platform
- Select menu item Window/Preferences from your Eclipse IDE.
- Open the preference page Plug-in Development/Target Platform.
- Activate the Simantics 1.6 target platform definition by checking it and pressing Apply. Wait until Eclipse finishes downloading. Press OK.
- Members: Select Simantics SDK 1.6 for source code access instead. Use the SVN credentials available in the members wiki when Eclipse asks for the credentials to the target platform.
- This will make Eclipse download the target platform components from simantics.org and install them as your target platform.
- If your internet access has an HTTP proxy that causes problems while downloading, try using Simantics 1.6 (HTTPS).
- Keep your platform up-to-date
- Updating is as easy as reloading the target platform from Target Platform preference page. Select your target from the list and then press the Reload button.
Simantics TRUNK (head)
Same instructions apply as for #Simantics 1.5 with the following changes:
- Download the following files and copy them into the new project:
or
- Checkout svn:target/branches/head project from the Simantics SVN into your workspace.
The same procedure applies for Stable Branch also, just use svn:target/branches/stable.