Re: documentaion building for android

[Mike Rosset <mike rosset gmail com>]

Lionel that patch was as exactly what I needed . Ok looks like I have
what I need to start a README or something of sorts. If I have
problems I'll post to the list but I think with theses patches I'll be
ok.

On Mon, Dec 17, 2012 at 1:18 PM, Lionel Landwerlin
<llandwerlin gmail com> wrote:
> Yes indeed the libiconv config.guess doesn't recognize the android canonical
> host name.
> This script is basically full of switch/case trying to match names like
> theses :
>
> | -mingw32* | -linux-gnu*
>
> Basically what you need to do is add the -linux-android* to that, so you can
> run the script.
>
> You can find the packages we patched and the patches there :
> http://vps10963.ovh.net/~djdeath/android-clutter/patches/
> (Not all of the patches might be useful for you)
>
> -Lionel
>
>
> On 17/12/12 21:03, Mike Rosset wrote:
>
> Thanks for the reply Lionel.
>
> I forgot to mention that you probably need to use the following repos :
>
> Few patches to glib to compile on Bionic :
> https://github.com/djdeath/glib
>
> Integration with the Android mainloop system :
> https://github.com/dlespiau/glib-android
>
> A few patches to cogl, most of them should be upstream now :
> https://github.com/djdeath/cogl-android
>
> Ok looks like I was on the right path here, but the distinction
> between glib and glib-android had me a bit confused. thanks
>
> I did run into a snag building both glib though. Related to libiconv
> haveing an outdated config.guess. Looks like libiconv's git repos  is
> using an outdated autoconf and friends so I'll play with that unless
> you guys have a better work around?
>
>
> How close is it from upstream? That's hard to say, because it might require
> a bit of time to investigate the remaining bugs.
> Also the whole Android application life cycle and the mainloop integration
> don't really fit with the way we do things on more traditional GNU/Linux
> systems...
>
> Ironically the whole mainloop is exactly the reason I started playing
> with clutter. Mainly because we have this exact same problem with go
> language. Since go language can not produce share libs, there is
> simply no way other then some IPC or RPC to use it in  some graphical
> way with android. On the flip side if you want to build a command line
> posix program for android with go. its pretty trivial.
>
> Even though the mainloop is pita, I still think clutter in theory, is
> one of the only open source alternatives that can probably get away
> with using it.
>
> As for things getting pushed upstream, I'm not to worried about that
> as long as I know which repo's are which and that they are tracking
> upstream.
>
> Regards,
>
> Mike
> _______________________________________________
> clutter-list mailing list
> clutter-list gnome org
> https://mail.gnome.org/mailman/listinfo/clutter-list
>
>
>
> _______________________________________________
> clutter-list mailing list
> clutter-list gnome org
> https://mail.gnome.org/mailman/listinfo/clutter-list