Skip to main content

How to setup Eclipse for Android Development

In order to work with Android Development Environment, Eclipse is one of the preferred tools. Following are the steps used to setup Eclipse for the development:


Step 1: Download the JDK Standard Edition from Oracle's website.

Step 2: Install the JDK Standard Edition

Step 3: Set the path of the Bin directory of JDK installation in the Environmental variable called PATH in Windows Environment.

Step 4: Download the Android SDK from Google.

Step 5: Install Android SDK and Select platforms which you want to download i.e. 2.2, 2.3, Android 4.0 ICS.

Step 6: Download Eclipse Software from Eclipse.org

Step 7. Install Eclipse software. While installation, it should automatically pick path of JDK installation. If not picked up automatically, then specify the same in the Eclipse settings.

Step 8. Download the ADT (Android Development Tools) plugin. 

Step 9. Add ADT Plugin in the Eclipse. For adding:

i.               In case of Indigo(Eclipse) go to Workspace and Software Centre and then choose, Software Tab and add plugin.
ii.              In case of Helios(Eclipse), add the ADT Plugin through HELP and install new software.

Note: In most of the cases, the Step 10 can be excluded, because step 9 will add all the details.

Step 10: Add Android SDK into Eclipse. In order to do the same, we need to go to the Preferences and Select Android from Left hand tree and give the path of the Android SDK.

Step 11: After we are done with the above steps, we need to establish AVD : Android Virtual Device. This can be done from Window à AVD Manager and create a new.

I hope this will help every one in setting up the environment to work with Android.

Comments

Post a Comment

Popular posts from this blog

Connecting Nodejs to SQL Server with Knex ORM - Part 1

Normally we connect Nodejs to the databases like SQLite, MongoDB, Postgres etc . In this multiple part post, I am going to show you, how we can connect Nodejs with Microsoft's SQL Server using Knex and run CRUD operations. 1. Installation of required packages In order to connect Nodejs to SQL Server with Knex, we will need following node packages installation: i. npm install knex ii. npm install mssql Once the packages are installed, we can write the following code to connect: //Code to KNEX connection settings. var knex = require('knex')({ client: 'mssql', connection: { user: 'sa', password: 'pwd', server: 'localhost', database: 'Test' } }); //Code to query the Table DEPT knex.select("*").from("dept") .then(function (depts){ depts.forEach((dept)=>{ //use of Arrow Function console.log({...dept}); }); }).catch(function(err) { ...
Post a Comment
Read more

SQLServer Error: 15404, Could not obtain information about Windows NT group/user Error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)

If we encounter this error "SQLServer Error: 15404, Could not obtain information about Windows NT group/user Error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)" in SQL Server in which the job fails because of the user account related problem, then we need to take the following steps to make it work: a. Go to SQL Server Agent. b. Then select the job which is giving error and not running successfully. c. Then choose properties and in the General Tab, change the owner to "SA" or any account that has the administrative privileges. The problem will be resolved.
1 comment
Read more

MAX pool size reached in ASP.NET

If you are handling large databases and big application(s) that are running on servers in a cluster, then probably this error might have occurred. In an ASP.NET app, we can use connection pooling that helps to share the connection between multiple request(s) rather than creating more connections. The settings relating to connection pool are defined in web.config file. Max pool size reached error in ASP.NET occurs, when the number of connections go beyond the maximum defined limit in Web.config file. Following are the various settings of the Connection Pooling: Name Default Description Connection Lifetime 0 When a connection is returned to the pool, its creation time is compared with the current time, and the connection is destroyed if that time span (in seconds) exceeds the value specified by  Connection Lifetime . This is useful in clustered configurations to force load balancing between a runnin...
Post a Comment
Read more