From: Erwin Rol <mailinglists@erwinrol.com>
To: Alexander Stein <alexander.stein@systec-electronic.com>
Cc: Robert Schwebel <r.schwebel@pengutronix.de>, ptxdist@pengutronix.de
Subject: Re: [ptxdist] mono
Date: Mon, 14 Nov 2011 12:10:29 +0100 [thread overview]
Message-ID: <4EC0F725.1090802@erwinrol.com> (raw)
In-Reply-To: <201111141204.49339.alexander.stein@systec-electronic.com>
On 14-11-2011 12:04, Alexander Stein wrote:
> Hello,
>
> On Monday 14 November 2011 11:59:45 Robert Schwebel wrote:
>> On Mon, Nov 14, 2011 at 11:56:05AM +0100, Erwin Rol wrote:
>>> Yeah target is fine. And yes they are needed on the host to build
>>> libraries for the target.
>>>
>>>> If you have pre/post scripts, you should use $DESTDIR; we set this
>>>> variable while installing the opkg packages and it is not set on
>>>> runtime.
>>>
>>> Don't really understand how this will solve the problem ? The *.in
>>> versions of the scripts look like this. So they are created at
>>> "automake-time"
>>>
>>> less mcs.in
>>> #!/bin/sh
>>> exec @bindir@/mono $MONO_OPTIONS @mono_instdir@/2.0/mcs.exe
>>> -lib:@mono_instdir@/2.0 -lib:@mono_instdir@/3.5 "$@"
>>>
>>> My idea was to add a $MONO_PREFIX environment variable to the
>>> scripts and set that in the target build .make file. On the target
>>> itself the MONO_PREFIX variable would be not set and the path would
>>> be /usr/bin as expected.
>>
>> Hmm, I suppose you should discuss this with the Mono developers. I mean,
>> if they agree on an acceptable solution, we can patch it into ptxdist.
>
> The build system of momo seems to beabit strange. All cross-compile
> descriptions i found for mono was to (1) build for the host and install it in
> some DESTDIR and (2) buildfor the target and install it in the _same_ DESTDIR.
> To cleanly build mono for the target, there should be some host-mono.
Yep and that is what i did, I have a host-mono, that builds the compiler
but not the runtime libraries (the ones written in C#).
Than I have a mono package that builds the target compiler and the
runtime libaries (with use of the host-mono compiler).
Of course the weird thing is that the runtime libraries are written in
C# and could even be compiled on Windows and still be installed on the
target.
- Erwin
> Regards,
> Alexander
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2011-11-14 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 10:16 Erwin Rol
2011-11-14 10:35 ` Robert Schwebel
2011-11-14 10:56 ` Erwin Rol
2011-11-14 10:59 ` Robert Schwebel
2011-11-14 11:04 ` Alexander Stein
2011-11-14 11:10 ` Erwin Rol [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=4EC0F725.1090802@erwinrol.com \
--to=mailinglists@erwinrol.com \
--cc=alexander.stein@systec-electronic.com \
--cc=ptxdist@pengutronix.de \
--cc=r.schwebel@pengutronix.de \
/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