I need to keep the old Android 1.1_r1 SDK around because I have an app
that won't build with the 1.1 SDK included with the 1.5 SDK (Actually,
it builds, but the newer Dalvik converter won't convert it, error 2,
no other feedback as to the problem in Eclipse's console). So I have
two completely separate Eclipse installations. However, they seem to
share at least *some* preferences (this is on OS X btw), namely, the
Android SDK location preference.
Is this going to work? I can switch the SDK location preference back
and forth as I use the two different versions of Eclipse if I have to
(a little annoying I suppose), but are there larger issues I need to
worry about? Are there any other really serious problems, perhaps as
yet unanticipated, with maintaining two different Eclipse installs
using two different Android SDKs?
I've always found that the Workspace holds reference to the Android
SDK location so if you are using a different Workspace you should even
be able to use just the one install of Eclipse. I am working on
Windows but would image that the same would apply to Mac...
On May 19, 9:17 am, Keith Wiley <kbwi...@gmail.com> wrote:
> I need to keep the old Android 1.1_r1 SDK around because I have an app
> that won't build with the 1.1 SDK included with the 1.5 SDK (Actually,
> it builds, but the newer Dalvik converter won't convert it, error 2,
> no other feedback as to the problem in Eclipse's console). So I have
> two completely separate Eclipse installations. However, they seem to
> share at least *some* preferences (this is on OS X btw), namely, the
> Android SDK location preference.
> Is this going to work? I can switch the SDK location preference back
> and forth as I use the two different versions of Eclipse if I have to
> (a little annoying I suppose), but are there larger issues I need to
> worry about? Are there any other really serious problems, perhaps as
> yet unanticipated, with maintaining two different Eclipse installs
> using two different Android SDKs?
With Eclipse 3.3, the plugins are installed in the Eclipse directory.
With Eclipse 3.4 and P2 there's a common pool of plugin and specific
instances per Eclipse directory.
The plugins preferences are however associated with the workspace.
In your case you need to have 2 different plugins so you should have
the following:
- One install of Eclipse 3.4 with the ADT 0.8 plugin
- One workspace with the SDK 1.1 pref for that Eclipse install
- Another install of Eclipse 3.4 with the ADT 0.9 plugin
- Another workspace with the SDK 1.5 pref for the other Eclipse install
On Tue, May 19, 2009 at 6:24 PM, nEx.Software <justin.shapc...@gmail.com> wrote:
> I've always found that the Workspace holds reference to the Android
> SDK location so if you are using a different Workspace you should even
> be able to use just the one install of Eclipse. I am working on
> Windows but would image that the same would apply to Mac...
> On May 19, 9:17 am, Keith Wiley <kbwi...@gmail.com> wrote:
>> I need to keep the old Android 1.1_r1 SDK around because I have an app
>> that won't build with the 1.1 SDK included with the 1.5 SDK (Actually,
>> it builds, but the newer Dalvik converter won't convert it, error 2,
>> no other feedback as to the problem in Eclipse's console). So I have
>> two completely separate Eclipse installations. However, they seem to
>> share at least *some* preferences (this is on OS X btw), namely, the
>> Android SDK location preference.
>> Is this going to work? I can switch the SDK location preference back
>> and forth as I use the two different versions of Eclipse if I have to
>> (a little annoying I suppose), but are there larger issues I need to
>> worry about? Are there any other really serious problems, perhaps as
>> yet unanticipated, with maintaining two different Eclipse installs
>> using two different Android SDKs?
> With Eclipse 3.3, the plugins are installed in the Eclipse directory.
> With Eclipse 3.4 and P2 there's a common pool of plugin and specific
> instances per Eclipse directory.
> The plugins preferences are however associated with the workspace.
> In your case you need to have 2 different plugins so you should have
> the following:
> - One install of Eclipse 3.4 with the ADT 0.8 plugin
> - One workspace with the SDK 1.1 pref for that Eclipse install
> - Another install of Eclipse 3.4 with the ADT 0.9 plugin
> - Another workspace with the SDK 1.5 pref for the other Eclipse install
> R/
> On Tue, May 19, 2009 at 6:24 PM, nEx.Software <justin.shapc...@gmail.com> wrote:
> > I've always found that the Workspace holds reference to the Android
> > SDK location so if you are using a different Workspace you should even
> > be able to use just the one install of Eclipse. I am working on
> > Windows but would image that the same would apply to Mac...
> > On May 19, 9:17 am,KeithWiley<kbwi...@gmail.com> wrote:
> >> I need to keep the old Android 1.1_r1 SDK around because I have an app
> >> that won't build with the 1.1 SDK included with the 1.5 SDK (Actually,
> >> it builds, but the newer Dalvik converter won't convert it, error 2,
> >> no other feedback as to the problem in Eclipse's console). So I have
> >> two completely separate Eclipse installations. However, they seem to
> >> share at least *some* preferences (this is on OS X btw), namely, the
> >> Android SDK location preference.
> >> Is this going to work? I can switch the SDK location preference back
> >> and forth as I use the two different versions of Eclipse if I have to
> >> (a little annoying I suppose), but are there larger issues I need to
> >> worry about? Are there any other really serious problems, perhaps as
> >> yet unanticipated, with maintaining two different Eclipse installs
> >> using two different Android SDKs?
|
