|
| Re: How to do a platform agnostic build [message #540469 is a reply to message #539866] |
Wed, 16 June 2010 09:22  |
 Peter Kullmann
Messages: 240
Registered: July 2009 |
Senior Member |
|
|
After a few experiments I think that it is not possible to create a
build without native launcher artifacts. This is not really a problem
because these artifacts do no harm. What I did was this: Add the
org.eclipse.equinox.executable feature to the site, create the site.p2
with target.os=* (ws=*,arch=*).
When installing with the director one can choose any setting for p2.os,
p2.ws and arch. Which one doesn't really matter (because there is no
platform specific code) but it must be a valid configuration. Certainly,
it makes sense to use the actual configuration for the target box.
Peter Kullmann schrieb:
> Hi,
>
> I'm trying out a buckminster build for our server-side products. For
> this I created a site-feature and am using the site.p2 action to build a
> p2 site. Everything is more or less working except for the platform
> specific stuff: My product configuration contains some special
> properties and specifies start levels but these settings are not there
> when I install the product from the site.
>
> To be more specific:
> 1. I launched site.p2 with the settings target.os=*, target.ws=* and
> target.arch=* because we have no platform dependent code. With these
> settings I'm getting the messages (for all platforms except my own):
> ...
> Missing executable launcher for configuration win32.win32.x86_64
> Missing executable launcher for configuration wpf.win32.x86
> Perhaps you should install the Platform Executable Launchers feature
> into your target platform
>
> The generated site contains my special configuration properties but only
> with a filter for my platform. I would like to see the configuration
> without any filter.
>
> 2. I tried to invoke site.p2 without any target.* properties. In this
> case it seems that it builds for my running platform (ie the
> configuration artifacts are available only for my platform).
>
> What should I set in the build to make sure the configuration artifacts
> are available on all platforms?
target.os=*, target.ws=*, target.arch=* and be sure to include the
org.eclipse.equinox.executable feature in the site or in a cspex.
>
> Why is site.p2 complaining about missing executable launchers? In the
> product configuration I have include native launchers set to false.
>
I think buckminster just ignores this setting.
> What do I have to set in the director call when installing a platform
> agnostic product?
Use a correct setting for the p2.os,p2.ws,p2.arch triple. Otherwise the
config.ini costumization are not installed.
>
> Thanks
> Peter
|
|
|
Powered by
FUDForum. Page generated in 0.03195 seconds
] 
Search
Help
Register
Login
Home
