| PDE-build with target platform [message #7146] |
Wed, 18 June 2008 05:27  |
Eclipse User |
|
|
|
How do I have to configure an automated PDE build (e.g. build.properties)
so that the build uses a given target platform?
In my current configuration the PDE build uses the platform for building
also as target platform.
I'd like to separate these two to have one platform (say eclipse 3.4) for
the PDE build. Then I'd like to use the PDE of this eclipse 3.4
installation to build a product against a different target platform (say
eclipse 3.3).
Thanks.
|
|
|
|
| Re: PDE-build with target platform [message #7287 is a reply to message #7194] |
Fri, 20 June 2008 11:34  |
| Eclipse User |
|
|
|
Originally posted by: breadlord.gmail.com
I've just built one of these...
In order to build the Target platform you need to get the RCP binary
pack for the platform you're running on and the delta pack - both from
the version you want to compile against. The only thing that the eclipse
IDE install is used for is running the PDE Build application.
You unzip both of the above into the same directory - it should look
like a massively cutdown version of eclipse. If your app uses some more
plugins you're going to have to add them to the plugins directory you've
just created.
In the build.properties set baselocation to be the directory just above
this one.
Try looking at:
http://rcpquickstart.com/2007/06/06/getting-started-with-pde -build/ for
an example and instructions
Tom
Andrew Niefer wrote:
> In the workbench PDE/UI does this with in the preferences:
> Plug-in Development -> Target Platform.
>
> When doing this in an automated PDE/Build, set the "baseLocation"
> property to point at your target platform.
> Generally speaking, in a headless build there are the following
> locations, all of which are independent of the version of eclipse that
> is actually running the build:
> baseLocation : generally pre-compiled binaries. ie target platform
> buildDirectory : generally the source for bundles being compiled
> pluginPath : a list of additional places to find (generally binary)
> bundles.
>
> -Andrew
> Oliver wrote:
>> How do I have to configure an automated PDE build (e.g.
>> build.properties) so that the build uses a given target platform?
>> In my current configuration the PDE build uses the platform for
>> building also as target platform.
>> I'd like to separate these two to have one platform (say eclipse 3.4)
>> for the PDE build. Then I'd like to use the PDE of this eclipse 3.4
>> installation to build a product against a different target platform
>> (say eclipse 3.3).
>>
>> Thanks.
>>
|
|
|
| Re: PDE-build with target platform [message #569340 is a reply to message #7146] |
Thu, 19 June 2008 15:53 |
| Eclipse User |
|
|
|
In the workbench PDE/UI does this with in the preferences:
Plug-in Development -> Target Platform.
When doing this in an automated PDE/Build, set the "baseLocation"
property to point at your target platform.
Generally speaking, in a headless build there are the following
locations, all of which are independent of the version of eclipse that
is actually running the build:
baseLocation : generally pre-compiled binaries. ie target platform
buildDirectory : generally the source for bundles being compiled
pluginPath : a list of additional places to find (generally binary) bundles.
-Andrew
Oliver wrote:
> How do I have to configure an automated PDE build (e.g.
> build.properties) so that the build uses a given target platform?
> In my current configuration the PDE build uses the platform for building
> also as target platform.
> I'd like to separate these two to have one platform (say eclipse 3.4)
> for the PDE build. Then I'd like to use the PDE of this eclipse 3.4
> installation to build a product against a different target platform (say
> eclipse 3.3).
>
> Thanks.
>
|
|
|
| Re: PDE-build with target platform [message #569501 is a reply to message #7194] |
Fri, 20 June 2008 11:34 |
| Eclipse User |
|
|
|
Originally posted by: breadlord.gmail.com
I've just built one of these...
In order to build the Target platform you need to get the RCP binary
pack for the platform you're running on and the delta pack - both from
the version you want to compile against. The only thing that the eclipse
IDE install is used for is running the PDE Build application.
You unzip both of the above into the same directory - it should look
like a massively cutdown version of eclipse. If your app uses some more
plugins you're going to have to add them to the plugins directory you've
just created.
In the build.properties set baselocation to be the directory just above
this one.
Try looking at:
http://rcpquickstart.com/2007/06/06/getting-started-with-pde -build/ for
an example and instructions
Tom
Andrew Niefer wrote:
> In the workbench PDE/UI does this with in the preferences:
> Plug-in Development -> Target Platform.
>
> When doing this in an automated PDE/Build, set the "baseLocation"
> property to point at your target platform.
> Generally speaking, in a headless build there are the following
> locations, all of which are independent of the version of eclipse that
> is actually running the build:
> baseLocation : generally pre-compiled binaries. ie target platform
> buildDirectory : generally the source for bundles being compiled
> pluginPath : a list of additional places to find (generally binary)
> bundles.
>
> -Andrew
> Oliver wrote:
>> How do I have to configure an automated PDE build (e.g.
>> build.properties) so that the build uses a given target platform?
>> In my current configuration the PDE build uses the platform for
>> building also as target platform.
>> I'd like to separate these two to have one platform (say eclipse 3.4)
>> for the PDE build. Then I'd like to use the PDE of this eclipse 3.4
>> installation to build a product against a different target platform
>> (say eclipse 3.3).
>>
>> Thanks.
>>
|
|
|
Powered by
FUDForum. Page generated in 0.06439 seconds
Home