BUILD: enable final link via C++

[0-8-15]

It also links some files into a position where they are expected.

No idea how to do this the right way(TM).

[mgorges]

Why are you doing this instead of adding another -I$win_sysroot/include in targets/win32/build-binary#L89? Also, does this filename case matter?

[mgorges]

Shouldn't the -fpermissive also only be applied when using a c++ compiler, as I thought this was only needed if you use non-conforming code?

[0-8-15]

Am Wed, 04 Nov 2020 00:44:39 -0800 schrieb Matthias Görges <notifications@github.com>:

@mgorges commented on this pull request. > @@ -38,6 +38,11 @@ win_sysroot=`ls -1d ${WIN32SDK}/i?86-*mingw32* | head -n 1` win_cross=`ls -1 ${WIN32SDK}/bin/*mingw32*-gcc | head -n 1 | sed 's/gcc$//'` +test -f ${SYS_PREFIX}/include/WinSock2.h || ln -s $win_sysroot/include/winsock2.h ${SYS_PREFIX}/include/WinSock2.h Why are you doing this instead of adding another `-I$win_sysroot/include` in targets/win32/build-binary#L89?

because I did not find the right spot to do such a thing at the other hand: I'd rather not need such a shitty hack at all

Also, does this filename case matter?

That's been the issue behind: I cross-compile for Win32 under Linux. That's when it failed to work.

[0-8-15]

Am Wed, 04 Nov 2020 00:45:55 -0800 schrieb Matthias Görges <notifications@github.com>:

@mgorges commented on this pull request. > @@ -87,7 +87,7 @@ if [ `is_standalone_app` = "yes" ]; then else if [ `is_gui_app` = yes ]; then veval "$SYS_CC -I$SYS_PREFIX/include \ - $cflag_additions -mwindows win32_microgl.c main.c icon.o -o $tgt \ + $cflag_additions -mwindows -fpermissive win32_microgl.c main.c icon.o -o $tgt \ Shouldn't the `-fpermissive` also only be applied when using a c++ compiler, as I thought this was only needed if you use non-conforming code?

Likely it should. Again just a bad work around the actual issue: maybe someone knows how to fix the offending lines in the source code in a way compatible with both dialects.