Several thoughts/questions
Matt Richards
Been wondering a few things relating to android-x86, rather than
having several threads open I'll lump them all into one..
1) How often are test iso's released, what "milestones" need to be met
for any release? Think I saw something on the blog, but I'm not sure.
2) Eclair NDK - I've seen a couple binary releases for this, wondering
what is involved to get this built on my own? Is there a patch?
3) Android 2.0.1/2.1 - As we're on Ecliar how close are we to
following 2.1 or whatever the newewist is.. (are these numbers just
marketing)? Do we regularly sync to what Google pushes?
Thanks!
--
--Matt
Yi Sun
> Hey all,
> Been wondering a few things relating to android-x86, rather than
> having several threads open I'll lump them all into one..
>
> 1) How often are test iso's released, what "milestones" need to be met
> for any release? Think I saw something on the blog, but I'm not sure
two months (since we don't have full time developers, it is very hard
to maintain a accurate schedule). The changes in the Eclair relative
bigger, it takes longer time. We currently, shot on 01/15 for the
first Eclair test release. And we still having some issues with Bluz,
so the release may get delayed for a few days if we can not solve it
on time.
For each release, both Chih-wei and I will try to come up with some
TODO items for the release. It is more or less worked as the
milestones for each release.
> 2) Eclair NDK - I've seen a couple binary releases for this, wondering
> what is involved to get this built on my own? Is there a patch?
NDK in developement/ndk/build then you have it. Since we have already
fixed the NDK code, there are no special requirements for building
x86 ndk
> 3) Android 2.0.1/2.1 - As we're on Ecliar how close are we to
> following 2.1 or whatever the newewist is.. (are these numbers just
> marketing)? Do we regularly sync to what Google pushes?
moment, AOSP only has 2.0(Eclair)
>
> Thanks!
> --
> --Matt
>
> --
> You received this message because you are subscribed to the Google Groups "Android-x86" group.
> To post to this group, send email to andro...@googlegroups.com.
> To unsubscribe from this group, send email to android-x86...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.
>
>
>
>
--
Android-x86
http://www.android-x86.org
Matt Richards
> On Wed, Jan 13, 2010 at 1:37 PM, Matt Richards <mric...@gmail.com> wrote:
>> Hey all,
>> Been wondering a few things relating to android-x86, rather than
>> having several threads open I'll lump them all into one..
>>
>> 1) How often are test iso's released, what "milestones" need to be met
>> for any release? Think I saw something on the blog, but I'm not sure
> So far, we have been able to maintain a release cycle of every one or
> two months (since we don't have full time developers, it is very hard
> to maintain a accurate schedule). The changes in the Eclair relative
> bigger, it takes longer time. We currently, shot on 01/15 for the
> first Eclair test release. And we still having some issues with Bluz,
> so the release may get delayed for a few days if we can not solve it
> on time.
> For each release, both Chih-wei and I will try to come up with some
> TODO items for the release. It is more or less worked as the
> milestones for each release.
>> 2) Eclair NDK - I've seen a couple binary releases for this, wondering
>> what is involved to get this built on my own? Is there a patch?
> Very simple, just copy the toolchains into the prebuild directory of
> NDK in developement/ndk/build then you have it. Since we have already
> fixed the NDK code, there are no special requirements for building
> x86 ndk
And from where?
>> 3) Android 2.0.1/2.1 - As we're on Ecliar how close are we to
>> following 2.1 or whatever the newewist is.. (are these numbers just
>> marketing)? Do we regularly sync to what Google pushes?
> What are trying to keep up with AOSP as close as possible. At the
> moment, AOSP only has 2.0(Eclair)
Google doesn't directly commit to the public repos, they spuraticly
submit snapshots right? So.. 2.0.1/2.1 are still in thier private
repos? According to my Google skills, 2.0.1 (Presume 2.0.1 was just
some tiny patches) /2.1 seem to come from Eclair, but I'm a tad
confused.
>>
>> Thanks!
>> --
>> --Matt
>>
>> --
>> You received this message because you are subscribed to the Google Groups "Android-x86" group.
>> To post to this group, send email to andro...@googlegroups.com.
>> To unsubscribe from this group, send email to android-x86...@googlegroups.com.
>> For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.
>>
>>
>>
>>
>
>
>
> --
> Android-x86
> http://www.android-x86.org
>
> --
> You received this message because you are subscribed to the Google Groups "Android-x86" group.
> To post to this group, send email to andro...@googlegroups.com.
> To unsubscribe from this group, send email to android-x86...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.
>
>
>
>
--
--Matt
Yi Sun
>>> 3) Android 2.0.1/2.1 - As we're on Ecliar how close are we to
>>> following 2.1 or whatever the newewist is.. (are these numbers just
>>> marketing)? Do we regularly sync to what Google pushes?
>> What are trying to keep up with AOSP as close as possible. At the
>> moment, AOSP only has 2.0(Eclair)
> Google doesn't directly commit to the public repos, they spuraticly
> submit snapshots right? So.. 2.0.1/2.1 are still in thier private
> repos?
> According to my Google skills, 2.0.1 (Presume 2.0.1 was just
> some tiny patches) /2.1 seem to come from Eclair, but I'm a tad
> confused.
Matt Richards
to prebuilt/linux-x86 in the NDK folder..
but the host setup script says it cannot find any binaries for my system..
Matt Richards
--
--Matt