Go to the Eclipse downloads section at http://www.eclipse.org/downloads and select Eclipse Standard. The Eclipse 4 codename, Juno, is the minimum version needed to use the required plugins.

Simply pick the right version for your operating system and wait for it to download; be wary that it is also 32/64-bit sensitive.

Once this is complete, extract the compressed file where you want to use Eclipse from and you will be done.

From a GNU/Linux system, you can do the following:

cd ~/Downloads
tar –xzvf eclipse-standard-kepler-SR1-linux-gtk-x86_64.tar.gz
mv eclipse ~/dev
rm eclipse-standard-kepler-SR1-linux-gtk-x86_64.tar.gz

Access the download page at http://developer.android.com/sdk.

Scroll down and unfold the View all downloads and sizes section and, again, choose your operating system from the SDK Tools Only section. Google has an easy-to-use installer for Windows users, so if you want to be spared part of the hassle, use the installer.

The installer is really simple. Limit yourself to follow the instructions, and if JDK is properly added to the environment variables, everything should be completely smooth. The installation folder does not really matter.

Run Eclipse and create a new workspace to import your recipe's code into. Just so we are all on the same page, let's name it libgdx-cookbook.

Once you see the welcome panel, close it and select Help | Install New Software. The Android Developer Tools and the Google Web Toolkit plugins can be found at http://dl.google.com/eclipse/plugin/4.3.

Select Developer Tools, Google Plugin for Eclipse, and Google Web Toolkit SDK, and proceed with the installation. A modal dialog will warn you about installing unsigned content because there is always an inherent risk when installing plugins. Rest assured Google's tools are safe. Upon completion, Eclipse will need to restart, and you will be prompted to enter the Android SDK location.

Now, follow the same process for the RoboVM plugin; you will find it at http://download.robovm.org/eclipse.

There is only one option within the repository, so select it, carry on with the installation, and restart Eclipse once again.

Once again, go to the Install new software option in Eclipse and introduce the URL http://dist.springsource.com/release/TOOLS/gradle.

Install the Gradle IDE entry and restart Eclipse for the last time.

Character encoding is applied on a per-workspace basis, and to fix it, you need to access the libgdx-cookbook workspace you just created.

Click on Window, select Preferences | General, then select Workspace, and make sure UTF-8 encoding and Unix line endings are your choices.

Once you have Eclipse open in front of you, right-click on Package Explorer, select Import, and choose Gradle project inside the Gradle node.

Select the [cookbook]/environment folder, and click on Build Model.

Make sure you select all listed projects, and click on Finish to start importing the projects. Gradle will now download all the dependencies, which may take a while.

As long as everything goes according to plan, the only error you might see on the Problems pane will be in the Android project. This is because it is set to use an Android SDK different from the one you installed. In such a case, right-click on environment-test-android, go to Properties, and tick your installed Android SDK under the Android tab. You can also install the missing SDK if you prefer to do so.

All the assets are located inside the environment-test-android project and will be shared across all platforms.

We now need to tell the desktop project where the assets are located. Right-click on the desktop project (environment-test-desktop), select Properties | Run/Debug Settings, select DesktopLauncher, and click on Edit.

Open the Arguments tab and select Other as the working directory.

Now enter this in the input box:

${workspace_loc:environment-test-android/assets}

On the device, go to Settings, enter About Phone, and tap the Build Number block seven times to enable developer options. Yes, do not ask why.

Once you get a message saying you just became a developer, you can go to Settings | Developer options and enable USB debugging.

Now, you can run the environment test on your device by right-clicking on the Android project, entering the Run As menu, and selecting Android Application. Finally, choose your device from the list.

Right-click on the environment-test-gwt project and select Run As Gradle build….

On the next window, type Ctrl + Space, and scroll down and double-click on the gwtSuperDev task. Click on Apply followed by Run.

The first time you do this, it will take quite a while. Under the hood, the build process will launch a Jetty web server on your computer.

After a while, you will be able to access it through the following URL:

http://localhost:8080/gwt

A background code server will accept build requests from the browser, so no manual full compilation is needed once you kick it off. You will notice a particular message in the compiler output:

The code server is ready.
Next, visit http://localhost:9876/

Access the URL and drag the Dev Mode On bookmarklet onto the browser's bar. You will never need to do this again.

Back on your running environment test tab, click on the newly added bookmarklet, and select compile. Any change to the game code will be recompiled and reinjected in the web server.

After a short time, the page will refresh and you can run the most recent version of your code.