From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: Richard Tollerton <rich.tollerton@ni.com>, yocto@yoctoproject.org
Subject: Re: [meta-mono] [RFC] [PATCH 0/1] Force MONO_CFG_DIR
Date: Mon, 20 Jul 2015 19:16:29 +0100 [thread overview]
Message-ID: <55AD3AFD.2010100@dynamicdevices.co.uk> (raw)
In-Reply-To: <878uaar96l.fsf@weregild.amer.corp.natinst.com>
Hi Richard,
On 20/07/2015 19:11, Richard Tollerton wrote:
> Alex J Lennon <ajlennon@dynamicdevices.co.uk> writes:
>
>> Out of image-full-mono these have problems without gmcs present,
>>
>> Looks like we need a solution for these three to use mcs instead of gmcs,
>>
>> mono-xsp_3.0.11.bb
> I guess I'm the least concerned about this because of the fixes applied
> in git. They still haven't cut a release yet so I'd guess we should just
> create a mono-xsp_git.bb.
>
>> dbus-sharp_0.8.0.bb
> We might be able to work around this by setting $GMCS, judging from
> configure.ac.
>
>> mono-addins_1.1.bb
> We might be able to work around this by setting $MCS, judging from
> configure.ac.
>
> Beyond that, I suppose the most OE-y way of solving this would be to
> promote your script to a full-blown package that PROVIDES gmcs, such
> that mono3 PROVIDES gmcs and mcs, but mono4 only PROVIDES mcs. Or
> something like that.
>
>> Cheers,
>>
>> Alex
I did a set of work today to bring the recipes up to use mcs instead of
gmcs.
Maybe you can take a look? Thanks,
Alex
prev parent reply other threads:[~2015-07-20 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 16:57 [meta-mono] [RFC] [PATCH 0/1] Force MONO_CFG_DIR Richard Tollerton
2015-07-17 16:57 ` [meta-mono] [RFC] [PATCH 1/1] mono.bbclass: set MONO_CFG_DIR Richard Tollerton
2015-07-17 17:26 ` [meta-mono] [RFC] [PATCH 0/1] Force MONO_CFG_DIR Alex J Lennon
2015-07-17 18:24 ` Richard Tollerton
2015-07-17 18:44 ` Alex J Lennon
2015-07-18 9:29 ` Alex J Lennon
2015-07-20 18:11 ` Richard Tollerton
2015-07-20 18:16 ` Alex J Lennon [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=55AD3AFD.2010100@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--cc=rich.tollerton@ni.com \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.