From: Alexander Varnin <fenixk19@mail.ru>
To: buildroot@busybox.net
Subject: [Buildroot] mono runtime porting to buildroot
Date: Tue, 10 Dec 2013 20:05:32 +0400 [thread overview]
Message-ID: <52A73BCC.30309@mail.ru> (raw)
In-Reply-To: <000b01ceef4c$9a7ded20$cf79c760$@elgsis.com>
There was letter by kerim.fryer at gmail.com from 01.11.2013, and he
provided mono package:
http://lists.busybox.net/pipermail/buildroot/2013-November/081553.html
I have also made a package for mono, just before I saw above package.
So I have a patch that is not well tested. I am attaching my patch so
you can try it if you want.
If you find something that fits your need, you can try making good patch
for upstream.
02.12.2013 14:52, Linas Lisauskas ?????:
>
> Hi,
>
> I have a question. Maybe somebody of Your team tried to port mono
> project for buildroot. I was using openembedded dist, but is the
> requirement to use buildroot dist and mono project. Can anyone help
> write *.mk file for this? I have cross compiled mono project with
> native buildroot toolchain.
>
> Thanks.
>
> ------------
>
> Best regards,
>
> Embedded Software Engineer
>
> Linas Lisauskas
>
> Elgama Sistemos, Ltd.
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-mono-new-package.patch
Type: text/x-patch
Size: 3105 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20131210/671d4a7b/attachment.bin>
prev parent reply other threads:[~2013-12-10 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 10:52 [Buildroot] mono runtime porting to buildroot Linas Lisauskas
2013-12-05 22:29 ` Arnout Vandecappelle
2013-12-10 16:05 ` Alexander Varnin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52A73BCC.30309@mail.ru \
--to=fenixk19@mail.ru \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox