is windows-mingw_64-clang valid for ABI?

[Jack]

Hannah,

Thanks for the response.  Given that info, perhaps there should be a  
note someplace about how to set it up.  The .ini sample file just lists  
gcc and clang as equivalent.  Also perhaps some comment or note  
somewhere on the implications of changing the ABI value mid-stream.  I  
know it only affects installs after it changes, but am I correct that  
different pieces compiled with either clang of gcc should still work OK  
together?

Also - given the so much of KDE depends on Qt, how far would I get  
trying to use mingw clang?  Or is it just that the Qt stuff itself  
should be compiled with gcc, and then frameworks and applications can  
use clang?

Jack

On 2018.05.29 09:18, Hannah von Reth wrote:
> Hi,
> 
> Yes when using clan, craft is expecting clang to be available.
> 
> Be warned that Qt currently doesn't support mingw clang.
> 
> To use clang I'd recommend to set the compiler to mingw-gcc, craft  
> clang
> and then change the compiler to mingw-clang.
> 
> 
> Cheers,
> 
> Hannah
> 
> 
> On 28/05/2018 15:39, Jack wrote:
> > Hi Thomas,
> >
> > On 2018.05.28 03:11, Thomas Friedrichsmeier wrote:
> >> On Sat, 26 May 2018 19:37:23 -0400
> >> Jack Ostroff <ostroffjh at users.sourceforge.net> wrote:
> >>> The craftsettings.ini example file seems to say that
> >>> windows-mingw_64-clang should be valid for ABI, but "craft ninja"
> >>> fails with "'clang' is not recognized as an internal or external
> >>> command, operable program or batch file.
> >>
> >> [...]
> >>
> >>> The only packages installed so far are cacert,  
> craft-blueprint-kde,
> >>> craft-core, 7zip, craft-startment-entry, git, mingw-w64, shimgen,
> >>> wget, and runtime.
> >>
> >> you will have to install clang. *In theory*
> >>   craft clang
> >> should be all you need. Right now, mingw is the only compiler to be
> >> installed automatically by craft, as far as I am aware.
> > Thanks for the info/suggestions,
> >
> > If this is the case, then there really should be some instructions
> > somewhere in the docs.  The default .ini file includes both craft  
> and
> > gcc as equal options.
> >
> > By the way - "craft clang" fails in the same way - probably because  
> it
> > is trying to install it using clang....  I'm wondering if I need to
> > start with -gcc, then install clang, and then switch ABI back to
> > clang.  I've already switched my install to gcc, so I'll have to  
> wait
> > until I have time to start in a separate instance to try this.  I
> > guess it is because the base mingw install includes gcc, and not  
> clang.
> >
> > Jack
> 
>