Re: [Mingw-users] xmingw, cross compile issue

[Michael G. <mg...@te...>]

[bootstrapping problem when creating x-idl-compiler]
> I try to build ORBit2-2.12.5 under Linux using xmingw.
> Using autoconf options:
>     configure \
>         --target=3Di686-pc-mingw32 \
>         --host=3Di686-pc-mingw32 \
>         --build=3Di686-pc-linux-gnu \
>         ....
>=20
>=20
> In the build process, a IDL compiler, orbit-idl-2.exe, will be created
> and generate some source code from IDL which are part of ORBit2-2.12.5.
> The problem is orbit-idl-2.exe is suppose to run on Windows not Linux ...
>=20
> I overcome this by create a native Linux ORBit2-2.12.5 and copy
> the native orbit-idl-2 to orbit-idl-2.exe and rebuild xmingw's ORBit2-2.1=
2.5
> again and it works fine.

What you describe above is exactly how bootstrapping and in your
case x-bootstrapping works.

> Although my approach is OK, but I don't think this is a good solution.

Why do you think so ?
In other words:
How else do you think this could possibly be done ?

At the end of the day you will need some native idl-compiler to
do the compiling on your host. There is no way around it short of
not compiling the idl at all.

Of course you could try to start an emulator of the target OS to
run the freshly created idl-compiler but that's hardly a viable
solution.

Best,
Michael
=2D-=20
 Vote against SPAM - see http://www.politik-digital.de/spam/
 Michael Gerdau       email: mg...@te...
 GPG-keys available on request or at public keyserver