Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Angelo Compagnucci <angelo.compagnucci@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v6 0/2] Mono new package
Date: Wed, 22 Oct 2014 22:22:08 +0200	[thread overview]
Message-ID: <1414009330-4433-1-git-send-email-angelo.compagnucci@gmail.com> (raw)

This patch adds mono and monolite packages.

Changes v5 -> v6:

- Fixed /etc/mono configs files installation

Changes v4 -> v5:

- Defaulting BR2_PACKAGE_MONO_45 now depends on select
- Minor formatting issues

[Thomas:

  - Merge mono-managed and mono-native as a single package. The
    mono-managed stuff is done by the host variant of the mono
    package, while the mono-native stuff is done as the target variant
    of the mono package.

  - Introduce a BR2_PACKAGE_MONO_ARCH_SUPPORTS blind Config.in option
    to make sure the IPv6 related comment is not displayed when the
    architecture being used anyway doesn't support Mono.

  - Add a patch to Mono to fix the C library path when uClibc and Musl
    is used. This is a better approach than the
    POST_INSTALL_TARGET_HOOKS because this approach can potentially be
    submitted upstreamed, which ultimately allows to simplify the
    Buildroot package.

  - Depend on a 'monolite' package, and use it instead of letting Mono
    download Monolite by itself, which circumvents Buildroot's
    download infrastructure.
    mono-managed stuff is done by the host variant of the mono
    package, while the mono-native stuff is done as the target variant
    of the mono package.

  - Introduce a BR2_PACKAGE_MONO_ARCH_SUPPORTS blind Config.in option
    to make sure the IPv6 related comment is not displayed when the
    architecture being used anyway doesn't support Mono.

  - Add a patch to Mono to fix the C library path when uClibc and Musl
    is used. This is a better approach than the
    POST_INSTALL_TARGET_HOOKS because this approach can potentially be
    submitted upstreamed, which ultimately allows to simplify the
    Buildroot package.

  - Depend on a 'monolite' package, and use it instead of letting Mono
    download Monolite by itself, which circumvents Buildroot's
    download infrastructure.

  - Move the installation of Mono libraries to the target Mono
    package, as a POST_INSTALL_TARGET_HOOKS.]

[Angelo:

  - Bump to the latest Mono version 3.10.0

  - Add selection for .Net runtime compilation and installation in
    target.]


Angelo Compagnucci (2):
  package/monolite: new package
  package/mono: new package

 package/Config.in                               |  1 +
 package/mono/Config.in                          | 40 +++++++++++++++
 package/mono/mono-001-gc-fix-uclibc.patch       | 16 ++++++
 package/mono/mono-002-support-uclibc-musl.patch | 25 ++++++++++
 package/mono/mono.mk                            | 65 +++++++++++++++++++++++++
 package/monolite/monolite.mk                    | 17 +++++++
 6 files changed, 164 insertions(+)
 create mode 100644 package/mono/Config.in
 create mode 100644 package/mono/mono-001-gc-fix-uclibc.patch
 create mode 100644 package/mono/mono-002-support-uclibc-musl.patch
 create mode 100644 package/mono/mono.mk
 create mode 100644 package/monolite/monolite.mk

-- 
2.1.1

             reply	other threads:[~2014-10-22 20:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22 20:22 Angelo Compagnucci [this message]
2014-10-22 20:22 ` [Buildroot] [PATCH v6 1/2] package/monolite: new package Angelo Compagnucci
2014-10-22 20:22 ` [Buildroot] [PATCH v6 2/2] package/mono: " Angelo Compagnucci
2014-10-25  8:50 ` [Buildroot] [PATCH v6 0/2] Mono " Thomas Petazzoni
2014-10-27 22:16   ` Luca Ceresoli
2014-10-28  7:21     ` Angelo Compagnucci
2014-10-28 13:41       ` Luca Ceresoli
2014-10-30  8:35         ` Angelo Compagnucci

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=1414009330-4433-1-git-send-email-angelo.compagnucci@gmail.com \
    --to=angelo.compagnucci@gmail.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