haopengzhan/CoderSherlock.github.io
1
0
Fork 0
mirror of https://github.com/CoderSherlock/CoderSherlock.github.io.git synced 2026-06-13 08:08:10 -07:00
Code Issues Packages Projects Releases Wiki Activity

ARM_Update&Pokemon_Pause

Browse Source
This commit is contained in:
CoderSherlock
2016-08-04 17:39:36 -04:00
parent b8ec4e14d0
commit 1c8a7f61de
9 changed files with 306 additions and 72 deletions
Download Patch File Download Diff File Expand all files Collapse all files
categories/2016_07/index.xml
+46 -7
View File
@@ -27,7 +27,7 @@ Anyway, after coming back, I think I write too much on useless words, so let me
<h2 id="todo-list">TODO List</h2> <h2 id="todo-list">TODO List</h2>
<p>-[x] Test API <p>-[ ] Test API
-[ ] Finish Walk Algorithm -[ ] Finish Walk Algorithm
-[ ] Finish other movement, etc. catch, hatch -[ ] Finish other movement, etc. catch, hatch
-[ ] Smart Walking route -[ ] Smart Walking route
@@ -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> <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> <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> <h3 id="original-system-environment-configuration">Original System Environment Configuration</h3>
<pre><code>/# Android NDK sources and standalone toolchain is put here <p>[TODO]-> I will fix this part later.
export DEV=~/Android/ /# 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 export PREFIX=/opt/android
/# Don't mix up .pc files from your host and build target /# 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 /# The cross-compile toolchain we use
export TOOLCHAIN=arm-linux-androideabi 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 export NDK=${DEV}/android-ndk
/# The path of standalone NDK toolchain /# 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" export LDFLAGS="-Wl,-rpath-link=-I${SYSROOT}/usr/lib -L${SYSROOT}/usr/lib -L${PREFIX}/lib -L${NDK_TOOLCHAIN}/lib"
</code></pre> </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> <h2 id="preferences">Preferences</h2>
<ul> <ul>
index.xml
+46 -7
View File
@@ -27,7 +27,7 @@ Anyway, after coming back, I think I write too much on useless words, so let me
<h2 id="todo-list">TODO List</h2> <h2 id="todo-list">TODO List</h2>
<p>-[x] Test API <p>-[ ] Test API
-[ ] Finish Walk Algorithm -[ ] Finish Walk Algorithm
-[ ] Finish other movement, etc. catch, hatch -[ ] Finish other movement, etc. catch, hatch
-[ ] Smart Walking route -[ ] Smart Walking route
@@ -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> <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> <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> <h3 id="original-system-environment-configuration">Original System Environment Configuration</h3>
<pre><code>/# Android NDK sources and standalone toolchain is put here <p>[TODO]-> I will fix this part later.
export DEV=~/Android/ /# 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 export PREFIX=/opt/android
/# Don't mix up .pc files from your host and build target /# 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 /# The cross-compile toolchain we use
export TOOLCHAIN=arm-linux-androideabi 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 export NDK=${DEV}/android-ndk
/# The path of standalone NDK toolchain /# 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" export LDFLAGS="-Wl,-rpath-link=-I${SYSROOT}/usr/lib -L${SYSROOT}/usr/lib -L${PREFIX}/lib -L${NDK_TOOLCHAIN}/lib"
</code></pre> </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> <h2 id="preferences">Preferences</h2>
<ul> <ul>
post/Cross-Compile-Seafile-2-ARM/index.html
+45 -6
View File
@@ -98,16 +98,33 @@
<h2 id="pre-work">Pre-work</h2> <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&rsquo;s</em> blog mentioned, we can write following useful system environment and export in terminal.</p> <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&rsquo;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 />
&ndash;toolchain=arm-linux-androideabi-4.9 <br />
&ndash;stl=gnustl <br />
&ndash;arch=arm <br />
&ndash;ndk-dir=/home/moslab/Android/android-ndk-r12b <br />
&ndash;package-dir=/home/moslab/Android <br />
&ndash;install-dir=/home/moslab/Android/android-ndk-toolchain <br />
&ndash;platform=android-22</p>
<h3 id="original-system-environment-configuration">Original System Environment Configuration</h3> <h3 id="original-system-environment-configuration">Original System Environment Configuration</h3>
<pre><code>/# Android NDK sources and standalone toolchain is put here <p>[TODO]-&gt; I will fix this part later.
export DEV=~/Android/ /# 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 export PREFIX=/opt/android
/# Don't mix up .pc files from your host and build target /# 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 /# The cross-compile toolchain we use
export TOOLCHAIN=arm-linux-androideabi 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 export NDK=${DEV}/android-ndk
/# The path of standalone NDK toolchain /# The path of standalone NDK toolchain
@@ -169,6 +186,28 @@ export LIBS=&quot;-lc -lstdc++ -ld&quot;
export LDFLAGS=&quot;-Wl,-rpath-link=-I${SYSROOT}/usr/lib -L${SYSROOT}/usr/lib -L${PREFIX}/lib -L${NDK_TOOLCHAIN}/lib&quot; export LDFLAGS=&quot;-Wl,-rpath-link=-I${SYSROOT}/usr/lib -L${SYSROOT}/usr/lib -L${PREFIX}/lib -L${NDK_TOOLCHAIN}/lib&quot;
</code></pre> </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> <h2 id="preferences">Preferences</h2>
<ul> <ul>
post/Pokemon-Go-Hack/index.html
+1 -1
View File
@@ -100,7 +100,7 @@ Anyway, after coming back, I think I write too much on useless words, so let me
<h2 id="todo-list">TODO List</h2> <h2 id="todo-list">TODO List</h2>
<p>-[x] Test API <p>-[ ] Test API
-[ ] Finish Walk Algorithm -[ ] Finish Walk Algorithm
-[ ] Finish other movement, etc. catch, hatch -[ ] Finish other movement, etc. catch, hatch
-[ ] Smart Walking route -[ ] Smart Walking route
post/index.xml
+46 -7
View File
@@ -27,7 +27,7 @@ Anyway, after coming back, I think I write too much on useless words, so let me
&lt;h2 id=&#34;todo-list&#34;&gt;TODO List&lt;/h2&gt; &lt;h2 id=&#34;todo-list&#34;&gt;TODO List&lt;/h2&gt;
&lt;p&gt;-[x] Test API &lt;p&gt;-[ ] Test API
-[ ] Finish Walk Algorithm -[ ] Finish Walk Algorithm
-[ ] Finish other movement, etc. catch, hatch -[ ] Finish other movement, etc. catch, hatch
-[ ] Smart Walking route -[ ] Smart Walking route
@@ -52,16 +52,33 @@ Anyway, after coming back, I think I write too much on useless words, so let me
&lt;h2 id=&#34;pre-work&#34;&gt;Pre-work&lt;/h2&gt; &lt;h2 id=&#34;pre-work&#34;&gt;Pre-work&lt;/h2&gt;
&lt;h3 id=&#34;tool-chain&#34;&gt;Tool-Chain&lt;/h3&gt;
&lt;p&gt;Basically, I used the native android compilation tool-chains, &lt;a href=&#34;https://developer.android.com/ndk/downloads/index.html&#34;&gt;Android NDK&lt;/a&gt;, as working tools. Due to my working situation, I use a &lt;a href=&#34;https://shield.nvidia.com/tablet/k1&#34;&gt;Nvidia Shield Tablet&lt;/a&gt; as target device. As &lt;em&gt;Zengwen&lt;/em&gt; said in his &lt;a href=&#34;http://zwyuan.github.io/2016/07/17/cross-compile-glib-for-android/&#34;&gt;blog&lt;/a&gt;, newest updated NDK might has some issue which can influence compilation progress. So you can find &lt;a href=&#34;http://stackoverflow.com/questions/6849981/where-do-i-find-old-versions-of-android-ndk&#34;&gt;other version&lt;/a&gt; of NDK once you have some problems. Based on what &lt;em&gt;Zengwen&amp;rsquo;s&lt;/em&gt; blog mentioned, we can write following useful system environment and export in terminal.&lt;/p&gt; &lt;p&gt;Basically, I used the native android compilation tool-chains, &lt;a href=&#34;https://developer.android.com/ndk/downloads/index.html&#34;&gt;Android NDK&lt;/a&gt;, as working tools. Due to my working situation, I use a &lt;a href=&#34;https://shield.nvidia.com/tablet/k1&#34;&gt;Nvidia Shield Tablet&lt;/a&gt; as target device. As &lt;em&gt;Zengwen&lt;/em&gt; said in his &lt;a href=&#34;http://zwyuan.github.io/2016/07/17/cross-compile-glib-for-android/&#34;&gt;blog&lt;/a&gt;, newest updated NDK might has some issue which can influence compilation progress. So you can find &lt;a href=&#34;http://stackoverflow.com/questions/6849981/where-do-i-find-old-versions-of-android-ndk&#34;&gt;other version&lt;/a&gt; of NDK once you have some problems. Based on what &lt;em&gt;Zengwen&amp;rsquo;s&lt;/em&gt; blog mentioned, we can write following useful system environment and export in terminal.&lt;/p&gt;
&lt;h3 id=&#34;prerequisites&#34;&gt;Prerequisites&lt;/h3&gt;
&lt;pre&gt;&lt;code&gt;$ sudo apt-get install build-essential
$ sudo apt-get install pkg-config automake autoconf libtool
&lt;/code&gt;&lt;/pre&gt;
&lt;h3 id=&#34;link-with-standalone-tool-chains&#34;&gt;Link with standalone tool-chains&lt;/h3&gt;
&lt;p&gt;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 &lt;br /&gt;
&amp;ndash;toolchain=arm-linux-androideabi-4.9 &lt;br /&gt;
&amp;ndash;stl=gnustl &lt;br /&gt;
&amp;ndash;arch=arm &lt;br /&gt;
&amp;ndash;ndk-dir=/home/moslab/Android/android-ndk-r12b &lt;br /&gt;
&amp;ndash;package-dir=/home/moslab/Android &lt;br /&gt;
&amp;ndash;install-dir=/home/moslab/Android/android-ndk-toolchain &lt;br /&gt;
&amp;ndash;platform=android-22&lt;/p&gt;
&lt;h3 id=&#34;original-system-environment-configuration&#34;&gt;Original System Environment Configuration&lt;/h3&gt; &lt;h3 id=&#34;original-system-environment-configuration&#34;&gt;Original System Environment Configuration&lt;/h3&gt;
&lt;pre&gt;&lt;code&gt;/# Android NDK sources and standalone toolchain is put here &lt;p&gt;[TODO]-&amp;gt; I will fix this part later.
export DEV=~/Android/ /# Android NDK sources and standalone toolchain is put here
export DEV=~/Android/&lt;/p&gt;
/# All the built binaries, libs and their header will be installed here &lt;pre&gt;&lt;code&gt;/# All the built binaries, libs and their header will be installed here
export PREFIX=/opt/android export PREFIX=/opt/android
/# Don&#39;t mix up .pc files from your host and build target /# Don&#39;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 /# The cross-compile toolchain we use
export TOOLCHAIN=arm-linux-androideabi 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 export NDK=${DEV}/android-ndk
/# The path of standalone NDK toolchain /# The path of standalone NDK toolchain
@@ -123,6 +140,28 @@ export LIBS=&amp;quot;-lc -lstdc++ -ld&amp;quot;
export LDFLAGS=&amp;quot;-Wl,-rpath-link=-I${SYSROOT}/usr/lib -L${SYSROOT}/usr/lib -L${PREFIX}/lib -L${NDK_TOOLCHAIN}/lib&amp;quot; export LDFLAGS=&amp;quot;-Wl,-rpath-link=-I${SYSROOT}/usr/lib -L${SYSROOT}/usr/lib -L${PREFIX}/lib -L${NDK_TOOLCHAIN}/lib&amp;quot;
&lt;/code&gt;&lt;/pre&gt; &lt;/code&gt;&lt;/pre&gt;
&lt;h2 id=&#34;compile-process&#34;&gt;Compile Process&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3 id=&#34;libsearpc&#34;&gt;libsearpc&lt;/h3&gt;
&lt;h4 id=&#34;glib&#34;&gt;glib&lt;/h4&gt;
&lt;h5 id=&#34;libiconv&#34;&gt;libiconv&lt;/h5&gt;
&lt;h5 id=&#34;libffi&#34;&gt;libffi&lt;/h5&gt;
&lt;h5 id=&#34;gettext&#34;&gt;gettext&lt;/h5&gt;
&lt;h4 id=&#34;libjasson&#34;&gt;libjasson&lt;/h4&gt;
&lt;h3 id=&#34;ccnet&#34;&gt;ccnet&lt;/h3&gt;
&lt;h4 id=&#34;libuuid&#34;&gt;libuuid&lt;/h4&gt;
&lt;h3 id=&#34;seafile&#34;&gt;seafile&lt;/h3&gt;
&lt;h2 id=&#34;preferences&#34;&gt;Preferences&lt;/h2&gt; &lt;h2 id=&#34;preferences&#34;&gt;Preferences&lt;/h2&gt;
&lt;ul&gt; &lt;ul&gt;
tags/android/index.xml
+45 -6
View File
@@ -25,16 +25,33 @@
&lt;h2 id=&#34;pre-work&#34;&gt;Pre-work&lt;/h2&gt; &lt;h2 id=&#34;pre-work&#34;&gt;Pre-work&lt;/h2&gt;
&lt;h3 id=&#34;tool-chain&#34;&gt;Tool-Chain&lt;/h3&gt;
&lt;p&gt;Basically, I used the native android compilation tool-chains, &lt;a href=&#34;https://developer.android.com/ndk/downloads/index.html&#34;&gt;Android NDK&lt;/a&gt;, as working tools. Due to my working situation, I use a &lt;a href=&#34;https://shield.nvidia.com/tablet/k1&#34;&gt;Nvidia Shield Tablet&lt;/a&gt; as target device. As &lt;em&gt;Zengwen&lt;/em&gt; said in his &lt;a href=&#34;http://zwyuan.github.io/2016/07/17/cross-compile-glib-for-android/&#34;&gt;blog&lt;/a&gt;, newest updated NDK might has some issue which can influence compilation progress. So you can find &lt;a href=&#34;http://stackoverflow.com/questions/6849981/where-do-i-find-old-versions-of-android-ndk&#34;&gt;other version&lt;/a&gt; of NDK once you have some problems. Based on what &lt;em&gt;Zengwen&amp;rsquo;s&lt;/em&gt; blog mentioned, we can write following useful system environment and export in terminal.&lt;/p&gt; &lt;p&gt;Basically, I used the native android compilation tool-chains, &lt;a href=&#34;https://developer.android.com/ndk/downloads/index.html&#34;&gt;Android NDK&lt;/a&gt;, as working tools. Due to my working situation, I use a &lt;a href=&#34;https://shield.nvidia.com/tablet/k1&#34;&gt;Nvidia Shield Tablet&lt;/a&gt; as target device. As &lt;em&gt;Zengwen&lt;/em&gt; said in his &lt;a href=&#34;http://zwyuan.github.io/2016/07/17/cross-compile-glib-for-android/&#34;&gt;blog&lt;/a&gt;, newest updated NDK might has some issue which can influence compilation progress. So you can find &lt;a href=&#34;http://stackoverflow.com/questions/6849981/where-do-i-find-old-versions-of-android-ndk&#34;&gt;other version&lt;/a&gt; of NDK once you have some problems. Based on what &lt;em&gt;Zengwen&amp;rsquo;s&lt;/em&gt; blog mentioned, we can write following useful system environment and export in terminal.&lt;/p&gt;
&lt;h3 id=&#34;prerequisites&#34;&gt;Prerequisites&lt;/h3&gt;
&lt;pre&gt;&lt;code&gt;$ sudo apt-get install build-essential
$ sudo apt-get install pkg-config automake autoconf libtool
&lt;/code&gt;&lt;/pre&gt;
&lt;h3 id=&#34;link-with-standalone-tool-chains&#34;&gt;Link with standalone tool-chains&lt;/h3&gt;
&lt;p&gt;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 &lt;br /&gt;
&amp;ndash;toolchain=arm-linux-androideabi-4.9 &lt;br /&gt;
&amp;ndash;stl=gnustl &lt;br /&gt;
&amp;ndash;arch=arm &lt;br /&gt;
&amp;ndash;ndk-dir=/home/moslab/Android/android-ndk-r12b &lt;br /&gt;
&amp;ndash;package-dir=/home/moslab/Android &lt;br /&gt;
&amp;ndash;install-dir=/home/moslab/Android/android-ndk-toolchain &lt;br /&gt;
&amp;ndash;platform=android-22&lt;/p&gt;
&lt;h3 id=&#34;original-system-environment-configuration&#34;&gt;Original System Environment Configuration&lt;/h3&gt; &lt;h3 id=&#34;original-system-environment-configuration&#34;&gt;Original System Environment Configuration&lt;/h3&gt;
&lt;pre&gt;&lt;code&gt;/# Android NDK sources and standalone toolchain is put here &lt;p&gt;[TODO]-&amp;gt; I will fix this part later.
export DEV=~/Android/ /# Android NDK sources and standalone toolchain is put here
export DEV=~/Android/&lt;/p&gt;
/# All the built binaries, libs and their header will be installed here &lt;pre&gt;&lt;code&gt;/# All the built binaries, libs and their header will be installed here
export PREFIX=/opt/android export PREFIX=/opt/android
/# Don&#39;t mix up .pc files from your host and build target /# Don&#39;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 /# The cross-compile toolchain we use
export TOOLCHAIN=arm-linux-androideabi 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 export NDK=${DEV}/android-ndk
/# The path of standalone NDK toolchain /# The path of standalone NDK toolchain
@@ -96,6 +113,28 @@ export LIBS=&amp;quot;-lc -lstdc++ -ld&amp;quot;
export LDFLAGS=&amp;quot;-Wl,-rpath-link=-I${SYSROOT}/usr/lib -L${SYSROOT}/usr/lib -L${PREFIX}/lib -L${NDK_TOOLCHAIN}/lib&amp;quot; export LDFLAGS=&amp;quot;-Wl,-rpath-link=-I${SYSROOT}/usr/lib -L${SYSROOT}/usr/lib -L${PREFIX}/lib -L${NDK_TOOLCHAIN}/lib&amp;quot;
&lt;/code&gt;&lt;/pre&gt; &lt;/code&gt;&lt;/pre&gt;
&lt;h2 id=&#34;compile-process&#34;&gt;Compile Process&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3 id=&#34;libsearpc&#34;&gt;libsearpc&lt;/h3&gt;
&lt;h4 id=&#34;glib&#34;&gt;glib&lt;/h4&gt;
&lt;h5 id=&#34;libiconv&#34;&gt;libiconv&lt;/h5&gt;
&lt;h5 id=&#34;libffi&#34;&gt;libffi&lt;/h5&gt;
&lt;h5 id=&#34;gettext&#34;&gt;gettext&lt;/h5&gt;
&lt;h4 id=&#34;libjasson&#34;&gt;libjasson&lt;/h4&gt;
&lt;h3 id=&#34;ccnet&#34;&gt;ccnet&lt;/h3&gt;
&lt;h4 id=&#34;libuuid&#34;&gt;libuuid&lt;/h4&gt;
&lt;h3 id=&#34;seafile&#34;&gt;seafile&lt;/h3&gt;
&lt;h2 id=&#34;preferences&#34;&gt;Preferences&lt;/h2&gt; &lt;h2 id=&#34;preferences&#34;&gt;Preferences&lt;/h2&gt;
&lt;ul&gt; &lt;ul&gt;
tags/arm/index.xml
+45 -6
View File
@@ -25,16 +25,33 @@
&lt;h2 id=&#34;pre-work&#34;&gt;Pre-work&lt;/h2&gt; &lt;h2 id=&#34;pre-work&#34;&gt;Pre-work&lt;/h2&gt;
&lt;h3 id=&#34;tool-chain&#34;&gt;Tool-Chain&lt;/h3&gt;
&lt;p&gt;Basically, I used the native android compilation tool-chains, &lt;a href=&#34;https://developer.android.com/ndk/downloads/index.html&#34;&gt;Android NDK&lt;/a&gt;, as working tools. Due to my working situation, I use a &lt;a href=&#34;https://shield.nvidia.com/tablet/k1&#34;&gt;Nvidia Shield Tablet&lt;/a&gt; as target device. As &lt;em&gt;Zengwen&lt;/em&gt; said in his &lt;a href=&#34;http://zwyuan.github.io/2016/07/17/cross-compile-glib-for-android/&#34;&gt;blog&lt;/a&gt;, newest updated NDK might has some issue which can influence compilation progress. So you can find &lt;a href=&#34;http://stackoverflow.com/questions/6849981/where-do-i-find-old-versions-of-android-ndk&#34;&gt;other version&lt;/a&gt; of NDK once you have some problems. Based on what &lt;em&gt;Zengwen&amp;rsquo;s&lt;/em&gt; blog mentioned, we can write following useful system environment and export in terminal.&lt;/p&gt; &lt;p&gt;Basically, I used the native android compilation tool-chains, &lt;a href=&#34;https://developer.android.com/ndk/downloads/index.html&#34;&gt;Android NDK&lt;/a&gt;, as working tools. Due to my working situation, I use a &lt;a href=&#34;https://shield.nvidia.com/tablet/k1&#34;&gt;Nvidia Shield Tablet&lt;/a&gt; as target device. As &lt;em&gt;Zengwen&lt;/em&gt; said in his &lt;a href=&#34;http://zwyuan.github.io/2016/07/17/cross-compile-glib-for-android/&#34;&gt;blog&lt;/a&gt;, newest updated NDK might has some issue which can influence compilation progress. So you can find &lt;a href=&#34;http://stackoverflow.com/questions/6849981/where-do-i-find-old-versions-of-android-ndk&#34;&gt;other version&lt;/a&gt; of NDK once you have some problems. Based on what &lt;em&gt;Zengwen&amp;rsquo;s&lt;/em&gt; blog mentioned, we can write following useful system environment and export in terminal.&lt;/p&gt;
&lt;h3 id=&#34;prerequisites&#34;&gt;Prerequisites&lt;/h3&gt;
&lt;pre&gt;&lt;code&gt;$ sudo apt-get install build-essential
$ sudo apt-get install pkg-config automake autoconf libtool
&lt;/code&gt;&lt;/pre&gt;
&lt;h3 id=&#34;link-with-standalone-tool-chains&#34;&gt;Link with standalone tool-chains&lt;/h3&gt;
&lt;p&gt;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 &lt;br /&gt;
&amp;ndash;toolchain=arm-linux-androideabi-4.9 &lt;br /&gt;
&amp;ndash;stl=gnustl &lt;br /&gt;
&amp;ndash;arch=arm &lt;br /&gt;
&amp;ndash;ndk-dir=/home/moslab/Android/android-ndk-r12b &lt;br /&gt;
&amp;ndash;package-dir=/home/moslab/Android &lt;br /&gt;
&amp;ndash;install-dir=/home/moslab/Android/android-ndk-toolchain &lt;br /&gt;
&amp;ndash;platform=android-22&lt;/p&gt;
&lt;h3 id=&#34;original-system-environment-configuration&#34;&gt;Original System Environment Configuration&lt;/h3&gt; &lt;h3 id=&#34;original-system-environment-configuration&#34;&gt;Original System Environment Configuration&lt;/h3&gt;
&lt;pre&gt;&lt;code&gt;/# Android NDK sources and standalone toolchain is put here &lt;p&gt;[TODO]-&amp;gt; I will fix this part later.
export DEV=~/Android/ /# Android NDK sources and standalone toolchain is put here
export DEV=~/Android/&lt;/p&gt;
/# All the built binaries, libs and their header will be installed here &lt;pre&gt;&lt;code&gt;/# All the built binaries, libs and their header will be installed here
export PREFIX=/opt/android export PREFIX=/opt/android
/# Don&#39;t mix up .pc files from your host and build target /# Don&#39;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 /# The cross-compile toolchain we use
export TOOLCHAIN=arm-linux-androideabi 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 export NDK=${DEV}/android-ndk
/# The path of standalone NDK toolchain /# The path of standalone NDK toolchain
@@ -96,6 +113,28 @@ export LIBS=&amp;quot;-lc -lstdc++ -ld&amp;quot;
export LDFLAGS=&amp;quot;-Wl,-rpath-link=-I${SYSROOT}/usr/lib -L${SYSROOT}/usr/lib -L${PREFIX}/lib -L${NDK_TOOLCHAIN}/lib&amp;quot; export LDFLAGS=&amp;quot;-Wl,-rpath-link=-I${SYSROOT}/usr/lib -L${SYSROOT}/usr/lib -L${PREFIX}/lib -L${NDK_TOOLCHAIN}/lib&amp;quot;
&lt;/code&gt;&lt;/pre&gt; &lt;/code&gt;&lt;/pre&gt;
&lt;h2 id=&#34;compile-process&#34;&gt;Compile Process&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3 id=&#34;libsearpc&#34;&gt;libsearpc&lt;/h3&gt;
&lt;h4 id=&#34;glib&#34;&gt;glib&lt;/h4&gt;
&lt;h5 id=&#34;libiconv&#34;&gt;libiconv&lt;/h5&gt;
&lt;h5 id=&#34;libffi&#34;&gt;libffi&lt;/h5&gt;
&lt;h5 id=&#34;gettext&#34;&gt;gettext&lt;/h5&gt;
&lt;h4 id=&#34;libjasson&#34;&gt;libjasson&lt;/h4&gt;
&lt;h3 id=&#34;ccnet&#34;&gt;ccnet&lt;/h3&gt;
&lt;h4 id=&#34;libuuid&#34;&gt;libuuid&lt;/h4&gt;
&lt;h3 id=&#34;seafile&#34;&gt;seafile&lt;/h3&gt;
&lt;h2 id=&#34;preferences&#34;&gt;Preferences&lt;/h2&gt; &lt;h2 id=&#34;preferences&#34;&gt;Preferences&lt;/h2&gt;
&lt;ul&gt; &lt;ul&gt;
tags/github/index.xml
+1 -1
View File
@@ -27,7 +27,7 @@ Anyway, after coming back, I think I write too much on useless words, so let me
&lt;h2 id=&#34;todo-list&#34;&gt;TODO List&lt;/h2&gt; &lt;h2 id=&#34;todo-list&#34;&gt;TODO List&lt;/h2&gt;
&lt;p&gt;-[x] Test API &lt;p&gt;-[ ] Test API
-[ ] Finish Walk Algorithm -[ ] Finish Walk Algorithm
-[ ] Finish other movement, etc. catch, hatch -[ ] Finish other movement, etc. catch, hatch
-[ ] Smart Walking route -[ ] Smart Walking route
tags/hack/index.xml
+1 -1
View File
@@ -27,7 +27,7 @@ Anyway, after coming back, I think I write too much on useless words, so let me
&lt;h2 id=&#34;todo-list&#34;&gt;TODO List&lt;/h2&gt; &lt;h2 id=&#34;todo-list&#34;&gt;TODO List&lt;/h2&gt;
&lt;p&gt;-[x] Test API &lt;p&gt;-[ ] Test API
-[ ] Finish Walk Algorithm -[ ] Finish Walk Algorithm
-[ ] Finish other movement, etc. catch, hatch -[ ] Finish other movement, etc. catch, hatch
-[ ] Smart Walking route -[ ] Smart Walking route