Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-swt-dev] Deploying a single cross platform SWT


See https://bugs.eclipse.org/bugs/show_bug.cgi?id=292062 for progress on number 1).

I believe one could use the Eclipse RCP Delta Packs to implement 3).  In which case, 1) is not that important anymore as the Eclipse bundles already expose those attributes (Eclipse-PlatformFilter).

Silenio


From: Silenio Quarti/Ottawa/IBM@IBMCA
To: "Eclipse Platform SWT component developers list." <platform-swt-dev@xxxxxxxxxxx>
Date: 04/27/2011 06:33 PM
Subject: Re: [platform-swt-dev] Deploying a single cross platform SWT
Sent by: platform-swt-dev-bounces@xxxxxxxxxxx






I opened this bug to add your info to the SWT FAQ. It should get done by next week.


https://bugs.eclipse.org/bugs/show_bug.cgi?id=344049

I believe we can do 1) as well in the short term. I am assuming you are talking about the stand alone SWT jars (because the SWT jars that are part of the Eclipse build already have this info). The manifest we add to the stand alone jar is auto generated by the ant JAR task and is not very useful.  It should not take too long to get this done.


Silenio



From: Martin Hare Robertson <mchr3k@xxxxxxxxx>
To: "platform-swt-dev@xxxxxxxxxxx" <platform-swt-dev@xxxxxxxxxxx>
Date: 04/27/2011 12:33 PM
Subject: Re: [platform-swt-dev] Deploying a single cross platform SWT
Sent by: platform-swt-dev-bounces@xxxxxxxxxxx






In the short term linking to my SO answer or duplicating the content
in the SWT FAQ would allow existing users to deploy multiple platform,
single jar SWT apps.

Longer term, there are three things which would be nice to see.

1) SWT build updated to tag the per platform jars with a string
defining which platform they apply to. This could be done with a new
Manifest attribute and strings such as "win32" or "osx64".

2) The code described in my SO answer should be cleaned up and added
to something like the "One-Jar" tool. The aim would be to create an
ant task which could build a jar with any number of SWT jars
referenced. The bootstrap class would load the manifest for all the
included jars and attempt to find an appropriate SWT jar for the
current platform.

3) Eclipse should be updated to support the new SWT enabled "One-Jar"
tool. This would involve updating the export jar wizard to support a
new "Export SWT UI jar" mode and would allow the user to select all
the SWT jars they want to include. Ideally Eclipse would ship with a
full set of SWT jars for the user to pick from.

> Date: Tue, 26 Apr 2011 22:29:41 +0200
> From: Christopher Deckers <chrriis@xxxxxxxxx>
> To: "Eclipse Platform SWT component developers list."
>         <platform-swt-dev@xxxxxxxxxxx>
> Subject: Re: [platform-swt-dev] Deploying a single cross platform SWT
>         Jar
> Message-ID: <BANLkTi=hMvaMEroJUF3gF7SbfCPe7neYVg@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1
>
>> I would like to propose a new Q&A to be added to the SWT FAQ
>> (
http://www.eclipse.org/swt/faq.php).
>
> I am sure this approach would help many users of my library, so this
> is a step in the right direction.
>
>> In this stackoverflow discussion
>> (
http://stackoverflow.com/questions/2706222/create-cross-platform-java-swt-application/5784073#5784073)
>> I present an approach which produces a single jar packaging up the SWT jars
>> for a number of platforms and which loads the correct one at runtime.
>
> I would love to have this approach combined with a dynamic way of
> knowing which port is applicable rather than forging the names of the
> resources to load. cf:
>
https://bugs.eclipse.org/bugs/show_bug.cgi?id=292062
>
> -Christopher
>
>
_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx

https://dev.eclipse.org/mailman/listinfo/platform-swt-dev

_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-swt-dev



Back to the top