| Specifying a combination for target.ws/os/arch [message #1005431] |
Fri, 25 January 2013 07:26  |
 Lorenzo Bettini
Messages: 1119
Registered: July 2009 |
Senior Member |
|
|
Hi
a similar question was posted in this newsgroup, but I have a slightly
different context, though it's related to the possibility of specify
combination for target.os/ws/arch:
say that I want to build my site (and my products) only for these
combinations
os="linux,macosx,win32"
ws="cocoa,gtk,win32"
arch="x86,x86_64"
during materialization (of the TP) I cannot specify a combination in the
cquery for the desired os.ws.arch (I tried with LDAP filters but they
don't work) but I can exclude the other architectures
with advisor nodes, e.g.,
<cq:advisorNode namePattern=".*\.solaris.*" skipComponent="true"/>
and, then equinox launchers (for instance) are not included for these
architectures...
but then, when I build the site.p2 (for later product installation) I
cannot specify the desired combinations: I can only specify in the
properties file
target.os=*
target.ws=*
target.arch=*
and the action fails due to
No component named
org.eclipse.equinox.launcher.gtk.solaris.sparc:osgi.bundle/[1.1.200.v20120522-1813,1.1.200.v20120522-1813](&(target.arch=sparc)(target.os=solaris)(target.ws=gtk))
is known to Buckminster
how could then avoid this problem?
rationale: I'd have no problem in getting into the TP and in the site.p2
all available combinations, but I'd like to materialize the TP against a
local mirror built with the b3 aggregator (and possibly install the
products reusing this mirror), and, as far as I understand, in the
b3aggr you must specify manually all valid architecture combinations,
you can't just say * (and I'd like to avoid specifying here also the
combinations I'm not interested in).
thanks in advance
Lorenzo
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
|
|
|
] 
Search
Help
Register
Login
Home
