Remove the Mingw32/Mingw64 support

[XVilka]

Since we now have native MSVC support it is just an additional burden to support Mingw32/64, and some code can be cleaned. So please discuss. And MSVC 2015 version supports Windows versions higher than Windows XP (including it).

[XVilka]

Will solve those issues automagically:

• mingw32 thread.c bitching #1169
• Enable Mingw32 and Cygwin builds on AppVeyor back #9088
• build fails on MSYS2 64 Bit #7436
• Need to update cross compiler link in Windows.md #9937
• msys2 windows make problem #6743

[xarkes]

I agree, I see no advantages to keep MinGW while MSVC is available.

[radare]

How can i get msvc in mac/linux? Mingw is there because its the only easy way to crosscompile to windows from there. Imho its useful, but i agree there are some inconsistencies that can make some people complain

…

On 28 Apr 2018, at 08:58, xarkes ***@***.***> wrote: I agree, I see no advantages to keep MinGW while MSVC is available. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[xarkes]

Well indeed, but give me one good reason to cross compile when there are releases binaries? If you don't have Windows, you surely don't need Windows binaries?

[XVilka]

@radare easy - just use Wine: https://github.com/xantares/msvc-wine

[radare]

And how to wget msvc.zip?

…

On 28 Apr 2018, at 10:07, Anton Kochkov ***@***.***> wrote: @radare easy - just use Wine: https://github.com/xantares/msvc-wine — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[XVilka]

http://landinghub.visualstudio.com/visual-cpp-build-tools

…

On Sat, Apr 28, 2018, 5:31 PM radare ***@***.***> wrote: And how to wget msvc.zip? > On 28 Apr 2018, at 10:07, Anton Kochkov ***@***.***> wrote: > > @radare easy - just use Wine: https://github.com/xantares/msvc-wine > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub, or mute the thread. > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#9973 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAMZ_U7iD9ZnWPoMKWA3EtFPxvnLE8szks5ttDb4gaJpZM4TrO2a> .

[radare]

Why is this thing not in r2pm yet then?

…

On 28 Apr 2018, at 11:47, Anton Kochkov ***@***.***> wrote: http://landinghub.visualstudio.com/visual-cpp-build-tools On Sat, Apr 28, 2018, 5:31 PM radare ***@***.***> wrote: > And how to wget msvc.zip? > > > On 28 Apr 2018, at 10:07, Anton Kochkov ***@***.***> > wrote: > > > > @radare easy - just use Wine: https://github.com/xantares/msvc-wine > > > > — > > You are receiving this because you were mentioned. > > Reply to this email directly, view it on GitHub, or mute the thread. > > > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#9973 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AAMZ_U7iD9ZnWPoMKWA3EtFPxvnLE8szks5ttDb4gaJpZM4TrO2a> > . > — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[xarkes]

Because no one needed it until you today :p
So if we add that to r2pm and documentation to cross compile with wine, then it's all good, we can remove MinGW support?

[radare]

Let me try first. But my reasoning for this would be if mingw project was dead. Which seems so because it was forked here https://mingw-w64.org And maybe that people would want to use r2 as a testbed for improving their project too. Last release was half a year ago and maybe we want to point them all those missing function definitions and unicode issues What do you think?

…

On 28 Apr 2018, at 12:36, xarkes ***@***.***> wrote: Because no one needed it until you today :p So if we add that to r2pm and documentation to cross compile with wine, then it's all good, we can remove MinGW support? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[radare]

Mainly because i dont like to depend on privative software to do something. And when i was maintaining r2 for windows i was doing cygwin and mingw alone

…

On 28 Apr 2018, at 12:36, xarkes ***@***.***> wrote: Because no one needed it until you today :p So if we add that to r2pm and documentation to cross compile with wine, then it's all good, we can remove MinGW support? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[XVilka]

I was using Cygwin and Mingw too, but these days those are not popular due to WSL (and improved C99 in MSVC) and have too big overhead. On Apr 29, 2018 4:19 AM, "radare" <[email protected]> wrote: Mainly because i dont like to depend on privative software to do something. And when i was maintaining r2 for windows i was doing cygwin and mingw alone

On 28 Apr 2018, at 12:36, xarkes ***@***.***> wrote: Because no one needed it until you today :p So if we add that to r2pm and documentation to cross compile with wine,

then it's all good, we can remove MinGW support?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#9973 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAMZ_V6xnD8LbY_rWgClvzXKYVnnSFk0ks5ttM7hgaJpZM4TrO2a> .

[radare]

World surf league?

…

On 29 Apr 2018, at 04:30, Anton Kochkov ***@***.***> wrote: I was using Cygwin and Mingw too, but these days those are not popular due to WSL (and improved C99 in MSVC) and have too big overhead. On Apr 29, 2018 4:19 AM, "radare" ***@***.***> wrote: Mainly because i dont like to depend on privative software to do something. And when i was maintaining r2 for windows i was doing cygwin and mingw alone > On 28 Apr 2018, at 12:36, xarkes ***@***.***> wrote: > > Because no one needed it until you today :p > So if we add that to r2pm and documentation to cross compile with wine, then it's all good, we can remove MinGW support? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub, or mute the thread. > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#9973 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAMZ_V6xnD8LbY_rWgClvzXKYVnnSFk0ks5ttM7hgaJpZM4TrO2a> . — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[pelijah]

Windows Subsystem for Linux. But it is available only on Windows 10.

[TheAifam5]

What about Clang? :) We can use a clang and stuff from MinGW like headers and libraries.

[xarkes]

You can use clang with meson+ninja build system. Just do set CC=clang and follow the instructions for building.

[pelijah]

Meson doesn't support clang on Windows.

[thestr4ng3r]

If you want to cross compile, couldn't you just use meson? It has support for that built in already, so if we drop support for mingw in acr it would still be possible without us having to maintain anything. (except maybe details in the source code that may be incompatible with mingw).

[virteman]

I don't agree this suggestion. on the contrary, radare should support Mingw32/Mingw64 and cygwin better.

[xarkes]

@virteman Could you please explain why? If you are using Windows, you surely have Visual Studio installed, why would you use mingw or cygwin rather than the official VS tools?

[radare]

my reasoning is that i prefer opensource than closed source compilers. but its true that cygwin is a mess and mingw is pretty badly maintained which ends up with unsync headers with windows, wrong structs, missing function signatures and weird crashes that we have to fix in our side with “dlopen/dlsym” and other ugly hacks. which was the reason to switch to msvc

…

On 18 Oct 2018, at 15:45, xarkes ***@***.***> wrote: @virteman <https://github.com/virteman> Could you please explain why? If you are using Windows, you surely have Visual Studio installed, why would you use mingw or cygwin rather than the official VS tools? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#9973 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA3-lldyU2uUKG3ieJ3wR7ghDhwzbTnKks5umIXqgaJpZM4TrO2a>.

[virteman]

@xarkes cygwin can be used connect windows via ssh，then I can use linux terminal run r2 other than window's cmd.exe which is a ugly termal without some keybind as linux terminal.

[xarkes]

There are many replacements for Windows cmd.exe, including WSL.
I mean that @radare argument makes more sense to me than what you are describing...

[radare]

Probably the biggest problem of all this is that e cant support all those targets with a single build. So window users will be confused again with 4 different zips to download and the problem is that they will behave wrongly depending on how you run them.. so its not just a development problem

[XVilka]

@pelijah by the way, meson support for clang-cl is improving steadily and only some minor parts are now unsolved. See these bugs for keeping the track:

• Windows Clang with ninja backend not supported
• Compiler detection is incorrect for native LLVM/Clang install on Windows
• Meson can't find the resource compiler when using clang in MSVC ABI mode

[XVilka]

Resolved by bb67b54