Thank you for this information.
On 20.10.2014 17:27, Adrien Nader wrote: > On Mon, Oct 20, 2014, Óscar Fuentes wrote: >> Ruben Van Boxem <[email protected]> >> writes: >> >>>> As stated, the problem is not related to MinGW-w64, it is about how you >>>> configure the CMake/Clang combo for cross-compiling. >>> I beg to differ, and it is quite related to using MinGW-w64. It's just not >>> about GCC. >>> >>> Currently, Clang as-is cannot cross-compile to the MinGW-w64 targets. >> Clang is not under the control of MinGW-w64. Nor this project >> distributes Clang binaries with any promise of support. So if Clang has >> a problem targeting MinGW-w64, that's something to discuss on the Clang >> lists. > As a project, mingw-w64 wishes to have clang and llvm supported. There > have been recent reports of troubles with it however but we'd prefer it > to work. > >> OTOH if CMake invokes Clang without the desired options and switches, it >> is a problem with how CMake is used. > On the other side, the llvm project needs to do a bit of work too or at > least to state they want to support mingw-w64 and are ready to at least > try to not break its support. > >> Don't get me wrong, I'm not upset for this question being posted here. >> It's just that by asking it on clang-users or cmake-users the OP would >> get more chances of getting help. > I think the discussion is relevant but at least some troubles seem to > come from clang so the issue is worth raising there too imho. > ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
