Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cbi-dev] Building 3.8 stream

Hi Andrey,

My responses inline.


Thanh


On 07/06/2012 10:09 AM, Andrey Loskutov wrote:
There are few plugins deployed as directories in the "eclipse.org" build which were now deployed as jars:

"3.8 from eclipse.org":

org.eclipse.core.runtime.compatibility.registry_3.5.100.v20120521-2346
org.eclipse.platform_3.8.0.v201206081200
org.eclipse.sdk_3.8.0.v201206081200
org.eclipse.ui.intro.universal_3.2.600.v20120521-2344
org.eclipse.ui.workbench.compatibility_3.2.101.v20120523-1956

"3.8 custom":
org.eclipse.core.runtime.compatibility_3.2.200.201207061258.jar
org.eclipse.platform_3.8.0.201207061258.jar
org.eclipse.sdk_3.8.0.201207061258.jar
org.eclipse.ui.intro.universal_3.2.600.201207061258.jar
org.eclipse.ui.workbench.compatibility_3.2.101.201207061258.jar
I'm not positive but I think to fix these we need to add

  Eclipse-BundleShape: dir

to the MANIFEST.MF files.

Igor, Paul can either of you confirm?

Second, it looks like SWT build is not optimal yet: AFAIK SWT maintains their own very special build and version schema, and so the generated jar has wrong version/content (see attached picture):

"3.8 from eclipse.org":
org.eclipse.swt_3.8.0.v3833.jar 18 KB

"3.8 custom":
org.eclipse.swt_3.8.0.201207061258.jar 7.2 MB

However this seems not break the UI (after quick smoke test).
I'm not familiar with how this is built maybe someone form the platform team can comment or maybe Krzysztof knows?

And last one: even if I specified to re-build swt native binaries on Linux 64 gtk, they still contain parts built on eclipse.org:

libcairo-swt.so
libswt-mozilla-gtk-3833.so
libswt-xpcominit-gtk-3833.so
libswt-xulrunner-fix.so
libswt-xulrunner-gtk-3833.so

I guess there are some preconditions for the build (like xulrunner/mozilla SDK installed) which are not considered by the maven build. I wonder if this can/should be manual step before the build, or can be done by maven downloading those SDK's to the build area.
I think your correct, we had to modify the build.xml for the linux natives to disable xulrunner per commit [1].

Krzysztof worked on this area so I hope he can provide more details.



[1] http://git.eclipse.org/c/cbi/eclipse.platform.swt.binaries.git/diff/bundles/org.eclipse.swt.gtk.linux.x86_64/build.xml?h=Juno_RC4_R4&id=b62729b030fc0696920dd4c80e142d29248129c0

Back to the top