[Webkit-unassigned] [Bug 161864] Building on Win 64 (Windows 10 64 bit)

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=161864

Don Olmstead <don.olmstead at am.sony.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |don.olmstead at am.sony.com
         Resolution|---                         |FIXED

--- Comment #9 from Don Olmstead <don.olmstead at am.sony.com> ---
(In reply to Tom Sisson from comment #7)
> (In reply to comment #6)
> > 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.
> 
> 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.

I recently fixed https://bugs.webkit.org/show_bug.cgi?id=172570 which should get you past that issue if you are using mingw. I don't compile on mingw so no clue how much further it will get you.

I do know that if you do not set CC and CXX if you are using Ninja then it will search the path. If it finds mingw or another compiler first then it will attempt to use that.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170530/d46c2bae/attachment-0001.html>