From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Mono package
Date: Fri, 1 Nov 2013 17:39:34 +0100 [thread overview]
Message-ID: <20131101173934.63cf0a93@skate> (raw)
In-Reply-To: <CA+R-mPPYzHxdfxvfcmo=bzEhd9A4rs1Gsf9=onaYxjh74VAmLA@mail.gmail.com>
Dear Mirek Frajkowski,
On Fri, 1 Nov 2013 15:29:31 +0000, Mirek Frajkowski wrote:
> I would like to contribute to buildroot by sending Mono package, which I
> believe many people will find useful.
Nice, thanks!
> Mono has to be cross compiled in two steps:
>
> 1. Native code - for the virtual execution system, garbage collector and
> other unmanaged bits
> 2. Managed code - this includes C# compiler, assembler, class libraries and
> so on
>
> Due to this fact it is divided into two sub-folders/sub-packages. The build
> configuration itself is not very complicated, however one thing is worth
> pointing out.
>
> Mono signs its binary files and thus we have to disable stripping of the
> binaries in the buildroot, which is done through "Config.in" file.
>
> Everything else is pretty much straight forward and self explanatory.
>
> Package is also installed in staging directory, just in case someone needs
> to compile other packages which depend on Mono.
>
> Please find the Mono package attached.
Can you send this as one or several patches, with the patches inline.
See
http://buildroot.org/downloads/manual/manual.html#_contributing_to_buildroot
for details on how to contribute to Buildroot.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2013-11-01 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 15:29 [Buildroot] Mono package Mirek Frajkowski
2013-11-01 16:39 ` Thomas Petazzoni [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=20131101173934.63cf0a93@skate \
--to=thomas.petazzoni@free-electrons.com \
--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