| Can't start off with a empty target platform [message #684491] |
Wed, 15 June 2011 16:51  |
 Matthew Webber
Messages: 198
Registered: December 2010 |
Senior Member |
|
|
In a new, empty workspace, I went to Window --> Preferences --> Target Platform and un-checked the default target (which is the running IDE platform). It then told me that I had no active target - good.
I now open a CQuery and materialize it. My RMap points to everything required, including the helios p2 site. Buckminster as expected creates a .buckminster/tp directory to hold the target platform.
After materializtion, I go to the look at the target platform defintion, and see that in addition to .buckminster/tp it also includes the ${eclipse_home} installation, which is NOT what I wanted - that contains the wrong version of various things.
Is the observed behaviour as expected, or a bug?
I was able to work around it by defining an explicit target platform, pointing to an empty directory, but is there another way?
This is Helios SR2 by the way.
Thanks
|
|
|
| Re: Can't start off with a empty target platform [message #684569 is a reply to message #684491] |
Wed, 15 June 2011 20:34  |
|
On 2011-06-15 18:51, Matthew Webber wrote:
> In a new, empty workspace, I went to Window --> Preferences --> Target Platform and un-checked the default target (which
> is the running IDE platform). It then told me that I had no active target - good.
>
Not really. I think you should create an empty target platform and add a directory to it. Then set that as the active
target platform. Buckminster will then use that as the default destination for everything binary.
> I now open a CQuery and materialize it. My RMap points to everything required, including the helios p2 site. Buckminster
> as expected creates a .buckminster/tp directory to hold the target platform.
>
> After materializtion, I go to the look at the target platform defintion, and see that in addition to .buckminster/tp it
> also includes the ${eclipse_home} installation, which is NOT what I wanted - that contains the wrong version of various
> things.
>
This is the default behavior when Buckminster doesn't find an active target platform.
> Is the observed behaviour as expected, or a bug?
>
It's expected.
> I was able to work around it by defining an explicit target platform, pointing to an empty directory, but is there
> another way?
>
No, that's the way to do it. If you run headless you can use the preference setting targetPlatformPath. It will
automatically create an empty (and active) target platform unless it doesn't already exist.
HTH,
Thomas Hallgren
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02727 seconds
] 
Search
Help
Register
Login
Home
