Getting Started Guide?

[Andrex]

If it's not too much trouble could someone post some simplified steps
to getting this to compile correctly?

I've checked out the source code from SVN, but either get errors when
importing it into a new Android project, or the project loses its
status as an Android app entirely. I know I'm doing something wrong,
so if anyone could point me to the Right Way of doing things it'd be
appreciated, thanks.

Perhaps including these steps in a file with the source in the future
would be a good idea. The README isn't very helpful.

[Martin Foot]

In Eclipse it should be as easy as going to File > New > Android Project, selecting "Create project from existing source", and pointing the wizard to your checked out folder. You should ensure that you have the correct build target installed too.

If you fancy using Ant, you can do the following:

Create a build.xml

$ ant update

Get rid of some pesky apostrophes, there's a possibility that this might mess up the text string in Java, I haven't tested it

$ sed -i "s/'/\\\'/g" res/values/*.xml

Make an apk

$ ant debug

Perhaps install it

$ ant install

[Martin Foot]

Oops, that should have said

$ android update project -p .

Instead of "ant update"!

On 24 June 2010 18:59, Andrex <emailo...@gmail.com> wrote:

[Bart Hirst]

We need a specific error message or screenshot to diagnose the problem.

[Andrex]

OK, so like when I imported, when I created from an existing source I
got several errors. Here's a list:

One parsing error each in res/values/strings.xml and res/values/
wanda.xml having to do with unescaped single quote marks.

Multiple errors having to deal with R.java either not being declared
or having the correct types, even when explicitly importing it. This
affects the following files: AndouKun.java,
AnimationPlayerActivity.java, ConversationDialogActivity.java,
CustomToastSystem.java, DebugSystem.java, DiaryActivit.javay,
Game.java, GameObjectFactory.java,
KeyboardConfigDialogPreferences.java, LevelBuilder.java,
LevelSelectActivity.java, MainMenuActivity.java,
SetPreferencesActivity.java, and SliderPreference.java.

Error in GLSurfaceView.java, "GL_ES_VERSION_UNDEFINED cannot be
resolved."

It is targeting Android 1.5. It's frustrating because I've been toying
with Android since the first SDK and I'm not really a Java beginner,
but there's still things which are obvious to everyone else that mess
me up. The drawback of being mostly self-taught I guess.

On Jun 24, 3:27 pm, Bart Hirst <louisbhi...@gmail.com> wrote:
> We need a specific error message or screenshot to diagnose the problem.
>
>
>
> On Thu, Jun 24, 2010 at 2:45 PM, Martin Foot <supernova...@gmail.com> wrote:
> > Oops, that should have said
>
> > $ android update project -p .
>
> > Instead of "ant update"!
>

[Chris Pruett]

OK, couple of things:

- The project should be built against Android 1.6. It's backwards-
compatible to 1.5, but targets 1.6 (for now; next release will
probably target 2.2 and be backwards compatible to 1.5).

- The apostrophe errors are the only real errors here. Sorry about
those. Escaping them will solve the problem. Last minute string
additions.

- The R.java file errors are a result of the apostrophe errors causing
that file not to get generated. Should go away if you escape the
apostrophes.

- The GL error is probably a result of targeting 1.5.

Sorry for the confusion. Apostrophes will be fixed in next source
push (which may be a while--in the middle of a bunch of other changes).

Chris

[Andrex]

Thanks Chris. I was gonna make it 1.6 but I got a warning saying the
min-sdk was API 3, so I figured that's what it was supposed to be.

Anyways I think that worked, changed the target to 1.6 and fixed the
apostrophes. Then re-cleaned it in Eclipse and no problems anymore (so
far.)

Would it be too much trouble to ask if you could post the zip on the
Google Code page? Maybe when development settles down a bit? Would be
a lot easier not to jump through SVN's hoops.

[Andrex]

Some more troubles that don't seem to go away... Three errors in
preferences.xml having to do with not having resource identifiers
found for various things. Obviously, it sounds like it would have to
be more problems with R.java, but cleaning and building doesn't seem
to solve it. Relaunching Eclipse doesn't fix it. Maybe I should just
use the command line from now on.

[Chris Pruett]

Eclipse just calls the command line tools, so ditching it won't help you with this.  Could you post the errors that are reported? Others have not had problems.

[Andrex]

Well the weird thing is I did get it to compile a few times after
fixing those two xml files. Then I restarted my computer and boom,
some more errors. :P

Errors in res/xml/preferences.xml

Line 44:
- error: No resource identifier found for attribute 'attackKey' in
package 'com.replica.replicaisland'
- error: No resource identifier found for attribute 'jumpKey' in
package 'com.replica.replicaisland'
- error: No resource identifier found for attribute 'rightKey' in
package 'com.replica.replicaisland'
- error: No resource identifier found for attribute 'leftKey' in
package 'com.replica.replicaisland'

Line 58:
- error: No resource identifier found for attribute 'minText' in
package 'com.replica.replicaisland'
- error: No resource identifier found for attribute 'maxText' in
package 'com.replica.replicaisland'

Line 77:
- error: No resource identifier found for attribute 'minText' in
package 'com.replica.replicaisland'
- error: No resource identifier found for attribute 'maxText' in
package 'com.replica.replicaisland'

Sorry for the trouble Chris.

On Jul 5, 8:39 pm, Chris Pruett <sm0a...@gmail.com> wrote:
> Eclipse just calls the command line tools, so ditching it won't help you
> with this.  Could you post the errors that are reported? Others have not had
> problems.
>

[Andrex]

A month later... the same errors again. I thought it had something to
do with Eclipse, but I don't know at this point.

[Andrex]

Actually, I think I found the problem. I made a project, then imported
Replica Island. Switching the default activity and some other things
around in the AndroidManifest to RI instead of the package I started
with seems to have worked. Sorry for the headaches guys.

Though I'll probably have another one for you all soon.