Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "SWT/Devel/Gtk/Missing so file errors"
(Created page with "= Background = This article assumes you have built the SWT JNI bindings using [https://github.com/LeoUfimtsev/ldts/blob/master/pathscripts/swtjnibuild this script]. Even when...") |
|||
| Line 1: | Line 1: | ||
= Background = | = Background = | ||
| − | This article assumes you have built the SWT JNI bindings using [https://github.com/LeoUfimtsev/ldts/blob/master/pathscripts/swtjnibuild this script]. Even when using this script, | + | This article assumes you have built the SWT JNI bindings using [https://github.com/LeoUfimtsev/ldts/blob/master/pathscripts/swtjnibuild this script]. Even when using this script, launching a child Eclipse might give an error where the parent Eclipse complains about missing .so files, and then stops the launch. |
= Solution = | = Solution = | ||
Latest revision as of 14:35, 6 October 2015
Background
This article assumes you have built the SWT JNI bindings using this script. Even when using this script, launching a child Eclipse might give an error where the parent Eclipse complains about missing .so files, and then stops the launch.
Solution
Usually this means that you have forgotten to import the SWT binaries projects into your workspace/run configuration. To remedy this, clone the eclipse.platform.swt.binaries project into your gitroot. Import the projects into your Eclipse workspace.
You then need to ensure that Eclipse is launching a child Eclipse with those workspace binaries enabled at launch. These are the binaries that will be replaced by the ones generated with the SWT JNI script.
To enable this, execute the following steps:
- Go to Run Configurations
- Select your child Eclipse Run Configuration
- Click the Plug-ins tab and select "launch with plug-ins selected below only"
- From the list of workspace plug-ins, choose the Gtk binary that matches your OS and architecture (for example: org.eclipse.swt.gtk.linux.x86_64). Enabling this will allow your child Eclipse to run properly