Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Using the Build Model Editor


I see I forgot to answer another of your questions:

> Is it true that I have to build it from CVS?

I'm not sure. Probably, for Helios. The last time I installed it from its repository site, I had to use
Galileo SR2 as . the base to install into. I suspect there is some ranges specific to that release?





From: David M Williams/Raleigh/IBM@IBMUS
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 06/06/2010 10:06 AM
Subject: Re: [cross-project-issues-dev] Using the Build Model Editor
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx






> Is that a sign that the helios.build model (instance) is invalid or that
> the amalgamation build (meta) model is not uptodate?


The later. This was introduced with the fix for bug 312011 (to add more platforms to verify, and have in content metadata).

https://bugs.eclipse.org/bugs/show_bug.cgi?id=312011

Since we are moving toward the b3.aggregator, the old model was not updated
to accommodate more platforms.


You can still use the editor with a little twist. What I do is first open the helios.build file with a text editor

and remove all the "new" platforms and leave only a subset:


 <configs/>

 <configs arch="x86_64"/>

 <configs os="linux" ws="gtk" archiveFormat="tar"/>

 <configs os="linux" ws="gtk" arch="ppc" archiveFormat="tar"/>


(You need to have 'four' in this list, as there's another part of the file that refers to "config:3".)


The editor will then open and you can edit what you like. If changes are made to helios.build that have to be checked in,
then you need to use care to restore the configs list to what it was initially, again "by hand".
 
Hope this helps you accomplish what you need.


Thanks,




From: Eike Stepper <stepper@xxxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 06/06/2010 01:41 AM
Subject: [cross-project-issues-dev] Using the Build Model Editor
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx






Hi,

I'd like to use the Build Model Editor from Amalgamation. Is it true
that I have to build it from CVS?

For now I've built it locally and I can open an EMF editor for my build
contribution file. That's cool if I only want to change the properties
of existing features.

But if I want to *add* features to the helios.build file it would be
nice to use the editor on that file. Unfortunately it opens with an
error message and lets me create these error markers:

Description    Resource    Path    Location    Type
IllegalValueException: Value 'aix' is not legal.
(platform:/resource/org.eclipse.helios.build/helios.build, 16, 64)    
helios.build    /org.eclipse.helios.build    line 16, column 64    Problem
IllegalValueException: Value 'hpux' is not legal.
(platform:/resource/org.eclipse.helios.build/helios.build, 15, 69)    
helios.build    /org.eclipse.helios.build    line 15, column 69    Problem
IllegalValueException: Value 'ia64_32' is not legal.
(platform:/resource/org.eclipse.helios.build/helios.build, 15, 69)    
helios.build    /org.eclipse.helios.build    line 15, column 69    Problem
IllegalValueException: Value 'motif' is not legal.
(platform:/resource/org.eclipse.helios.build/helios.build, 15, 69)    
helios.build    /org.eclipse.helios.build    line 15, column 69    Problem
IllegalValueException: Value 'motif' is not legal.
(platform:/resource/org.eclipse.helios.build/helios.build, 16, 64)    
helios.build    /org.eclipse.helios.build    line 16, column 64    Problem
IllegalValueException: Value 'motif' is not legal.
(platform:/resource/org.eclipse.helios.build/helios.build, 7, 55)    
helios.build    /org.eclipse.helios.build    line 7, column 55    Problem
IllegalValueException: Value 'ppc64' is not legal.
(platform:/resource/org.eclipse.helios.build/helios.build, 10, 66)    
helios.build    /org.eclipse.helios.build    line 10, column 66    Problem
IllegalValueException: Value 's390' is not legal.
(platform:/resource/org.eclipse.helios.build/helios.build, 11, 65)    
helios.build    /org.eclipse.helios.build    line 11, column 65    Problem
IllegalValueException: Value 's390x' is not legal.
(platform:/resource/org.eclipse.helios.build/helios.build, 12, 66)    
helios.build    /org.eclipse.helios.build    line 12, column 66    Problem
IllegalValueException: Value 'solaris' is not legal.
(platform:/resource/org.eclipse.helios.build/helios.build, 13, 68)    
helios.build    /org.eclipse.helios.build    line 13, column 68    Problem
IllegalValueException: Value 'solaris' is not legal.
(platform:/resource/org.eclipse.helios.build/helios.build, 14, 55)    
helios.build    /org.eclipse.helios.build    line 14, column 55    Problem
IllegalValueException: Value 'sparc' is not legal.
(platform:/resource/org.eclipse.helios.build/helios.build, 13, 68)    
helios.build    /org.eclipse.helios.build    line 13, column 68    Problem

Is that a sign that the helios.build model (instance) is invalid or that
the amalgamation build (meta) model is not uptodate?

Cheers
/Eike

----

http://thegordian.blogspot.com
http://twitter.com/eikestepper


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx

https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



Back to the top