Hi Huihong,

Don't think MSVC compilation can be easily done (C compiler in MSVC also don't support C99, whose array initialization by index feature is heavily used). Maybe easier will be to use MinGW64. Cross compilation process is just a compilation with cross-compiler :) - you build GCC as Windows executable capable to produce Linux binaries. There are docs on the net. GCC version is around 3.4, IIRC.

Thanks,
   Nikolay.



Huihong Luo пишет:
Hi Nilolay,
I will give it a try to see if msvc++ compilation of recompiler can be easily done. In the meantime, can you give some details on the cross compilation process? which tool are you using? which version? more info is highly appreciated. Thanks for your very helpful info thus far, Huihong

--- On *Tue, 7/14/09, Nikolay Igotti /<[email protected]>/* wrote:


    From: Nikolay Igotti <[email protected]>
    Subject: Re: [vbox-dev] Is gcc 3.3.x really necessary to compile
    the recompiler?
    To: "Huihong Luo" <[email protected]>
    Cc: "VirtualBox developer's list" <[email protected]>
    Date: Tuesday, July 14, 2009, 12:25 PM

    Hi Huihong,

    Actually this file is built on Windows using cross-compiler for
    Linux target :). It's being built this way, because there was no
    good MinGW for 64-bit at times it was done, and REM relies on GCC
    extensions (notably global registers variables and some FP stuff)
    to function correctly. Right approach would be to rebuild
    recompiler with MSVC eventually, but it needs a volunteer (I think
    it was done for QEMU, so should be feasible).
    Also if taking MinGW64 approach don't forget calling convention
    difference on AMD64 between Linux and Windows. REM relies on that
    too (not too hard to fix, for sure, just need a bit of
    understanding in TCG).

    If you (or someone else on this list ) will do that - I can help
    with getting patch integrated (never found enough time/desire to
    do that myself).

    Thanks,
    Nikolay.


    Huihong Luo пишет:
    > Hi Nikolay,
    > Thanks for the clarification. It's much easier without sticking
    to the old gcc version.
    > Yes, I noticed that VBoxRem2.rel is an ELF image. Can you
    explain how this file is built? I assume it's done on Linux. Do
    you use mingw toolchain on linux to do the cross compile? Since
    it's ELF image, perhaps it's built from pure linux gcc (w/o cross
    compile to windows)?
    > I am trying to eliminate VBoxREM2.rel on windows using MingW64,
    in other words, combining the current VBoxREM.dll + VBoxREM2.rel
    ==> VBoxREM.dll
    > Thanks,
    > Huihong
    >
    > --- On *Tue, 7/14/09, Nikolay Igotti /<[email protected]
    <http://us.mc343.mail.yahoo.com/mc/[email protected]>>/*
    wrote:
    >
    >
    >     From: Nikolay Igotti <[email protected]
    <http://us.mc343.mail.yahoo.com/mc/[email protected]>>
    >     Subject: Re: [vbox-dev] Is gcc 3.3.x really necessary to compile
    >     the recompiler?
    >     To: "Huihong Luo" <[email protected]
    <http://us.mc343.mail.yahoo.com/mc/[email protected]>>
    >     Cc: "VirtualBox developer's list" <[email protected]
    <http://us.mc343.mail.yahoo.com/mc/[email protected]>>
    >     Date: Tuesday, July 14, 2009, 2:24 AM
    >
    >     Hi Huihong,
    >
    >
    >     Recompiler should build OK with recent gcc. Gcc 3 limitation was
    >     applicable to 'old' recompiler, not relying on TCG for
    >     codegeneration. Windows 64-bit REM is built to ELF image,
    not PE,
    >     thus MinGW shall be of little help to you.
    >
    >     Thanks,
    >     Nikolay.
    >
    >
    >     Huihong Luo wrote:
    >     > The reason I asked is that gcc 4.4.3 seems to be working
    fine on
    >     linux, so I am very confused about gcc requirement.
    >     > I am trying to use the latest gcc4.4.0 mingw64 bit on amd64 to
    >     build the recompiler, would this be a problem?
    >     > Does 3.3.x requirement only apply to mingw32? in other cases,
    >     gcc 4 is OK?
    >     > Thanks,
    >     >
    >     >
> ------------------------------------------------------------------------
    >     >
    >     > _______________________________________________
    >     > vbox-dev mailing list
    >     > [email protected]
    <http://us.mc343.mail.yahoo.com/mc/[email protected]>
> <http://us.mc343.mail.yahoo.com/mc/[email protected]>
    >     > http://vbox.innotek.de/mailman/listinfo/vbox-dev
    >     >
    >
    >
    ------------------------------------------------------------------------
    >
    > _______________________________________________
    > vbox-dev mailing list
    > [email protected]
    <http://us.mc343.mail.yahoo.com/mc/[email protected]>
    > http://vbox.innotek.de/mailman/listinfo/vbox-dev
>
------------------------------------------------------------------------

_______________________________________________
vbox-dev mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-dev


_______________________________________________
vbox-dev mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-dev

Reply via email to