-
Notifications
You must be signed in to change notification settings - Fork 80
Build
These instructions should work on Mac and Linux. Windows/cygwin is not fully working yet.
Get the latest Android SDK and NDK. You need to install support for the android-10 platform.
Install a recent version of Python 2.x.
Install Git.
Create a directory, we'll refer to as <work dir> that will contain all of the repositories you need, and cd into this directory.
anode depends on the openssl libraries libssl.so and libcrypto.so. These libraries are present on the phone and also on the emulator, but aren't officially part of the ndk. We prefer to use the platform-provided versions of these libraries (instead of building a copy into anode) and so you have to build a copy of each of these libraries before building anode itself.
Starting in <work dir>, clone the repo:
git clone git://github.com/paddybyers/openssl-android.git
To build it:
cd openssl-android
ndk-build
cd back to <work dir>.
Clone each of the repositories in turn.
git clone git://github.com/paddybyers/anode.git
git clone git://github.com/paddybyers/pty.git
git clone git://github.com/paddybyers/node.git
This last repository has a number of development branches with the Android port, but use the default, v0.6-android which is derived from node.js v0.6.
There is also a master-isolate-android branch which is derived from master. To use this, you will need to cd into the node directory and git checkout master-isolate-android. This will be used to track 0.7/0.8 developments but should be expected to be unstable.
If the organisation of the repo directories is as suggested above, then the build system will find everything.
However, if you specifically wish to build against a node source tree located elsewhere, set up the NODE_ROOT variable to point to the top-level node directory of that repo.
There is a single top-level Application.mk that builds the libjninode and bridge dependencies.
cd anode
ndk-build NDK_PROJECT_PATH=. NDK_APPLICATION_MK=Application.mk
Once the native libraries is built, this needs to be included as an asset in the top-level Android project:
cp libs/armeabi/libjninode.so ./app/assets/
cp libs/armeabi/bridge.node ./app/assets/
(The previous instructions involved creating a symlink to the shared library instead of copying the file. However, for some reason this does not work with bridge.node - Eclipse does not seem to recognise the file if it is linked and not copied. If anyone understands why this is, please let me know.)
Or if you prefer (or on Windows), edit the top-level makefile to add an install target to perform the copy.
Open Eclipse and do:
File->Import->General->Existing projects into workspace
Point to the <work dir>/anode directory and import the app, libnode and bridge-java projects.
You are now ready to build and run.
Note : If the UNEXPECTED TOP-LEVEL EXCEPTION: already added: Lorg/meshpoint/anode/RuntimeNative; error shows up in Eclipse, try to remove libnode-src from build path (in package explorer, right-click on app/libnode-src>Build path...>Remove from build path).