On Fri, Oct 21, 2016 at 10:31:00 -0400, David Thompson wrote:
> Your attempt to set CMAKE_OSX_SDK=10.12 was probably on the superbuild
> project, and it is not passed to the Qt subproject as QT_MAC_SDK. Try
> passing the proper value to CMAKE_OSX_SDK (i.e., the full path which
> is usually
>
Hi David,
you are right, I apply the cmake option for superbuild. This was my first
attempt. With an additional -verbose on configure I get
Running configuration tests…
Failed to process makespec for platform ‚macx-clang‘
Info: creating stash file
Hi folks,
Great discussion.
Might I suggest creating an issue in the ParaView issue tracker (
https://gitlab.kitware.com/paraview/paraview/issues) to track progress on
building Qt on Mac OS X 10.12 and continuing discussion there? I'd like to
reserve this email thread for issues specific to
Hi Fabian,
Your attempt to set CMAKE_OSX_SDK=10.12 was probably on the superbuild project,
and it is not passed to the Qt subproject as QT_MAC_SDK. Try passing the proper
value to CMAKE_OSX_SDK (i.e., the full path which is usually
But your guess was right:
xcodebuild -showsdks
iOS SDKs:
iOS 10.0-sdk iphoneos10.0
iOS Simulator SDKs:
Simulator - iOS 10.0-sdk iphonesimulator10.0
macOS SDKs:
macOS 10.12 -sdk macosx10.12
tvOS SDKs:
tvOS
Did not work:
-DCMAKE_OSX_SDK=macosx10.12
in cmake ../paraview-superbuild -DENABLE_cxx11=ON -DENABLE_hdf5=ON
-DENABLE_qt5=ON -Dsuperbuild_download_location=~/tmp/pvsb_downloads
-DCMAKE_OSX_ARCHITECTURES=x86_64 -DCMAKE_OSX_DEPLOYMENT_TARGET=10.12
Hi Fabian,
CMAKE_OSX_SDK needs to be something like `macosx10.9`. I forget the
command to make XCode list the valid sdk versions available. For your case
I would guess `macosx10.12` is the correct value. Qt looks up the path to
the SDK from that string.
HTH,
Shawn
On Fri, Oct 21, 2016 at
Maybe they mean:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk
or what ever version of macOS works for 10.12?
--
Mike Jackson [mike.jack...@bluequartz.net]
Fabian Wein wrote:
I added a lot of the stuff to the issue tracker.
I’m
On Thu, Oct 20, 2016 at 15:13:51 +0300, Gena Bug via ParaView wrote:
> Now, with RC2, fontconfig warns me about blank section:
>
> Fontconfig warning: line 160: blank doesn't take any effect anymore.
> please remove it from your fonts.conf
We're now using a newer fontconfig, so the fontconfig
On Thu, Oct 20, 2016 at 16:03:05 +0200, Fabian Wein wrote:
> Are you interested in superbuild tests, too? Or do you want to skip
> that issue for the time 5.2 is released?
We're interested :) .
> On macOS 10.12 Sierra I have problems building qt5:
Hmm, we haven't done 10.12 yet; upgrading it
Are you interested in superbuild tests, too? Or do you want to skip that issue
for the time 5.2 is released?
On macOS 10.12 Sierra I have problems building qt5:
superbuild fails with the output below but building qt5 manually seems to work
(at least it builds for a longer time up to now)
On
Hi!
Now, with RC2, fontconfig warns me about blank section:
Fontconfig warning: line 160: blank doesn't take any effect anymore.
please remove it from your fonts.conf
However, that all -- no more new folder "fontconfig" in the running
directory. Thank you, that was really annoying!
Also,
On behalf of the ParaView development team, I am happy to announce that
ParaView 5.2 Release Candidate 2 binaries and source tarballs are now
available for download at
http://www.paraview.org/download/
Please let us know if you encounter any problems with this release
candidate.
Thanks,
Cory
13 matches
Mail list logo
