Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » platform-independent target platform
platform-independent target platform [message #1116341] Wed, 25 September 2013 09:15 Go to next message
Carsten Reckord is currently offline Carsten Reckord
Messages: 17
Registered: June 2012
Junior Member
Hi,

I recently tried to update out Buckminster-based build chain from a somewhat
dusty 1.5.0 from around the Juno R0 release to the latest 1.6.0.

After that, we weren't able to build a platform-independent target platform
anymore. As far as I could figure out from the logs, the resolver still
included platform-specific bits for different platforms, i.e. I see

....
org.eclipse.swt.cocoa.macosx.x86_64:osgi.bundle/[3.102.1.v20130827-2048,3.102.1.v20130827-2048](&(target.arch=x86_64)(target.os=macosx)(target.ws=cocoa)):
Trying provider
p2(${p2.url.platform}[http://download.eclipse.org/releases/maintenance])
org.eclipse.swt.cocoa.macosx.x86_64:osgi.bundle/[3.102.1.v20130827-2048,3.102.1.v20130827-2048](&(target.arch=x86_64)(target.os=macosx)(target.ws=cocoa)):
Found match 3.102.1.v20130827-2048
org.eclipse.swt.cocoa.macosx.x86_64:osgi.bundle/[3.102.1.v20130827-2048,3.102.1.v20130827-2048](&(target.arch=x86_64)(target.os=macosx)(target.ws=cocoa)):
Using provider
p2(${p2.url.platform}[http://download.eclipse.org/releases/maintenance])
....

But after materialization has finished, only the Linux artifacts matching
the actual environment are found in the target platform.

The target platform definition is created with "setpref
targetPlatformPath=/some/path" in a clean workspace and we are using an
MSpec containing <md:property key="target.os" value="*"/> etc. entries that
references a CQuery without any target.* definitions. I also tried adding
properties to the command line as -D target.os=* ... but without effect.

I tried downgrading to the latest 1.5.0 release from around Juno SR2, but
had the same problem. So I'm back to our old version for now.

Has there been any change in how to request platform-independent
materialization?
Re: platform-independent target platform [message #1116358 is a reply to message #1116341] Wed, 25 September 2013 09:56 Go to previous message
Lorenzo Bettini is currently offline Lorenzo Bettini
Messages: 1356
Registered: July 2009
Senior Member
Hi

if I remember correctly there has been a similar problem in the past and
an easy way to solve it is to put

<cq:property key="target.arch" value="*"/>
<cq:property key="target.os" value="*"/>
<cq:property key="target.ws" value="*"/>

in the cquery...

hope this helps
Lorenzo

On 25/09/2013 11:15, Carsten Reckord wrote:
> Hi,
>
> I recently tried to update out Buckminster-based build chain from a somewhat
> dusty 1.5.0 from around the Juno R0 release to the latest 1.6.0.
>
> After that, we weren't able to build a platform-independent target platform
> anymore. As far as I could figure out from the logs, the resolver still
> included platform-specific bits for different platforms, i.e. I see
>
> ...
> org.eclipse.swt.cocoa.macosx.x86_64:osgi.bundle/[3.102.1.v20130827-2048,3.102.1.v20130827-2048](&(target.arch=x86_64)(target.os=macosx)(target.ws=cocoa)):
> Trying provider
> p2(${p2.url.platform}[http://download.eclipse.org/releases/maintenance])
> org.eclipse.swt.cocoa.macosx.x86_64:osgi.bundle/[3.102.1.v20130827-2048,3.102.1.v20130827-2048](&(target.arch=x86_64)(target.os=macosx)(target.ws=cocoa)):
> Found match 3.102.1.v20130827-2048
> org.eclipse.swt.cocoa.macosx.x86_64:osgi.bundle/[3.102.1.v20130827-2048,3.102.1.v20130827-2048](&(target.arch=x86_64)(target.os=macosx)(target.ws=cocoa)):
> Using provider
> p2(${p2.url.platform}[http://download.eclipse.org/releases/maintenance])
> ...
>
> But after materialization has finished, only the Linux artifacts matching
> the actual environment are found in the target platform.
>
> The target platform definition is created with "setpref
> targetPlatformPath=/some/path" in a clean workspace and we are using an
> MSpec containing <md:property key="target.os" value="*"/> etc. entries that
> references a CQuery without any target.* definitions. I also tried adding
> properties to the command line as -D target.os=* ... but without effect.
>
> I tried downgrading to the latest 1.5.0 release from around Juno SR2, but
> had the same problem. So I'm back to our old version for now.
>
> Has there been any change in how to request platform-independent
> materialization?
>


--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
Previous Topic:Trigger Eclipse Compiler Log generation in Headless Build
Next Topic:build command that proceeds on error
Goto Forum:
  


Current Time: Mon Sep 22 00:15:05 GMT 2014

Powered by FUDForum. Page generated in 0.01643 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software