Re: [cbi-dev] [tycho-user] Merging CBI into Platform progress

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

I am not 100% sure, but I think you confirmed that P2 should handle
eclipsec.exe, but it does not and therefor PDE/Build has to provide a
workaround. So instead of code the same/similar workaround on Tycho, I
think the right solution is to implement proper eclipsec.exe support in
P2, where it belongs.

If Platform team is reluctant to make this P2 change for some reason, I
can investigate alternative solutions. I don't know what this solution
might be yet, but I most likely it won't be one-to-one reimplementation
of PDE logic.

Andrew, is this something you consider critical for CBI 1.0?

--
Regards,
Igor

On 12-09-18 1:17 PM, Paul Webster wrote:
> On Tue, Sep 18, 2012 at 1:01 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx
> <mailto:igor@xxxxxxxxxxxxxx>> wrote:
>
>     Tycho delegates most of the work to assemble RCP applications to P2
>     director.
>
>      From what I remember, this is controlled with includeLaunchers .product
>     attribute and P2 director knows how to include proper launcher for the
>     selected target environment.
>
>     Is there a flag we can pass to P2 director to include both eclipse.exe
>     and eclipsec.exe for win32 platforms?
>
>
> No, that's not currently done via p2 for eclipsec.exe.  I believe that
> PDE build is using the root.* to generate root file IUs that just allow
> eclipsec.exe (and for the equinox.executable feature, the other root.*
> files like libcairo-swt.so for gtk/linux/x86_64) and including a filter:
>
> root.linux.gtk.x86_64=bin/gtk/linux/x86_64,gtk_root ->
>        <filter>
>          (&amp;(osgi.arch=x86_64)(osgi.os=linux)(osgi.ws
> <http://osgi.ws>=gtk))
>        </filter>
>
> PW
>
>
> --
> Paul Webster
> Hi floor.  Make me a sammich! - GIR
>
>
> _______________________________________________
> cbi-dev mailing list
> cbi-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cbi-dev