On 02/01/2011 12:09 PM, vijay singh wrote: > On Tue, 2011-02-01 at 11:21 +0100, Michael Haubenwallner wrote: >> On 02/01/2011 10:45 AM, vijay singh wrote: >>> On Tue, 2011-02-01 at 09:23 +0100, Michael Haubenwallner wrote: >>>> Hi, >>>> >>>> Which platform do you use to crosscompile? >>> i am on X-86/Ubuntu10.04. >>>> Which platform do you crosscompile for? >>> ARM11 >>>> >>>> On 01/31/2011 11:48 AM, vijay singh wrote: >>>>> Hello, >>>>> >>>>> Can any one let me know orbit2 cross compiling is possible or not. >>>>> I am trying with 2.14.18 & i found below error during make : >>>>> ==================================================================== >>>>> (rm -f corba-defs.h corba-defs-stubs.c corba-defs-skels.c >>>>> corba-defs-common.c corba-defs-imodule.c corba-defs-skelimpl.c || true) >>>>>> /dev/null >>>>> ../../../src/idl-compiler/orbit-idl-2 -I../../../src/idl/CORBA_PIDL >>>> >>>> (haven't cross-compiled ORBit2 myself, so just guessing) >>>> >>>> As ORBit2's IDL-compiler is executed at buildtime, you likely will need >>>> to have ORBit2 (same version) installed natively on the build platform. >>> How can i do the same ?? >>>> Additionally, you might have to tweak ORBit's build-system to use the >>>> pre-installed IDL-compiler instead of the just built one. >>> I understand that i have to use :--with-idl-compiler option while >>> configuring ORBit2. >>> One catch here is if i will give--with-idl-compiler=/usr/bin/orbit-idl-2 >>> then it will build for me. >> >> Then this is the way to go. >> >>> But i think in this case it uses orbit-idl-2 binary built for host & it >>> will not run on target. >> >> Do you /think/ so or have you /tried/ an experienced this problem? > > I found that orbit2 build will give us orbit-idl-2 binary,it means while > building orbit2 it will build for target.
Yes, this should be independent of whether giving --with-idl-compiler or not. > One more point if any other application want's to use orbit-idl-2 then > in this case it is from host machine (/usr/bin/orbit-idl-2) or it should > be used from the result of orbit2 cross build. It depends - on /where/ the other application needing orbit-idl-2 is running: If it is running on the build machine, /usr/bin/orbit-idl-2 has to be used. If it is running on the target machine, the cross-built orbit-idl-2 has to be used. > Please correct me if i am wrong at any point for my better > understanding. Thing simply is: /usr/bin/orbit-idl-2 (from the build machine) does run on the build machine only, while cross-built orbit-idl-2 does run on the target machine only. /haubi/ >> >> Actually, you do want to use /usr/bin/orbit-idl-2 at cross-build-time: it >> is "used" (=executed) to process idl-files shipped with ORBit2 to create >> more c-files to be cross-compiled. >> >> This does /not/ mean /usr/bin/orbit-idl-2 will be "used" (=copied) to the >> target machine instead of another cross-compiled orbit-idl-2 binary. >> >> /haubi/ _______________________________________________ orbit-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/orbit-list
