Re: [Interest] configuring qt from cmake fails

2016-12-16 Thread Fabian Wein
>>> You have to pass -stdlib=libc++. > add_compile_options(-stdlib=libc++) We solved it by adding the flags via a PV macro, by a quick search I could not dig deep enough to verify if it ended up with add_compile_options() but it might be. Anyway, it works. Thanks for your help Fabian

Re: [Interest] configuring qt from cmake fails

2016-12-15 Thread Samuel Gaist
> On 15 Dec 2016, at 20:15, Fabian Wein wrote: > >>> So patching qt such that the options „-headerpad_max_install_names >>> -stdlib=libc++“ are used for linking would be just fine for me. >> >> You have to pass -stdlib=libc++. > > I know this, but how? > Hi,

Re: [Interest] configuring qt from cmake fails

2016-12-15 Thread Thiago Macieira
Em quinta-feira, 15 de dezembro de 2016, às 16:41:06 PST, Fabian Wein escreveu: > I examined both builds via configure -verbose and export VERBOSE=1 and while > vanilla qt links with clang++ -headerpad_max_install_names -stdlib=libc++ > -Wl,-syslibroot … > > the first two options

[Interest] configuring qt from cmake fails

2016-12-15 Thread Fabian Wein
Hello to the list, I want to build Paraview (PV) which builds qt by itself by myself. The project is called paraview-superbuild. On macOS 10.12 (Sierra) I have an issue with qt 5.7.1 but it seems this also applies to other qt versions. PV builds qt as external cmake project but building qt