organizing the code as it is splitted across some projects, soon I'll
> put it into a git repo.
>
>
> On Thu, Jun 13, 2013 at 5:28 PM, Jeremy Bell wrote:
>
>> There is a subset of the WPF framework implemented in the .net
>> microframework. It might be a good st
There is a subset of the WPF framework implemented in the .net
microframework. It might be a good starting point (xaml parsing, data
binding scaffolding perhaps?) - you'd almost certainly need to rewrite all
the rendering code however as I believe it is a software renderer.
On Thu, Jun 13, 2013 a
Is the website itself on github? If not, I think this would be worthwhile.
Then the community could submit pull requests to update the site - would
free up the Xamarin devs to work on more useful things.
On Fri, May 31, 2013 at 12:09 PM, eb65 wrote:
> ...and, the libgdiplus-3.0.tar.bz2 package
Zoltan
>
>
> On Wed, May 29, 2013 at 6:00 PM, Jeremy Bell wrote:
>
>> I'm not sure if this is the best way to fix the issue, but I've submitted
>> a pull request with a small fix:
>> https://github.com/mono/mono/pull/650
>>
>> This is my first mon
ree files used to
> generate some files, but the byproduct is fine. This is for the AMQP
> driver, I believe. They are non-free because they cannot be changed even if
> they can be distributed freely.
>
>
>
> On Wed, May 29, 2013 at 12:59 PM, Jeremy Bell wrote:
>
>> Th
'I love this project, and want to see it succeed in more than just mobile.'
I share these sentiments! :)
At first glance, this seems like a big opportunity. There is likely to be a
lot of ASP.NET/WebAPI/socket based enterprise server software currently
running on IIS via MS-CLR where the company
have a paid license[1], you can
> copy them over. Yes, it's brittle, I'm sorry for that.
>
> But it's something that should be fixed on the build system.
>
> Cheers,
> Rodrigo
>
> [1]Starter edition doesn't allow random assemblies be used for the BCL
Yes, it's not copied because those assemblies are not very useful on the
> desktop.
>
>
> On Wed, May 29, 2013 at 11:40 AM, Jeremy Bell wrote:
>
>> When I build the monodroid assemblies with the configure option
>> --with-monodroid=yes, the profile is built correct
13 at 2:25 PM, Jeremy Bell wrote:
>
> These:
> export SYSROOT=$NDK/platforms/android-14/arch-arm
> export PATH=$NDK_STANDALONE/bin:$PATH
> export CC=arm-linux-androideabi-gcc
> export CXX=arm-linux-androideabi-g++
> export AR=arm-linux-androideabi-ar
> export AS=arm-lin
When I build the monodroid assemblies with the configure option
--with-monodroid=yes, the profile is built correctly in the master branch,
but when you make install, the monodroid profile assemblies are not copied
to the install prefix directory with the other profiles. Is this expected
behavior?
bles it. What
> configure arguments are you using ?
>
> Zoltan
>
>
> On Thu, May 23, 2013 at 5:01 PM, Jeremy Bell wrote:
>
>> At some point between branch mono-2-10-9 and branch master, a change was
>> made to /mono/mini/main.c:
>>
>> branch
>
>
> On Thu, May 23, 2013 at 11:01 AM, Jeremy Bell wrote:
>
>> At some point between branch mono-2-10-9 and branch master, a change was
>> made to /mono/mini/main.c:
>>
>> branch mono-2-10-9:
>>
>> main.c:
>> #include
>> #include &quo
At some point between branch mono-2-10-9 and branch master, a change was
made to /mono/mini/main.c:
branch mono-2-10-9:
main.c:
#include
#include "mini.h"
#ifndef HOST_WIN32
#include "buildver.h"
#endif
branch master:
#include
#include "mini.h"
#ifndef HOST_WIN32
#ifdef HAVE_SGEN_GC
#include
t -n1
--pretty=format:%h`; \
echo "#define FULL_VERSION \"$branch/$version\""; \
); \
else \
echo "#define FULL_VERSION \"tarball\""; \
fi > version.h
CC genmdesc-genmdesc.o
In file included from genmdesc.c:9:0
I'm attempting to build mono using the ndk standalone toolchain from the
android ndk (version r8e), but I am unable to complete the build.
I setup my standalone environment like so:
export
SYSROOT=/home/jeremybell/Desktop/android-ndk-r8e/platforms/android-14/arch-arm
/home/jeremybell/Desktop/andro
How about Mono.Simd support for arm NEON?
On Sun, Sep 12, 2010 at 4:07 AM, Eddy Zavaleta wrote:
> Hi,
>
> Thanks for the reply, I realized that the engine already existed when I
> browsed the mono's source code tree after sending this email.
>
> I have two big areas of interest OS stuff and grap
And it looks like they have. Except there are only 257 testers right now.
On Wed, Aug 18, 2010 at 2:14 PM, Jeremy Bell wrote:
> Miguel recently said on twitter that they are releasing the first 1024
> MonoDroid invites, so I assume they have already done so? I wasn't on the
> lis
Miguel recently said on twitter that they are releasing the first 1024
MonoDroid invites, so I assume they have already done so? I wasn't on the
list heh, so I'll have to wait.
On Wed, Aug 18, 2010 at 10:05 AM, Kris Ray wrote:
>
> Any updates on the first MonoDroid release?
>
> My Droid X is in
I've just recently been able to get the mono runtime running on android
using koush's androidmono project:
http://github.com/koush/androidmono
It seems that koush has found a possible issue regarding the Boehm GC and
threading. His description of the issue is as follows:
If you create a simple app
As the official MonoDroid SDK is getting closer to release (relatively
speaking), I have a few questions regarding licensing. What part of the Mono
project is covered only under the commercial license and what is covered
under the general license, with respect to using Mono for commercial android
a
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?
On Mon, Apr 19, 2010 at 1:44 PM, Jonathan Pryor wrote:
> This is a series of patches to add support to Mono for bui
Will there be incremental monodroid releases before the final product is
released?
Also, how will monodroid applications be deployed? Will they bundle mono in
the app itself or will it be a shared "Mono" application/activity that
launches CLI apps in response to an intent or broadcast?
___
There might be a possibility that the core runtime will be free, but not the
bindings that would let you use the native Android APIs that would allow you
to do anything outside of a hello world console program:
Quote from Miquel de Icaza:
> It seems like you can use Mono on the Android today, but
Koush responded to my tweet saying that he stopped working on it when Novell
announced their own plans for Droid bindings. I don't think he ever
committed the binding generator code to his git repository. It's a pity,
because as a hobbyist mobile developer I certainly couldn't afford the
licensing
24 matches
Mail list logo
