ok, I switched the compiler to pure clang instead of clang-cl (frontend to
MSVC), and it went a lot better. You can look at
https://github.com/amoldeshpande/haproxy There's just one commit with the
shared code.
Since I don't have it really running I can't say if the LLP64 things will
cause any
On Tue, Oct 29, 2019 at 10:29:43AM -0700, Amol Deshpande wrote:
> The short answer as to why is that in the games industry Windows servers
> are not unknown. Plus during development it's helpful to have the ability
> to run all servers locally on a developer's computer, which is usually
> Windows
hi Willy,
Yes, I do have strange hobbies :-)
The short answer as to why is that in the games industry Windows servers
are not unknown. Plus during development it's helpful to have the ability
to run all servers locally on a developer's computer, which is usually
Windows for PC games.
Also,
My 2 cents: "let's wait for Windows to adopt the Linux kernel"..
Hi Amol,
On Sat, Oct 19, 2019 at 09:41:34AM -0700, Amol Deshpande wrote:
> hi,
>
> I've taken up a hobby task to make a native version of haproxy for Windows,
> using some of the platform-specific features for network I/O.
You're having strange hobbies in my opinion :-)
> I've been using
hi,
I've taken up a hobby task to make a native version of haproxy for Windows,
using some of the platform-specific features for network I/O.
I've been using clang-cl to compile and it mostly works well. There are a
lot of warnings generated in the code that fall into two categories:
1. General
6 matches
Mail list logo
