You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The project was not built since its build path is incomplete. Cannot find the class file for org.robovm.cocoatouch.uikit.UIApplicationDelegate$Adapter.
#33
Hi there!
I'm really keen to try libGTX. Just having a bit of trouble getting past this
little guy...
What steps will reproduce the problem?
1. Install Eclipse with Android SDK (from developer.android.com)
2. Install GTW libraries and add them to the build path
3. Add JRE 6 to the build path
What is the expected output? What do you see instead?
The project was not built since its build path is incomplete. Cannot find the
class file for org.robovm.cocoatouch.uikit.UIApplicationDelegate$Adapter. Fix
the build path then try building this project my-gdx-game-robovm Unknown Java
Problem
What version of the product are you using? On what operating system?
Eclipse 4.2, JRE6, libGDX 0.9.9, latest RoboVM from github, Windoes 8
Any help would be much appreciated,
Thanks!
Original issue reported on code.google.com by nathansh...@gmail.com on 19 Dec 2013 at 5:01
The text was updated successfully, but these errors were encountered:
Okay I found a solution. When generating the LibGDX project, you have "Generate
ios project" checked. It shouldn't be. And if you do want to generate one, get
the RoboVM plugin.
Original comment by crossthe...@gmail.com on 3 Feb 2014 at 5:44
Whew! Finally a proposed solution to my exact error.
I used the gdx-setup-ui, which generates the LibGDX projects automatically. Do
you know if I am able to change a setting on the robovm project within Eclipse
to effectively uncheck "generate ios project" (i.e. change the project type to
something else- and what should that something else be?). Or, do I have to
generate a new individual robovm project?
Original comment by wriedt.j...@gmail.com on 7 Feb 2014 at 11:05
Original issue reported on code.google.com by
nathansh...@gmail.com
on 19 Dec 2013 at 5:01The text was updated successfully, but these errors were encountered: