<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Building on Win 64 (Windows 10 64 bit)"
href="https://bugs.webkit.org/show_bug.cgi?id=161864#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Building on Win 64 (Windows 10 64 bit)"
href="https://bugs.webkit.org/show_bug.cgi?id=161864">bug 161864</a>
from <span class="vcard"><a class="email" href="mailto:thomas.sisson.1@gmail.com" title="Tom Sisson <thomas.sisson.1@gmail.com>"> <span class="fn">Tom Sisson</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=161864#c6">comment #6</a>)
<span class="quote">> This is my build log with CMake+Ninja on Windows 10 x64.
>
> > C:\home\fujihiro\work\webkit\webkit1\Tools\Scripts>perl build-webkit
> > WebKitSupportLibrary is up-to-date.
> > Not searching for unused variables given on the command line.
> > -- The C compiler identification is MSVC 19.0.24213.1
> > -- The CXX compiler identification is MSVC 19.0.24213.1
> > -- Check for working C compiler using: Ninja
> > -- Check for working C compiler using: Ninja -- works
>
> Comparing to your build log, I guess you have a 'gcc' in your PATH.</span >
The choice of C compiler should not make a difference, and GCC is a good C compiler. However, it may be best practice to use a compiler designed for Microsoft. It does seem that in the past there were many C compilers out there that did a good job when Windows was only 32 bit, though some 16-bit programs were still around. Borland had a working C compiler, but I have heard they have dropped out of the market with 64-bit Windows becoming commonplace and Visual Studio being available for free and much improved.
I also believe that programmers write sources and scripts with the assumption that Visual Studio will be used for Microsoft Windows, GCC will be used *nix programs, and XTools will be used for Apple programs that will use Apple libraries. One cannot simply write generic source code for a program and expect the build tools to compile the program without instructions.
Keeping this in mind, I would not expect GCC to build perfectly for Windows any more than Visual Studio to build perfectly for Linux. I know I can pass parameters on the command line in Linux to use specific tools. However, I have little experience in doing this in Windows. Perhaps, I should simply change the environment variables to hide undesirable tools, reboot and compile.
In conclusion it seems that the answer is to pass parameters or hide GCC.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>