Welcome!

Welcome to the Official BlackBerry Support Community Forums. This is your resource to discuss support topics with your peers, and learn from each other. New to the forum? Please visit the ‘Getting Started’ link below.
inside custom component

Android™ Runtime Development

Reply
New Developer
adamleaf8601
Posts: 61
Registered: ‎02-06-2012
My Carrier: Bell

Re: Eclipse Won't Accept Path to BlackBerry Tools SDK

And when i go in eclipse, their is no bb tab thing

Please use plain text.
New Contributor
mercraus
Posts: 8
Registered: ‎02-05-2012
My Carrier: AT&T

Re: Eclipse Won't Accept Path to BlackBerry Tools SDK

Follow these instructions closely.

https://bdsc.webapps.blackberry.com/android/documentation/request_keys_1766003_11.html

 

Steps are pretty much

1) Install Java JDK

2) Install Android SDK

3) Use Android SDK Manager to install Android SDK platform-tools, rev16 and Android 2.3.3 (API 10)

4) Install Eclipse

5) Install Android ADT Plugin in Eclipse

6) Install Blackberry Plugin in Eclipse

 

THEN the BB option shows up.

Please use plain text.
New Member
egfconnor
Posts: 1
Registered: ‎02-06-2012
My Carrier: AT&T

Re: Eclipse Won't Accept Path to BlackBerry Tools SDK

I am having the same issue as the OP as well. I have reinstalled Eclipse/Android SDK/ADT/Blackberry plugin 3 times now with the same problems. I have a brand new 64 bit version of Windows 7 and have followed their instructions to a tee everytime.

 

Makes it pretty hard to jump into converting apps to Blackberry when the guides don't even work :smileysad:

Please use plain text.
New Contributor
mercraus
Posts: 8
Registered: ‎02-05-2012
My Carrier: AT&T

Re: Eclipse Won't Accept Path to BlackBerry Tools SDK

Maybe this is a 64bit Windows 7 compatibility problem? I'm running the same OS setup. Anyone have this working on 64bit Windows 7?
Please use plain text.
New Contributor
mercraus
Posts: 8
Registered: ‎02-05-2012
My Carrier: AT&T

Re: Eclipse Won't Accept Path to BlackBerry Tools SDK

FIXED:

 

Check for updates in eclipse today and it grabbed an updated BlackBerry Plugin. Everything works now, they must have fixed it.

Please use plain text.