From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] package/mono: new package
Date: Fri, 10 Oct 2014 20:48:40 +0200 [thread overview]
Message-ID: <20141010204840.4ec4d5d3@free-electrons.com> (raw)
In-Reply-To: <1412951017-6769-1-git-send-email-angelo.compagnucci@gmail.com>
Dear Angelo Compagnucci,
On Fri, 10 Oct 2014 16:23:37 +0200, Angelo Compagnucci wrote:
> I tried to merge mono-managed and mono-native in a single package,
> but crosscompiling and compiling in the same folder without a clean
> makes a big mess, so I think these packages should remain splitted.
> Any hint appreciated!
I still don't understand why you think the build takes place in the
same folder: the host and target variants of the same package are built
in separate directories.
I'm working on the patches that use a single mono package. There are
other issues with your patch: host-mono-managed automatically downloads
monolite, which is bad, as it circumvents the download infrastructure
of Buildroot. I'll show you an approach to fix that.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-10 18:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 14:23 [Buildroot] [PATCH v3] package/mono: new package Angelo Compagnucci
2014-10-10 18:48 ` Thomas Petazzoni [this message]
2014-10-10 19:24 ` Angelo Compagnucci
2014-10-10 19:36 ` Angelo Compagnucci
2014-10-11 0:30 ` Matthew Weber
2014-10-11 7:25 ` Angelo Compagnucci
2014-10-14 20:24 ` Arnout Vandecappelle
2014-10-17 14:03 ` Angelo Compagnucci
2014-10-11 10:32 ` Thomas Petazzoni
2014-10-11 10:40 ` 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=20141010204840.4ec4d5d3@free-electrons.com \
--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