Re: [Mono-dev] [PATCH] Android Support [1/4]

2010-05-21 Thread damian 

I'm also interested in this.  I'm trying to run configure with options to
make it use the android ndk tools etc. as described here:
http://warpedtimes.wordpress.com/category/technology/android-technology/

It falls over when wanting to compile test code, so I'm setting various
options to get it to go a little further, but it is painful ... any help
would be very much appreciated (such as the magic ./configure comand line).

Thanks,
Damian


JeroMiya wrote:
 
 Oops, meant to send this to the list.
 
 Just a quick question. I'm new to the mono build process - with these
 changes, how do you target the android platform when building mono/mcs?
 
 ...
 
-- 
View this message in context: 
http://mono.1490590.n4.nabble.com/PATCH-Android-Support-1-4-tp2016287p2226260.html
Sent from the Mono - Dev mailing list archive at Nabble.com.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] [PATCH] Android Support [1/4]

2010-04-19 Thread Rodrigo Kumpera 
+static void
+out_vfprintf (FILE *ignore, const gchar *format, va_list args)
+{
+ __android_log_vprint (ANDROID_LOG_ERROR, mono, format, args);
+}

Shouldn't we identify the entry by the application name instead of mono?


On Mon, Apr 19, 2010 at 2:44 PM, Jonathan Pryor jonpr...@vt.edu wrote:

 This is a series of patches to add support to Mono for building against
 the Android NDK [0].  Android runs the Linux kernel, but moves many
 things around compared to a normal desktop Linux distro.

 These patches are based against the mono-2-6 branch.

 This first patch patches eglib so that messages produced by g_print(),
 g_printerr(), and g_log() are sent to the Android message log:

* src/glib.h: Rebase g_return_if_fail(), g_return_val_if_fail() in
  terms of g_critical() instead of printf, and turn g_printerr()
 into
  an actual function instead of a macro.
* src/goutput.c: Add Android support, sending g_print(),
 g_printerr(),
  and g_log() messages to the Android system log.

 Permission to commit?

  - Jon

 [0] http://developer.android.com/sdk/ndk/index.html


 ___
 Mono-devel-list mailing list
 Mono-devel-list@lists.ximian.com
 http://lists.ximian.com/mailman/listinfo/mono-devel-list


___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] [PATCH] Android Support [1/4]

2010-04-19 Thread Jonathan Pryor 
On Mon, 2010-04-19 at 15:15 -0300, Rodrigo Kumpera wrote:
 +static void 
 +out_vfprintf (FILE *ignore, const gchar *format, va_list args)
 +{
 + __android_log_vprint (ANDROID_LOG_ERROR, mono, format, args);
 +}
 
 Shouldn't we identify the entry by the application name instead of
 mono?

In an ideal world, yes, but I'm not sure how to do that.  I suppose
using g_get_application_name() would be THE way, except that Mono
doesn't currently call g_set_application_name() (and eglib doesn't
implement either), so that would appear to be a more invasive change for
the mono-2-6 branch.

Is there some other way to obtain this information?

Thanks,
 - Jon


___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] [PATCH] Android Support [1/4]

2010-04-19 Thread Jonathan Pryor 
On Mon, 2010-04-19 at 14:26 -0400, Jonathan Pryor wrote:
 On Mon, 2010-04-19 at 15:15 -0300, Rodrigo Kumpera wrote:
  +static void 
  +out_vfprintf (FILE *ignore, const gchar *format, va_list args)
  +{
  + __android_log_vprint (ANDROID_LOG_ERROR, mono, format, args);
  +}
  
  Shouldn't we identify the entry by the application name instead of
  mono?
 
 In an ideal world, yes, but I'm not sure how to do that.  I suppose
 using g_get_application_name() would be THE way, except that Mono
 doesn't currently call g_set_application_name() (and eglib doesn't
 implement either), so that would appear to be a more invasive change for
 the mono-2-6 branch.

Added a TODO comment noting that a better name should be used.

Committed to mono-2-6 (r155762) and trunk (r155763).

Thanks!
 - Jon


___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list