Basically, I used the native android compilation tool-chains, Android NDK, as working tools. Due to my working situation, I use a Nvidia Shield Tablet as target device. As Zengwen said in his blog, newest updated NDK might has some issue which can influence compilation progress. So you can find other version of NDK once you have some problems. Based on what Zengwen’s blog mentioned, we can write following useful system environment and export in terminal.
+$ sudo apt-get install build-essential
+$ sudo apt-get install pkg-config automake autoconf libtool
+In order to build standalone tool-chains, we need first to export following system environment. After doing that, we can use following command to build a standalone tool-chains from downloaded NDK.
+ $ ${NDK}/build/tools/make-standalone-toolchain.sh
+ –toolchain=arm-linux-androideabi-4.9
+ –stl=gnustl
+ –arch=arm
+ –ndk-dir=/home/moslab/Android/android-ndk-r12b
+ –package-dir=/home/moslab/Android
+ –install-dir=/home/moslab/Android/android-ndk-toolchain
+ –platform=android-22
/# Android NDK sources and standalone toolchain is put here
-export DEV=~/Android/
+[TODO]-> I will fix this part later.
+ /# Android NDK sources and standalone toolchain is put here
+ export DEV=~/Android/
-/# All the built binaries, libs and their header will be installed here
+/# All the built binaries, libs and their header will be installed here
export PREFIX=/opt/android
/# Don't mix up .pc files from your host and build target
@@ -133,7 +150,7 @@ export ANDROID_TARGET=armv7-none-linux-androideabi
/# The cross-compile toolchain we use
export TOOLCHAIN=arm-linux-androideabi
-/# This is a symlink pointing to the real Android NDK r10e
+/# This is a symlink pointing to the real Android NDK r12b
export NDK=${DEV}/android-ndk
/# The path of standalone NDK toolchain
@@ -169,6 +186,28 @@ export LIBS="-lc -lstdc++ -ld"
export LDFLAGS="-Wl,-rpath-link=-I${SYSROOT}/usr/lib -L${SYSROOT}/usr/lib -L${PREFIX}/lib -L${NDK_TOOLCHAIN}/lib"
+Compile Process
+
+To compile seafile, we should compile ccnet and libsearpc first. As for these two projects, they all have their own dependencies, so we must follow some order to run the compilation.
+
+libsearpc
+
+glib
+
+libiconv
+
+libffi
+
+gettext
+
+libjasson
+
+ccnet
+
+libuuid
+
+seafile
+
Preferences
diff --git a/post/Pokemon-Go-Hack/index.html b/post/Pokemon-Go-Hack/index.html
index c75b239..95056ca 100644
--- a/post/Pokemon-Go-Hack/index.html
+++ b/post/Pokemon-Go-Hack/index.html
@@ -100,12 +100,12 @@ Anyway, after coming back, I think I write too much on useless words, so let me
TODO List
--[x] Test API
--[ ] Finish Walk Algorithm
--[ ] Finish other movement, etc. catch, hatch
--[ ] Smart Walking route
--[ ] Pokemon Predict (Thanks to Pokevision’s idea)
--[ ] Become a Pokemon Master
+-[ ] Test API
+-[ ] Finish Walk Algorithm
+-[ ] Finish other movement, etc. catch, hatch
+-[ ] Smart Walking route
+-[ ] Pokemon Predict (Thanks to Pokevision’s idea)
+-[ ] Become a Pokemon Master
diff --git a/post/index.xml b/post/index.xml
index 72b16ec..f004d78 100644
--- a/post/index.xml
+++ b/post/index.xml
@@ -27,12 +27,12 @@ Anyway, after coming back, I think I write too much on useless words, so let me
<h2 id="todo-list">TODO List</h2>
-<p>-[x] Test API
--[ ] Finish Walk Algorithm
--[ ] Finish other movement, etc. catch, hatch
--[ ] Smart Walking route
--[ ] Pokemon Predict (Thanks to Pokevision’s idea)
--[ ] Become a Pokemon Master</p>
+<p>-[ ] Test API
+-[ ] Finish Walk Algorithm
+-[ ] Finish other movement, etc. catch, hatch
+-[ ] Smart Walking route
+-[ ] Pokemon Predict (Thanks to Pokevision’s idea)
+-[ ] Become a Pokemon Master</p>
@@ -52,16 +52,33 @@ Anyway, after coming back, I think I write too much on useless words, so let me
<h2 id="pre-work">Pre-work</h2>
-<h3 id="tool-chain">Tool-Chain</h3>
-
<p>Basically, I used the native android compilation tool-chains, <a href="https://developer.android.com/ndk/downloads/index.html">Android NDK</a>, as working tools. Due to my working situation, I use a <a href="https://shield.nvidia.com/tablet/k1">Nvidia Shield Tablet</a> as target device. As <em>Zengwen</em> said in his <a href="http://zwyuan.github.io/2016/07/17/cross-compile-glib-for-android/">blog</a>, newest updated NDK might has some issue which can influence compilation progress. So you can find <a href="http://stackoverflow.com/questions/6849981/where-do-i-find-old-versions-of-android-ndk">other version</a> of NDK once you have some problems. Based on what <em>Zengwen’s</em> blog mentioned, we can write following useful system environment and export in terminal.</p>
+<h3 id="prerequisites">Prerequisites</h3>
+
+<pre><code>$ sudo apt-get install build-essential
+$ sudo apt-get install pkg-config automake autoconf libtool
+</code></pre>
+
+<h3 id="link-with-standalone-tool-chains">Link with standalone tool-chains</h3>
+
+<p>In order to build standalone tool-chains, we need first to export following system environment. After doing that, we can use following command to build a standalone tool-chains from downloaded NDK.
+ $ ${NDK}/build/tools/make-standalone-toolchain.sh <br />
+ –toolchain=arm-linux-androideabi-4.9 <br />
+ –stl=gnustl <br />
+ –arch=arm <br />
+ –ndk-dir=/home/moslab/Android/android-ndk-r12b <br />
+ –package-dir=/home/moslab/Android <br />
+ –install-dir=/home/moslab/Android/android-ndk-toolchain <br />
+ –platform=android-22</p>
+
<h3 id="original-system-environment-configuration">Original System Environment Configuration</h3>
-<pre><code>/# Android NDK sources and standalone toolchain is put here
-export DEV=~/Android/
+<p>[TODO]-> I will fix this part later.
+ /# Android NDK sources and standalone toolchain is put here
+ export DEV=~/Android/</p>
-/# All the built binaries, libs and their header will be installed here
+<pre><code>/# All the built binaries, libs and their header will be installed here
export PREFIX=/opt/android
/# Don't mix up .pc files from your host and build target
@@ -87,7 +104,7 @@ export ANDROID_TARGET=armv7-none-linux-androideabi
/# The cross-compile toolchain we use
export TOOLCHAIN=arm-linux-androideabi
-/# This is a symlink pointing to the real Android NDK r10e
+/# This is a symlink pointing to the real Android NDK r12b
export NDK=${DEV}/android-ndk
/# The path of standalone NDK toolchain
@@ -123,6 +140,28 @@ export LIBS="-lc -lstdc++ -ld"
export LDFLAGS="-Wl,-rpath-link=-I${SYSROOT}/usr/lib -L${SYSROOT}/usr/lib -L${PREFIX}/lib -L${NDK_TOOLCHAIN}/lib"
</code></pre>
+<h2 id="compile-process">Compile Process</h2>
+
+<p>To compile seafile, we should compile ccnet and libsearpc first. As for these two projects, they all have their own dependencies, so we must follow some order to run the compilation.</p>
+
+<h3 id="libsearpc">libsearpc</h3>
+
+<h4 id="glib">glib</h4>
+
+<h5 id="libiconv">libiconv</h5>
+
+<h5 id="libffi">libffi</h5>
+
+<h5 id="gettext">gettext</h5>
+
+<h4 id="libjasson">libjasson</h4>
+
+<h3 id="ccnet">ccnet</h3>
+
+<h4 id="libuuid">libuuid</h4>
+
+<h3 id="seafile">seafile</h3>
+
<h2 id="preferences">Preferences</h2>
<ul>
diff --git a/tags/android/index.xml b/tags/android/index.xml
index e241c7a..af11928 100644
--- a/tags/android/index.xml
+++ b/tags/android/index.xml
@@ -25,16 +25,33 @@
<h2 id="pre-work">Pre-work</h2>
-<h3 id="tool-chain">Tool-Chain</h3>
-
<p>Basically, I used the native android compilation tool-chains, <a href="https://developer.android.com/ndk/downloads/index.html">Android NDK</a>, as working tools. Due to my working situation, I use a <a href="https://shield.nvidia.com/tablet/k1">Nvidia Shield Tablet</a> as target device. As <em>Zengwen</em> said in his <a href="http://zwyuan.github.io/2016/07/17/cross-compile-glib-for-android/">blog</a>, newest updated NDK might has some issue which can influence compilation progress. So you can find <a href="http://stackoverflow.com/questions/6849981/where-do-i-find-old-versions-of-android-ndk">other version</a> of NDK once you have some problems. Based on what <em>Zengwen’s</em> blog mentioned, we can write following useful system environment and export in terminal.</p>
+<h3 id="prerequisites">Prerequisites</h3>
+
+<pre><code>$ sudo apt-get install build-essential
+$ sudo apt-get install pkg-config automake autoconf libtool
+</code></pre>
+
+<h3 id="link-with-standalone-tool-chains">Link with standalone tool-chains</h3>
+
+<p>In order to build standalone tool-chains, we need first to export following system environment. After doing that, we can use following command to build a standalone tool-chains from downloaded NDK.
+ $ ${NDK}/build/tools/make-standalone-toolchain.sh <br />
+ –toolchain=arm-linux-androideabi-4.9 <br />
+ –stl=gnustl <br />
+ –arch=arm <br />
+ –ndk-dir=/home/moslab/Android/android-ndk-r12b <br />
+ –package-dir=/home/moslab/Android <br />
+ –install-dir=/home/moslab/Android/android-ndk-toolchain <br />
+ –platform=android-22</p>
+
<h3 id="original-system-environment-configuration">Original System Environment Configuration</h3>
-<pre><code>/# Android NDK sources and standalone toolchain is put here
-export DEV=~/Android/
+<p>[TODO]-> I will fix this part later.
+ /# Android NDK sources and standalone toolchain is put here
+ export DEV=~/Android/</p>
-/# All the built binaries, libs and their header will be installed here
+<pre><code>/# All the built binaries, libs and their header will be installed here
export PREFIX=/opt/android
/# Don't mix up .pc files from your host and build target
@@ -60,7 +77,7 @@ export ANDROID_TARGET=armv7-none-linux-androideabi
/# The cross-compile toolchain we use
export TOOLCHAIN=arm-linux-androideabi
-/# This is a symlink pointing to the real Android NDK r10e
+/# This is a symlink pointing to the real Android NDK r12b
export NDK=${DEV}/android-ndk
/# The path of standalone NDK toolchain
@@ -96,6 +113,28 @@ export LIBS="-lc -lstdc++ -ld"
export LDFLAGS="-Wl,-rpath-link=-I${SYSROOT}/usr/lib -L${SYSROOT}/usr/lib -L${PREFIX}/lib -L${NDK_TOOLCHAIN}/lib"
</code></pre>
+<h2 id="compile-process">Compile Process</h2>
+
+<p>To compile seafile, we should compile ccnet and libsearpc first. As for these two projects, they all have their own dependencies, so we must follow some order to run the compilation.</p>
+
+<h3 id="libsearpc">libsearpc</h3>
+
+<h4 id="glib">glib</h4>
+
+<h5 id="libiconv">libiconv</h5>
+
+<h5 id="libffi">libffi</h5>
+
+<h5 id="gettext">gettext</h5>
+
+<h4 id="libjasson">libjasson</h4>
+
+<h3 id="ccnet">ccnet</h3>
+
+<h4 id="libuuid">libuuid</h4>
+
+<h3 id="seafile">seafile</h3>
+
<h2 id="preferences">Preferences</h2>
<ul>
diff --git a/tags/arm/index.xml b/tags/arm/index.xml
index 11f9f40..1c23145 100644
--- a/tags/arm/index.xml
+++ b/tags/arm/index.xml
@@ -25,16 +25,33 @@
<h2 id="pre-work">Pre-work</h2>
-<h3 id="tool-chain">Tool-Chain</h3>
-
<p>Basically, I used the native android compilation tool-chains, <a href="https://developer.android.com/ndk/downloads/index.html">Android NDK</a>, as working tools. Due to my working situation, I use a <a href="https://shield.nvidia.com/tablet/k1">Nvidia Shield Tablet</a> as target device. As <em>Zengwen</em> said in his <a href="http://zwyuan.github.io/2016/07/17/cross-compile-glib-for-android/">blog</a>, newest updated NDK might has some issue which can influence compilation progress. So you can find <a href="http://stackoverflow.com/questions/6849981/where-do-i-find-old-versions-of-android-ndk">other version</a> of NDK once you have some problems. Based on what <em>Zengwen’s</em> blog mentioned, we can write following useful system environment and export in terminal.</p>
+<h3 id="prerequisites">Prerequisites</h3>
+
+<pre><code>$ sudo apt-get install build-essential
+$ sudo apt-get install pkg-config automake autoconf libtool
+</code></pre>
+
+<h3 id="link-with-standalone-tool-chains">Link with standalone tool-chains</h3>
+
+<p>In order to build standalone tool-chains, we need first to export following system environment. After doing that, we can use following command to build a standalone tool-chains from downloaded NDK.
+ $ ${NDK}/build/tools/make-standalone-toolchain.sh <br />
+ –toolchain=arm-linux-androideabi-4.9 <br />
+ –stl=gnustl <br />
+ –arch=arm <br />
+ –ndk-dir=/home/moslab/Android/android-ndk-r12b <br />
+ –package-dir=/home/moslab/Android <br />
+ –install-dir=/home/moslab/Android/android-ndk-toolchain <br />
+ –platform=android-22</p>
+
<h3 id="original-system-environment-configuration">Original System Environment Configuration</h3>
-<pre><code>/# Android NDK sources and standalone toolchain is put here
-export DEV=~/Android/
+<p>[TODO]-> I will fix this part later.
+ /# Android NDK sources and standalone toolchain is put here
+ export DEV=~/Android/</p>
-/# All the built binaries, libs and their header will be installed here
+<pre><code>/# All the built binaries, libs and their header will be installed here
export PREFIX=/opt/android
/# Don't mix up .pc files from your host and build target
@@ -60,7 +77,7 @@ export ANDROID_TARGET=armv7-none-linux-androideabi
/# The cross-compile toolchain we use
export TOOLCHAIN=arm-linux-androideabi
-/# This is a symlink pointing to the real Android NDK r10e
+/# This is a symlink pointing to the real Android NDK r12b
export NDK=${DEV}/android-ndk
/# The path of standalone NDK toolchain
@@ -96,6 +113,28 @@ export LIBS="-lc -lstdc++ -ld"
export LDFLAGS="-Wl,-rpath-link=-I${SYSROOT}/usr/lib -L${SYSROOT}/usr/lib -L${PREFIX}/lib -L${NDK_TOOLCHAIN}/lib"
</code></pre>
+<h2 id="compile-process">Compile Process</h2>
+
+<p>To compile seafile, we should compile ccnet and libsearpc first. As for these two projects, they all have their own dependencies, so we must follow some order to run the compilation.</p>
+
+<h3 id="libsearpc">libsearpc</h3>
+
+<h4 id="glib">glib</h4>
+
+<h5 id="libiconv">libiconv</h5>
+
+<h5 id="libffi">libffi</h5>
+
+<h5 id="gettext">gettext</h5>
+
+<h4 id="libjasson">libjasson</h4>
+
+<h3 id="ccnet">ccnet</h3>
+
+<h4 id="libuuid">libuuid</h4>
+
+<h3 id="seafile">seafile</h3>
+
<h2 id="preferences">Preferences</h2>
<ul>
diff --git a/tags/github/index.xml b/tags/github/index.xml
index 975f967..8a53f88 100644
--- a/tags/github/index.xml
+++ b/tags/github/index.xml
@@ -27,12 +27,12 @@ Anyway, after coming back, I think I write too much on useless words, so let me
<h2 id="todo-list">TODO List</h2>
-<p>-[x] Test API
--[ ] Finish Walk Algorithm
--[ ] Finish other movement, etc. catch, hatch
--[ ] Smart Walking route
--[ ] Pokemon Predict (Thanks to Pokevision’s idea)
--[ ] Become a Pokemon Master</p>
+<p>-[ ] Test API
+-[ ] Finish Walk Algorithm
+-[ ] Finish other movement, etc. catch, hatch
+-[ ] Smart Walking route
+-[ ] Pokemon Predict (Thanks to Pokevision’s idea)
+-[ ] Become a Pokemon Master</p>
diff --git a/tags/hack/index.xml b/tags/hack/index.xml
index f9c071f..16717cc 100644
--- a/tags/hack/index.xml
+++ b/tags/hack/index.xml
@@ -27,12 +27,12 @@ Anyway, after coming back, I think I write too much on useless words, so let me
<h2 id="todo-list">TODO List</h2>
-<p>-[x] Test API
--[ ] Finish Walk Algorithm
--[ ] Finish other movement, etc. catch, hatch
--[ ] Smart Walking route
--[ ] Pokemon Predict (Thanks to Pokevision’s idea)
--[ ] Become a Pokemon Master</p>
+<p>-[ ] Test API
+-[ ] Finish Walk Algorithm
+-[ ] Finish other movement, etc. catch, hatch
+-[ ] Smart Walking route
+-[ ] Pokemon Predict (Thanks to Pokevision’s idea)
+-[ ] Become a Pokemon Master</p>