Skip to content

Conversation

@zewt
Copy link

@zewt zewt commented Apr 30, 2011

No description provided.

zewt added 7 commits April 30, 2011 11:56
I'm building asmack for BEEM, and they have a patch to pin the revision of
smack to the one they build with.  This is a partial merge of that patch:

http://www.beem-project.com/hg/trunk/file/64f37098247c/doc/asmack-beem/beem-build-process.patch

However, this is done in a way that doesn't require specifying "HEAD" on
every fetch that doesn't require it, so it'll simplify the downstream
patch to a one-line change.
If something fails unexpectedly, stop immediately.  Pressing ^C should
stop the whole task, not cancel a running svn checkout and start the
next, and if a fetch fails, don't keep going and hide the error until
it breaks things later on.
Building in Eclipse fails when the SDK version is lower than 9, because
javax.xml.transform only exists in that version.  Removing the code
using the imports isn't enough; remove the imports, too.

Fixes build with SDK version 4.
The build drops files into build/src/trunk, leading to paths like
build/src/trunk/org.  Most projects have paths that look like
build/src/org.  By using the "standard" (ish) layout, you can
create an Eclipse project, tell it to "create project from existing
source", and point it at build/, and it'll just work.

Adjust build.xml for the Ant build.
This is the last step for Eclipse: it needs an AndroidManifest.xml, even
for libraries.  (It uses it to determine which SDK version to build
against, at least.)

Now, the only thing you need to do in Eclipse is create a project
pointing at build, then in the project properties Android page, select
"Is Library".
Unintended change in 70038b5 from a remote patch; revert it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant