[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Launcher and fragments

Both the eclipse.exe and the equinox.launcher bundle may load the native library in launcher.<os>.<ws>.<arch>. For example when launching self-hosting, the eclipse.exe is not used. In this case the equinox.launcher java code loads the shared library. Currently there is no eclipse.exe bundle, that left us with the equinox.launcher bundle for the host of the shared library fragments. We could create an equinox.executable host bundle but I'm not sure what the motivation would be for that since it would be an empty host that does nothing other than allow the native code fragment bundles to resolve.


Inactive hide details for Pascal Rapicault ---09/11/2007 08:47:29 AM---Hello,Pascal Rapicault ---09/11/2007 08:47:29 AM---Hello,

          Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>
          Sent by: equinox-dev-bounces@xxxxxxxxxxx

          09/11/2007 08:43 AM

          Please respond to
          Equinox development mailing list <equinox-dev@xxxxxxxxxxx>


Equinox development mailing list <equinox-dev@xxxxxxxxxxx>



[equinox-dev] Launcher and fragments


I'm questioning why the launcher.<os>.<ws>.<arch> bundles are fragments of
the launcher bundle?
If I remember correctly the launcher fragments result from the
reorganization of the eclipse.exe where we tried to make the exe as small
as possible. Therefore it seems to me that the declaration of the platform
specific launcher bundles as fragment of the launcher.jar (formerly
startup.jar) is abusive. However I found weird that we did without a
precise motive. Does anyone remember it?

For me, the platform specific launchers should be "fragment to the


equinox-dev mailing list

GIF image

GIF image

GIF image