Re: Making ORBit work with MS VS compilers



On Mon, 2008-03-17 at 21:08 -0700, Marcelo Vanzin wrote:
<snip>
> Since you've been using ORBit on Windows, did you have to make any
> modifications to libIDL? I moved into playing with the IDL compiler
> and ran into issues because of libIDL. Pretty trivial changes, but the
> code out of SVN did not work.

(Markus, correct me if I'm wrong)

Don't know how you build libIDL - we do a full autoreconf of any package
to be built with parity, currently with
      * patched libtool-1.5.24 to know about parity and winnt
        [libtool-1.5.24-parity.patch]
      * patched autoconf-2.59 to flip windows line endings in configure
        [autoconf-winnt-flip.patch]
      * vanilla automake-1.9.6
      * there still might be another patch required for any just-created
        configure (we do it in a generic way): Any 'rmdir conftest'
        needs to be 'rm -rf conftest'.
        You can apply this patch snippet as often as possible to
        configure:
        
        --- configure    2005-06-10 10:00:00.000000000 +0000
        +++ configure    2005-06-10 10:00:00.000000000 +0000
        @@ -1,1 +1,1 @@
        -    rmdir conftest
        +    rm -rf conftest

Using this procedure (maybe I forgot something), the patches required to
build native windows binaries of many packages using autotools can be
kept small - they normally just need to handle windows specific things
without touching the build environment. Even when calling just built
winnt executables with interix path-arguments, parity's runtime wrapper
should correctly convert them to windows style.

Attached are the patches for libtool and autoconf, as well as our patch
for libIDL-0.8.6 [libIDL-parity.patch], packed into
[libIDL-patches.tar.bz2].
Now we can build libIDL this way:
(NOTE: the autotools as well as parity are built for i586-pc-interix*)

$ export CC=parity.gnu.gcc
$ export CXX=parity.gnu.gcc
$ export LD=parity.gnu.gcc
$ ./configure --build=i586-pc-winnt --host=i586-pc-winnt --prefix=...
$ gmake
$ gmake install

But this does not mean you can use parity only as "cross"-compiler from
interix to winnt - parity should be able to build itself as winnt
executable, so you could use parity from within VisualStudio. Although
you don't have the path-conversion feature then - which you should not
need in this case.

HTH,
/haubi/

PS: please keep Markus Duft on CC, he's not on the list (yet)

Attachment: libIDL-patches.tar.bz2
Description: application/bzip-compressed-tar



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]