Re: [ptxdist] mono

[Alexander Stein <alexander.stein@systec-electronic.com>]

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.

Regards,
Alexander

-- 
ptxdist mailing list
ptxdist@pengutronix.de