| Building Update Site with platform specific fragments [message #330477] |
Tue, 29 July 2008 21:07  |
Eclipse User |
|
|
|
Originally posted by: amir.nospam_pyrus.us
I have an Eclipse feature that consists of several plug-ins, one of
which contains native methods that makes use of Java Native Interface (JNI).
I have placed the pre-compiled native shared library for each supported
platform in a platform specific fragment that is included in the feature.
I would like to have an update site that contains fragments for all the
supported platforms. But when I issue the 'Build All' command in my
update site project, only the fragment matching the build system's
environment is built.
To get around this limitation, I have had to do the following manually:
- Build the update site on each supported platform individually
to get the JAR file for the platform specific fragment
- Collect the JAR files for platform specific fragments and
place them in the plugins folder on one of the update sites
(pick one platform)
- Unpack the feature's JAR file, and modify the feature.xml file to
replace 'version="0.0.0" for the unmatched fragments with one
that contains the correct version
All this seems a bit silly, since the platform specific binaries are
already compiled. I should be able to build for all platforms since all
the tool needs to do is to pack the JAR files and put the correct
fragment versions in the feature.xml file.
To make matters worst, the 3.4 version of eclipse produces two new files
in the update site: content.xml and artifacts.xml
Manually updating these files to add the platform specific fragments is
not something I want to do every time I build for my update site.
Is there a solution to this problem? Is there a way to force the build
of platform specific fragments that do not match the build system's
environment?
I have seen discussions relating to to this topic on this forum before,
but I have not seen a workable solution.
I would appreciate any help in this regard.
Thanks.
Amir
|
|
|
| Re: Building Update Site with platform specific fragments [message #330513 is a reply to message #330477] |
Wed, 30 July 2008 18:53  |
| Eclipse User |
|
|
|
Originally posted by: zx.code9.com
Amir Kouchekinia wrote:
>
>
> I have an Eclipse feature that consists of several plug-ins, one of
> which contains native methods that makes use of Java Native Interface
> (JNI).
>
> I have placed the pre-compiled native shared library for each supported
> platform in a platform specific fragment that is included in the feature.
>
> I would like to have an update site that contains fragments for all the
> supported platforms. But when I issue the 'Build All' command in my
> update site project, only the fragment matching the build system's
> environment is built.
>
> To get around this limitation, I have had to do the following manually:
>
> - Build the update site on each supported platform individually
> to get the JAR file for the platform specific fragment
> - Collect the JAR files for platform specific fragments and
> place them in the plugins folder on one of the update sites
> (pick one platform)
> - Unpack the feature's JAR file, and modify the feature.xml file to
> replace 'version="0.0.0" for the unmatched fragments with one
> that contains the correct version
>
> All this seems a bit silly, since the platform specific binaries are
> already compiled. I should be able to build for all platforms since all
> the tool needs to do is to pack the JAR files and put the correct
> fragment versions in the feature.xml file.
>
> To make matters worst, the 3.4 version of eclipse produces two new files
> in the update site: content.xml and artifacts.xml
> Manually updating these files to add the platform specific fragments is
> not something I want to do every time I build for my update site.
>
> Is there a solution to this problem? Is there a way to force the build
> of platform specific fragments that do not match the build system's
> environment?
>
> I have seen discussions relating to to this topic on this forum before,
> but I have not seen a workable solution.
Check out this bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=196556
Cheers,
~ Chris
|
|
|
Powered by
FUDForum. Page generated in 0.03314 seconds
] 
Search
Help
Register
Login
Home
