From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Message-ID: <4EC0F725.1090802@erwinrol.com> Date: Mon, 14 Nov 2011 12:10:29 +0100 From: Erwin Rol MIME-Version: 1.0 References: <4EC0EA8C.3010902@erwinrol.com> <4EC0F3C5.9070403@erwinrol.com> <20111114105945.GH28900@pengutronix.de> <201111141204.49339.alexander.stein@systec-electronic.com> In-Reply-To: <201111141204.49339.alexander.stein@systec-electronic.com> Subject: Re: [ptxdist] mono Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: Alexander Stein Cc: Robert Schwebel , ptxdist@pengutronix.de 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