Has anyone tried building for Windows?

[Mukul Sabharwal]

For GCCSharp [https://github.com/mjsabby/GCCSharp], I did get GCC with
the JIT frontend working* but with modifications. I've been wanting to
tell Dave about them, so here is the very short list:

(1) `fchmod` in playback::compile_to_file::copy_file isn't supported
on MinGW - maybe put this behind an ifdef?

(2) `dlopen` and dl* family of things in
playback::context::dlopen_built_dso - again, on MinGW toolset this
isn't available. Since this is not essential to the JIT API, maybe
also make this something a user can opt out of?

So, the working* in my case was essentially generating .S files
(GCC_JIT_OUTPUT_KIND_ASSEMBLER)

If there is an interest in having a LIBGCCJIT.DLL built with these
modifications, I can certainly make a GitHub repo with some sort of
binary and source drops.

Mukul


On Wed, Jul 29, 2015 at 12:51 PM, Dibyendu Majumdar
<mobile@majumdar.org.uk> wrote:
> On 29 July 2015 at 11:44, David Malcolm <dmalcolm@redhat.com> wrote:
>> On Tue, 2015-07-28 at 22:43 -0700, Hayden Livingston wrote:
>>> I've attempted to build on Windows using Cygwin and MingW-64 and I'm
>>> not really familiar with the build system enough but I can't make any
>>> forward progress.
>>
>> Thanks for trying this.  As far as I know, you're the first person who's
>> attempted this.
>>
>
> I tried a few days ago - but could not even get configure to work. It
> kept complaining about missing mpfr, gmp, mpc even though these were
> installed. I was using msys2 as the environment with mingw64
> compilers. In the end decided life is too short and I have many other
> things I need to do.
>
> Does gcc even compile on Windows without patches from mingw project?
>
> It is a pity as LLVM code generated on Windows has a serious
> deficiency - longjmp calls cause crash as the generated code doesn't
> conform to Windows requirements. I was hoping that gcc generated code
> would not suffer from this.
>
> Regards
> Dibyendu