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.
Tom
Pascal Rapicault
<Pascal_Rapicault
@ca.ibm.com> To
Sent by: Equinox development mailing list
equinox-dev-bounc <equinox-dev@eclipse.org>
[EMAIL PROTECTED] cc
Subject
09/11/2007 08:43 [equinox-dev] Launcher and
AM fragments
Please respond to
Equinox
development
mailing list
<[EMAIL PROTECTED]
pse.org>
Hello,
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
eclipse.exe".
PaScaL
_______________________________________________
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
<<inline: graycol.gif>>
<<inline: pic26003.gif>>
<<inline: ecblank.gif>>
_______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
