[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cbi-dev] Bug 372794 CBI build of platform native SWT code
|
Hi Everyone,
I was running some tests this morning and I think I found a new issue.
Not with the patch per say but it seems to be with Tycho 0.16.0-SNAPSHOT
needed by the patch.
I discovered that if I erased my /var/tmp/lts/R4_localrepo directory and
reran the build fresh the following error appears. I was able to confirm
this issue by reverting the patches for the natives and running a build
without natives patches on both Tycho 0.15.0 and Tycho 0.16.0-SNAPSHOT.
When using 0.15.0 the build succeeds however if I build with
0.16.0-SNAPSHOT it fails with the error below.
I'm not sure if it's is due to a recent change in Tycho or not but I was
able to build successfully on Tycho 0.16.0-SNAPSHOT this morning before
I thought to try removing my /var/tmp/lts/R4_localrepo directory to make
sure we can build from a clean state.
Thanh
[INFO] org.eclipse.e4.rcp ................................ FAILURE [13.214s]
[ERROR] Failed to execute goal
org.eclipse.tycho.extras:tycho-source-feature-plugin:0.16.0-SNAPSHOT:source-feature
(source-feature) on project org.eclipse.e4.rcp: Could not generate
source feature for project MavenProject:
eclipse.platform.ui:org.eclipse.e4.rcp:1.1.0-SNAPSHOT @
/home/user/Downloads/eclipse2/R4_platform-aggregator/eclipse.platform.ui/features/org.eclipse.e4.rcp/pom.xml
[ERROR] Missing sources for plugins
[org.eclipse.e4.core.services_1.0.0.201206191524,
org.eclipse.e4.ui.workbench.swt_0.10.1.201206191524,
org.eclipse.e4.core.commands_0.10.1.201206191524,
org.eclipse.e4.ui.bindings_0.10.1.201206191524,
org.eclipse.e4.ui.model.workbench_0.10.1.201206191524,
org.eclipse.e4.ui.services_0.10.1.201206191524,
org.eclipse.e4.ui.workbench.renderers.swt_0.10.1.201206191524,
org.eclipse.e4.ui.workbench_0.10.2.201206191524,
org.eclipse.e4.ui.css.core_0.10.1.201206191524,
org.eclipse.e4.ui.css.swt_0.10.1.201206191524,
org.eclipse.e4.core.di_1.1.0.201206191524,
org.eclipse.e4.core.contexts_1.1.0.201206191524,
org.eclipse.e4.core.di.extensions_0.11.0.201206191524,
org.eclipse.e4.ui.css.swt.theme_0.9.2.201206191524,
org.eclipse.e4.ui.di_0.10.1.201206191524,
org.eclipse.e4.ui.widgets_0.12.0.201206191524,
org.eclipse.e4.ui.workbench.renderers.swt.cocoa_0.11.0.201206191524,
org.eclipse.equinox.common_3.6.100.201206191524,
org.eclipse.equinox.ds_1.4.0.201206191524,
org.eclipse.equinox.event_1.2.200.201206191524,
org.eclipse.core.commands_3.6.1.201206191524,
org.eclipse.core.contenttype_3.4.200.201206191524,
org.eclipse.core.databinding_1.4.1.201206191524,
org.eclipse.core.databinding.beans_1.2.200.201206191524,
org.eclipse.core.databinding.observable_1.4.1.201206191524,
org.eclipse.core.databinding.property_1.4.100.201206191524,
org.eclipse.core.expressions_3.4.400.201206191524,
org.eclipse.core.jobs_3.5.200.201206191524,
org.eclipse.core.runtime_3.8.0.201206191524,
org.eclipse.equinox.app_1.3.100.201206191524,
org.eclipse.equinox.preferences_3.5.0.201206191524,
org.eclipse.equinox.registry_3.5.200.201206191524,
org.eclipse.equinox.simpleconfigurator_1.0.300.201206191524,
org.eclipse.osgi_3.8.0.201206191524,
org.eclipse.osgi.services_3.3.100.201206191524,
org.eclipse.swt.win32.win32.x86_3.100.0.201206191524,
org.eclipse.swt.win32.win32.x86_64_3.100.0.201206191524,
org.eclipse.swt.gtk.linux.x86_3.100.0.201206191524,
org.eclipse.swt.gtk.linux.x86_64_3.100.0.201206191524,
org.eclipse.swt.cocoa.macosx.x86_64_3.100.0.201206191524,
org.eclipse.equinox.util_1.0.400.201206191524,
org.eclipse.jface_3.8.0.201206191524,
org.eclipse.jface.databinding_1.6.0.201206191524,
org.eclipse.e4.ui.workbench3_0.12.0.201206191524,
org.eclipse.equinox.console_1.0.0.201206191524,
org.eclipse.e4.ui.workbench.addons.swt_0.10.1.201206191524,
org.eclipse.equinox.bidi_0.9.0.201206191524]
[ERROR] -> [Help 1]
On 06/19/2012 02:59 AM, Krzysztof Daniel wrote:
On Mon, 2012-06-18 at 16:11 -0400, Andrew Ross wrote:
I'm going to defer to the experts to decide if the fix is an
appropriate fix... Igor, what do you think?
I know it looks like a hack, which it indeed is, because of the
following assumptions and limitations:
1. SWT must be still buildable as it is right now.
2. Tycho does not support ant build scripts.
3. Tycho is not compatible nor designed to work with maven-ant-runner.
4. Maven does not support building natives.
Unless Tycho starts supporting building natives and SWT conforms to
Tycho requirements in that area, I do not see any other way to get SWT
builds running.
