Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build fix for OS X 10.9 #62

Closed
wants to merge 1 commit into from

Conversation

robertknight
Copy link

OS X 10.9 uses libc++ by default and there are several build
issues with Qt 4.8.2 (and possibly later Qt 4.x versions, I haven't
tested)

This commit changes the C++ lib to libstdc++ on Mac.

I'm not sure that this is the right way to go about setting the C++ library to libstdc++ or even whether that is the right thing to do. Would it be better to require a later version of Qt with the libc++ issues fixed instead?

OS X 10.9 uses libc++ by default and there are several build
issues with Qt 4.8.2 (and possibly later Qt 4.x versions, I haven't
tested)

This commit changes the C++ lib to libstdc++
@yuyichao
Copy link

I'm not sure about Mac but at least clang(3.4) + libc++(3.3) + Qt (4.8.5/5.1.1) has no problem on Arch Linux. (I do have problem, however, when compiling with clang(3.4) + libstdc++(gcc4.8.2) in c++0x mode).
The bug report you are pointing to says the problem affects both Linux and Mac and is fixed in 4.8.2 and 5.0.0.

@krf
Copy link
Contributor

krf commented Oct 31, 2013

This is a Qt bug, and has been fixed in Qt already. Personally, I don't think we should do anything fancy here to work around an issue in an out-of-date Qt version.

@krf
Copy link
Contributor

krf commented Nov 27, 2013

Closing. Please reopen if you think there's still a problem in up-to-date Qt versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants