Summary: | Support for building on Android | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Alvaro Soliverez <alvaro.soliverez> |
Component: | yell | Assignee: | Telepathy bugs list <telepathy-bugs> |
Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | normal | ||
Priority: | medium | Keywords: | patch |
Version: | git master | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Patch to build on Android
Patch to build on Android - fixed Patch to build on Android - fixed Support for Android - fixed |
Description
Alvaro Soliverez
2011-11-02 09:34:46 UTC
This patch enables building tp-yell on Android, using Android NDK and androgenizer Created attachment 53063 [details] [review] Patch to build on Android Comment on attachment 53063 [details] [review] Patch to build on Android Review of attachment 53063 [details] [review]: ----------------------------------------------------------------- ::: telepathy-yell/Makefile.am @@ +195,5 @@ > + -:CFLAGS $(DEFS) $(CFLAGS) $(DEFAULT_INCLUDES) $(INCLUDES) \ > + $(AM_CFLAGS) \ > + -:CPPFLAGS $(CPPFLAGS) $(AM_CPPFLAGS) \ > + -:LDFLAGS $(libtelepathy_yell_la_LIBADD) \ > + $(libtelepath_yell_la_LDFLAGS) -lgio-2.0 -ltelepathy-glib \ There's a typo here: "libtelepath_yell_la_LDFLAGS" is missing a y. (So how does it work, we wonder? :) ) Created attachment 53419 [details] [review] Patch to build on Android - fixed The flag was actually not required, that's why it was working :) Created attachment 53556 [details] [review] Patch to build on Android - fixed Fixed the libs hardcoding (In reply to comment #5) > Created attachment 53556 [details] [review] [review] > Patch to build on Android - fixed > > Fixed the libs hardcoding I think this is the patch for Gabble, not for Yell. :) Created attachment 53574 [details] [review] Support for Android - fixed This is the correct patch, sorry |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.