I'd like to compile ASE myself, and the compile article is very
limited. So I toss this discussion to make things clear. Maybe I could
contribute a better article while I conquer the compile process.
I'd like to confirm the pre-requirement of CompilingASE first.
Does the description in article means:
1. get android source (and make sure you can compile it to make agcc
work)
2. get android SDK (1.5r1 or 1.5r2 ...downloading)
3. run tools/fix_android_sdk.py to patch those 2 folders
Then I have to use eclipse on linux to build the ASE environment.
> I'd like to compile ASE myself, and the compile article is very
> limited. So I toss this discussion to make things clear. Maybe I could
> contribute a better article while I conquer the compile process.
> I'd like to confirm the pre-requirement of CompilingASE first.
> Does the description in article means:
> 1. get android source (and make sure you can compile it to make agcc
> work)
> 2. get android SDK (1.5r1 or 1.5r2 ...downloading)
> 3. run tools/fix_android_sdk.py to patch those 2 folders
> Then I have to use eclipse on linux to build the ASE environment.
> Are the descriptions right so far?
Hello,
I successfully compiled the ASE,
the above prerequisites are right (but you don't need to compile the
android source, since python and lua are precompiled),
the lost chain is specify the tts library path in eclipse.
On Wed, Jun 10, 2009 at 1:40 PM, gasolin <gaso...@gmail.com> wrote:
> > Hello,
> > I'd like to compile ASE myself, and the compile article is very
> > limited. So I toss this discussion to make things clear. Maybe I could
> > contribute a better article while I conquer the compile process.
> > According to CompilingASE articlehttp://
> code.google.com/p/android-scripting/wiki/CompilingASE
> > I'd like to confirm the pre-requirement of CompilingASE first.
> > Does the description in article means:
> > 1. get android source (and make sure you can compile it to make agcc
> > work)
> > 2. get android SDK (1.5r1 or 1.5r2 ...downloading)
> > 3. run tools/fix_android_sdk.py to patch those 2 folders
> > Then I have to use eclipse on linux to build the ASE environment.
> > Are the descriptions right so far?
> Hello,
> I successfully compiled the ASE,
> the above prerequisites are right (but you don't need to compile the
> android source, since python and lua are precompiled),
> the lost chain is specify the tts library path in eclipse.
Compiling ASE requires modifying the Android SDK slightly. A script is
provided to make this easier, but you'll need to download the Android
source. Assuming you install the source to mydroid and the sdk to
android-sdk, execute the script as follows.
$ cd android-scripting/tools
$ python fix_android_sdk.py mydroid android-sdk
In addition to modifying the SDK by adding android.os.Exec, the script
will also copy the source files into the SDK so that they can be
browsed in Eclipse.
Change the project build path and specify the TTS lib path to (project
path)/lib/(TTSxxxx.jar)
Compile it, done!
PS:
Python and Lua are precompiled and already put in res/raw folder. You
don't need to setup the cross compile environment unless you want to
also compile Lua and Python yourself.
--
I'd like to compile python myself, hope I can conquer it, too.
On Thu, Jun 11, 2009 at 2:49 AM, gasolin <gaso...@gmail.com> wrote:
> Damon,
> Here's a more organized doc for reference.
> Compiling ASE requires modifying the Android SDK slightly. A script is
> provided to make this easier, but you'll need to download the Android
> source. Assuming you install the source to mydroid and the sdk to
> android-sdk, execute the script as follows.
> == Prerequisites ==
> To compile ASE, you need
> 1. Get Android source (read http://source.android.com/download) and
> name the folder as 'mydroid'(or else you prefer)
> 2. Get Android SDK (download from http://developer.android.com/) and
> extract it as "android-sdk"(or else you prefer)
> 3. Get ASE source (http://code.google.com/p/android-scripting/source/ > checkout) as 'android-scripting'(or else you prefer)
> 4. Enter android-scripting/tools folder and execute fix_android_sdk.py
> to patch android-sdk
> $ cd android-scripting/tools
> $ python fix_android_sdk.py mydroid android-sdk
> In addition to modifying the SDK by adding android.os.Exec, the script
> will also copy the source files into the SDK so that they can be
> browsed in Eclipse.
> Change the project build path and specify the TTS lib path to (project
> path)/lib/(TTSxxxx.jar)
> Compile it, done!
> PS:
> Python and Lua are precompiled and already put in res/raw folder. You
> don't need to setup the cross compile environment unless you want to
> also compile Lua and Python yourself.
> --
> I'd like to compile python myself, hope I can conquer it, too.
> On Thu, Jun 11, 2009 at 2:49 AM, gasolin <gaso...@gmail.com> wrote:
> > Damon,
> > Here's a more organized doc for reference.
> > Compiling ASE requires modifying the Android SDK slightly. A script is
> > provided to make this easier, but you'll need to download the Android
> > source. Assuming you install the source to mydroid and the sdk to
> > android-sdk, execute the script as follows.
> > == Prerequisites ==
> > To compile ASE, you need
> > 1. Get Android source (readhttp://source.android.com/download) and
> > name the folder as 'mydroid'(or else you prefer)
> > 2. Get Android SDK (download fromhttp://developer.android.com/) and
> > extract it as "android-sdk"(or else you prefer)
> > 3. Get ASE source (http://code.google.com/p/android-scripting/source/ > > checkout) as 'android-scripting'(or else you prefer)
> > 4. Enter android-scripting/tools folder and execute fix_android_sdk.py
> > to patch android-sdk
> > In addition to modifying the SDK by adding android.os.Exec, the script
> > will also copy the source files into the SDK so that they can be
> > browsed in Eclipse.
> > Change the project build path and specify the TTS lib path to (project
> > path)/lib/(TTSxxxx.jar)
> > Compile it, done!
> > PS:
> > Python and Lua are precompiled and already put in res/raw folder. You
> > don't need to setup the cross compile environment unless you want to
> > also compile Lua and Python yourself.
> > --
> > I'd like to compile python myself, hope I can conquer it, too.
ASE makes use of android.os.Exec. The fix_android_sdk.py script that adds
the lib to the SDK will make it available to any other apps you're writing
that use the SDK as well.
On Fri, Jun 19, 2009 at 8:15 PM, Protocol-X <shawn.bur...@gmail.com> wrote:
> If you compile this code would you be able to sue the android.os.exec
> Lib?
> On Jun 11, 8:26 am, Damon <damonkoh...@gmail.com> wrote:
> > Thanks, that's very helpful.
> > On Thu, Jun 11, 2009 at 2:49 AM, gasolin <gaso...@gmail.com> wrote:
> > > Damon,
> > > Here's a more organized doc for reference.
> > > Compiling ASE requires modifying the Android SDK slightly. A script is
> > > provided to make this easier, but you'll need to download the Android
> > > source. Assuming you install the source to mydroid and the sdk to
> > > android-sdk, execute the script as follows.
> > > == Prerequisites ==
> > > To compile ASE, you need
> > > 1. Get Android source (readhttp://source.android.com/download) and
> > > name the folder as 'mydroid'(or else you prefer)
> > > 2. Get Android SDK (download fromhttp://developer.android.com/) and
> > > extract it as "android-sdk"(or else you prefer)
> > > 3. Get ASE source (http://code.google.com/p/android-scripting/source/ > > > checkout) as 'android-scripting'(or else you prefer)
> > > 4. Enter android-scripting/tools folder and execute fix_android_sdk.py
> > > to patch android-sdk
> > > In addition to modifying the SDK by adding android.os.Exec, the script
> > > will also copy the source files into the SDK so that they can be
> > > browsed in Eclipse.
> > > Change the project build path and specify the TTS lib path to (project
> > > path)/lib/(TTSxxxx.jar)
> > > Compile it, done!
> > > PS:
> > > Python and Lua are precompiled and already put in res/raw folder. You
> > > don't need to setup the cross compile environment unless you want to
> > > also compile Lua and Python yourself.
> > > --
> > > I'd like to compile python myself, hope I can conquer it, too.
Need linux though huh? Can use windows I'd assume. I actually made the exec file myself but when I went to install it didn't appear. Thanks though ill look into that
Date: Sat, 20 Jun 2009 17:26:58 To: <android-scripting@googlegroups.com>
Subject: Re: Compile question
ASE makes use of android.os.Exec. The fix_android_sdk.py script that adds
the lib to the SDK will make it available to any other apps you're writing
that use the SDK as well.
On Fri, Jun 19, 2009 at 8:15 PM, Protocol-X <shawn.bur...@gmail.com> wrote:
> If you compile this code would you be able to sue the android.os.exec
> Lib?
> On Jun 11, 8:26 am, Damon <damonkoh...@gmail.com> wrote:
> > Thanks, that's very helpful.
> > On Thu, Jun 11, 2009 at 2:49 AM, gasolin <gaso...@gmail.com> wrote:
> > > Damon,
> > > Here's a more organized doc for reference.
> > > Compiling ASE requires modifying the Android SDK slightly. A script is
> > > provided to make this easier, but you'll need to download the Android
> > > source. Assuming you install the source to mydroid and the sdk to
> > > android-sdk, execute the script as follows.
> > > == Prerequisites ==
> > > To compile ASE, you need
> > > 1. Get Android source (readhttp://source.android.com/download) and
> > > name the folder as 'mydroid'(or else you prefer)
> > > 2. Get Android SDK (download fromhttp://developer.android.com/) and
> > > extract it as "android-sdk"(or else you prefer)
> > > 3. Get ASE source (http://code.google.com/p/android-scripting/source/ > > > checkout) as 'android-scripting'(or else you prefer)
> > > 4. Enter android-scripting/tools folder and execute fix_android_sdk.py
> > > to patch android-sdk
> > > In addition to modifying the SDK by adding android.os.Exec, the script
> > > will also copy the source files into the SDK so that they can be
> > > browsed in Eclipse.
> > > Change the project build path and specify the TTS lib path to (project
> > > path)/lib/(TTSxxxx.jar)
> > > Compile it, done!
> > > PS:
> > > Python and Lua are precompiled and already put in res/raw folder. You
> > > don't need to setup the cross compile environment unless you want to
> > > also compile Lua and Python yourself.
> > > --
> > > I'd like to compile python myself, hope I can conquer it, too.
Is it possible to manually add it to the sdk? Anyone know
On Jun 20, 2009 11:27 AM, "Damon" <damonkoh...@gmail.com> wrote:
ASE makes use of android.os.Exec. The fix_android_sdk.py script that adds the lib to the SDK will make it available to any other apps you're writing that use the SDK as well.
On Fri, Jun 19, 2009 at 8:15 PM, Protocol-X <shawn.bur...@gmail.com> wrote: > > > If you compile t...
I'm not exactly sure what you mean. Are you referring to the android.os.Exec
class? To compile against it, you need to add it to the SDK, which the
fix_android_sdk.py script does. The class is already availble on the device
so any code compiled against will work as it should.
On Sat, Jun 20, 2009 at 5:39 PM, Shawn Burkit <shawn.bur...@gmail.com>wrote:
> Is it possible to manually add it to the sdk? Anyone know
> On Jun 20, 2009 11:27 AM, "Damon" <damonkoh...@gmail.com> wrote:
> ASE makes use of android.os.Exec. The fix_android_sdk.py script that adds
> the lib to the SDK will make it available to any other apps you're writing
> that use the SDK as well.
> On Fri, Jun 19, 2009 at 8:15 PM, Protocol-X <shawn.bur...@gmail.com>
> wrote: > > > If you compile t...
> http://www.damonkohler.com/
What I mean is I use windows not lunix so is there a way to get the already compiled version for windows since you cannot compile it yourself using windows
Date: Sat, 20 Jun 2009 18:05:10 To: <android-scripting@googlegroups.com>
Subject: Re: Compile question
I'm not exactly sure what you mean. Are you referring to the android.os.Exec
class? To compile against it, you need to add it to the SDK, which the
fix_android_sdk.py script does. The class is already availble on the device
so any code compiled against will work as it should.
On Sat, Jun 20, 2009 at 5:39 PM, Shawn Burkit <shawn.bur...@gmail.com>wrote:
> Is it possible to manually add it to the sdk? Anyone know
> On Jun 20, 2009 11:27 AM, "Damon" <damonkoh...@gmail.com> wrote:
> ASE makes use of android.os.Exec. The fix_android_sdk.py script that adds
> the lib to the SDK will make it available to any other apps you're writing
> that use the SDK as well.
> On Fri, Jun 19, 2009 at 8:15 PM, Protocol-X <shawn.bur...@gmail.com>
> wrote: > > > If you compile t...
> http://www.damonkohler.com/
On Sat, Jun 20, 2009 at 6:04 PM, Shawn <shawn.bur...@gmail.com> wrote:
> What I mean is I use windows not lunix so is there a way to get the already
> compiled version for windows since you cannot compile it yourself using
> windows
> ------------------------------
> *From*: Damon
> *Date*: Sat, 20 Jun 2009 18:05:10 +0200
> *To*: <android-scripting@googlegroups.com>
> *Subject*: Re: Compile question
> I'm not exactly sure what you mean. Are you referring to the
> android.os.Exec class? To compile against it, you need to add it to the SDK,
> which the fix_android_sdk.py script does. The class is already availble on
> the device so any code compiled against will work as it should.
> On Sat, Jun 20, 2009 at 5:39 PM, Shawn Burkit <shawn.bur...@gmail.com>wrote:
>> Is it possible to manually add it to the sdk? Anyone know
>> On Jun 20, 2009 11:27 AM, "Damon" <damonkoh...@gmail.com> wrote:
>> ASE makes use of android.os.Exec. The fix_android_sdk.py script that adds
>> the lib to the SDK will make it available to any other apps you're writing
>> that use the SDK as well.
>> On Fri, Jun 19, 2009 at 8:15 PM, Protocol-X <shawn.bur...@gmail.com>
>> wrote: > > > If you compile t...
>> http://www.damonkohler.com/
Date: Sat, 20 Jun 2009 18:07:59 To: <android-scripting@googlegroups.com>
Subject: Re: Compile question
It's a Java class. You can compile it using Windows. All you need is javac.
On Sat, Jun 20, 2009 at 6:04 PM, Shawn <shawn.bur...@gmail.com> wrote:
> What I mean is I use windows not lunix so is there a way to get the already
> compiled version for windows since you cannot compile it yourself using
> windows
> ------------------------------
> *From*: Damon
> *Date*: Sat, 20 Jun 2009 18:05:10 +0200
> *To*: <android-scripting@googlegroups.com>
> *Subject*: Re: Compile question
> I'm not exactly sure what you mean. Are you referring to the
> android.os.Exec class? To compile against it, you need to add it to the SDK,
> which the fix_android_sdk.py script does. The class is already availble on
> the device so any code compiled against will work as it should.
> On Sat, Jun 20, 2009 at 5:39 PM, Shawn Burkit <shawn.bur...@gmail.com>wrote:
>> Is it possible to manually add it to the sdk? Anyone know
>> On Jun 20, 2009 11:27 AM, "Damon" <damonkoh...@gmail.com> wrote:
>> ASE makes use of android.os.Exec. The fix_android_sdk.py script that adds
>> the lib to the SDK will make it available to any other apps you're writing
>> that use the SDK as well.
>> On Fri, Jun 19, 2009 at 8:15 PM, Protocol-X <shawn.bur...@gmail.com>
>> wrote: > > > If you compile t...
>> http://www.damonkohler.com/