|
| Re: headless buckminster and plugin dependencies [message #516310 is a reply to message #516273] |
Tue, 23 February 2010 15:13   |
 Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
Hi,
The elegant way is to use a target platform.
You want to use the same TP in your IDE and headless.
This enables you to build your code against a precise definition (as
opposed to building it against whatever you happen to have installed in
your IDE).
As an example, a TP is very useful when using say 3.6 to develop against
3.5.
Buckminster can materialize a TP, and it can materialize from p2
repositories - so there is no need to check things into your SCM, nor do
you need to install them into your headless buckminster.
There has been several posts in this newsgroup with
examples/questions/answers how to do this. Also check out the
Buckminster Book (from the Buckminster download site).
In short - you need to decide on where the TP is (a folder). Best
practice is to keep this folder in the workspace so it can be
inspected). You then need a buckminster MSPEC (materialization
specification) that directs the components found in the resolution to
different locations (the workspace, or the TP of your choice).
Continuing on this path, you may want to also want to create your own p2
repository with the things you require in the TP (unless you want to
rely on external update sites to keep the things you need for as long as
you need them). To easily create the p2 repository you can use the b3
aggregator (a.k.a the buckminster aggregator) to author, run, and
validate your p2 repository composition.
Regards
- henrik
On 2/23/10 2:27 PM, Bernhard Merkle wrote:
> Hi,
>
> I have a project which has depdencies to e.g. emf 2.5 plugins.
>
> Now my eclipse installation (with buckminster) has emf 2.5.0 and
> everything builds fine, also the buckminster task for p2 updatesite
> build fine.
>
> Now if I run the same in my headless-buckminster, (which has no emf
> 2.5.0) I of course get build/compile errors.
>
> question:
> - what is the right approach to cope with this
>
> 1. make emf2.5.0 (and all other required plugins) part of my version
> control ? and check them out ? if yes, how can I achive that in a simple
> way ?
>
> or 2. install emf2.5.0 also in the headless-bucky installation ?
> which seem to end in a duplicated installation and anyway this build is
> not 100% reproducable as it is not under version control.
>
> is there another method to handle this in a elegant way,
>
> thanks,
> Berni.
>
|
|
|
|
|
| Re: headless buckminster and plugin dependencies [message #516465 is a reply to message #516443] |
Wed, 24 February 2010 01:56 |
|
On 02/24/2010 12:13 AM, Henrik Lindberg wrote:
> A target platform is a configuration similar to the IDE's configuration
> of "itself", but used to "build against" as opposed to "running". Maybe
> I am using the wrong term and Target Definition is the right/official
> one...
>
I think both are valid. A target definition defines a target platform.
>> PS. the eclipse newsgroup is a pain to search sorry, even with the
>> google search box. Is there any trick ?
>
> I use Thunderbird as a news reader, and I use the search there.
>
I found that one prerequisite for the search to work well in Thunderbird is that the newsgroup folder is marked as
available for off-line use.
- thomas
|
|
|
|
Powered by
FUDForum. Page generated in 0.03270 seconds
] 
Search
Help
Register
Login
Home
