suy/clang-win32

## clang-win32
[15:26:45] <aknight> kkoehne: so are you working on clang-win32 support?
[15:38:32] <kkoehne> aknight: Nope
[15:38:49] <aknight> kkoehne: who is then? :-)
[15:39:00] <kkoehne> aknight: You? :)
[15:39:10] <kkoehne> aknight: I intend(ed) to
[15:39:34] <kkoehne> aknight: But haven't really come around to play with it much more than trying to compile qtbase, only to see it choking on the very first .cpp file
[15:39:44] <aknight> kkoehne: i've played around with it, but per lars' email i assumed someone was actually spending time/money on it
[15:39:45] <kkoehne> aknight: But I heard you had a patch somewhere to overcome this ...
[15:40:45] <aknight> kkoehne: i haven't touched it in a while, but there's a wip on my dashboard
[15:40:53] <lars> aknight: no currently, this is only my wishful thinking... ;-)
[15:41:47] <aknight> lars: fair enough :) i might have some time to work on it for 5.6
[15:42:01] <kkoehne> According to makalino they're also still using the MSVC linker ...
[15:42:13] <aknight> yes. so that's something that needs to be decided
[15:42:29] <aknight> also which make to use
[15:42:48] <lars> aknight: it would be great if we could get to a decent open toolchain on windows.
[15:43:07] <lars> but as long as they are still using the msvc linker, we still have that dependency :/
[15:44:56] <aknight> kkoehne: lars: i think ld can be used, eventually lld too. that's probably what we should aim for. that means mingw (or at least binutils + make) installed alongside clang
[15:46:15] <lars> aknight: is that possible? I thought clang produced msvc compatible binaries
[15:47:14] <aknight> lars: you can alternatively produce mingw compatible binaries.
[15:47:29] <lars> really? didn't know that.
[15:47:32] <lars> nice :)
[15:48:55] <aknight> imo the msvc binaries would be better (no dependency on libgcc) as long as lld could do the linking
[15:50:28] <lars> aknight: yes, agree. the main issue is that we need a working linker.
[15:50:45] <mitchc> peppe: hmm, i see that it's already explained here http://doc.qt.io/qt-5/qml-url.html
[15:51:01] <kkoehne> fkleint: Interested? I'm not so much ;) https://bugreports.qt.io/browse/QTBUG-43877
[15:51:01] <qt_gerrit> QPrinter.setPaperSize crash app - https://bugreports.qt.io/browse/QTBUG-43877
[15:51:05] <lars> aknight: a toolchain without the gnu binutils purely based on llvm would probably be easier to manage
[15:51:41] <aknight> lars: definitely. http://lld.llvm.org/windows_support.html <-- progress looks pretty good here, but i haven't tried it in a while
[15:53:58] <lars> aknight: you're right. loks like we should be able to try it all on 32bit. and on 64bit we should be mostly ok as well, as we don't really use exceptions
	[15:26:45] <aknight> kkoehne: so are you working on clang-win32 support?
	[15:38:32] <kkoehne> aknight: Nope
	[15:38:49] <aknight> kkoehne: who is then? :-)
	[15:39:00] <kkoehne> aknight: You? :)
	[15:39:10] <kkoehne> aknight: I intend(ed) to
	[15:39:34] <kkoehne> aknight: But haven't really come around to play with it much more than trying to compile qtbase, only to see it choking on the very first .cpp file
	[15:39:44] <aknight> kkoehne: i've played around with it, but per lars' email i assumed someone was actually spending time/money on it
	[15:39:45] <kkoehne> aknight: But I heard you had a patch somewhere to overcome this ...
	[15:40:45] <aknight> kkoehne: i haven't touched it in a while, but there's a wip on my dashboard
	[15:40:53] <lars> aknight: no currently, this is only my wishful thinking... ;-)
	[15:41:47] <aknight> lars: fair enough :) i might have some time to work on it for 5.6
	[15:42:01] <kkoehne> According to makalino they're also still using the MSVC linker ...
	[15:42:13] <aknight> yes. so that's something that needs to be decided
	[15:42:29] <aknight> also which make to use
	[15:42:48] <lars> aknight: it would be great if we could get to a decent open toolchain on windows.
	[15:43:07] <lars> but as long as they are still using the msvc linker, we still have that dependency :/
	[15:44:56] <aknight> kkoehne: lars: i think ld can be used, eventually lld too. that's probably what we should aim for. that means mingw (or at least binutils + make) installed alongside clang
	[15:46:15] <lars> aknight: is that possible? I thought clang produced msvc compatible binaries
	[15:47:14] <aknight> lars: you can alternatively produce mingw compatible binaries.
	[15:47:29] <lars> really? didn't know that.
	[15:47:32] <lars> nice :)
	[15:48:55] <aknight> imo the msvc binaries would be better (no dependency on libgcc) as long as lld could do the linking
	[15:50:28] <lars> aknight: yes, agree. the main issue is that we need a working linker.
	[15:50:45] <mitchc> peppe: hmm, i see that it's already explained here http://doc.qt.io/qt-5/qml-url.html
	[15:51:01] <kkoehne> fkleint: Interested? I'm not so much ;) https://bugreports.qt.io/browse/QTBUG-43877
	[15:51:01] <qt_gerrit> QPrinter.setPaperSize crash app - https://bugreports.qt.io/browse/QTBUG-43877
	[15:51:05] <lars> aknight: a toolchain without the gnu binutils purely based on llvm would probably be easier to manage
	[15:51:41] <aknight> lars: definitely. http://lld.llvm.org/windows_support.html <-- progress looks pretty good here, but i haven't tried it in a while
	[15:53:58] <lars> aknight: you're right. loks like we should be able to try it all on 32bit. and on 64bit we should be mostly ok as well, as we don't really use exceptions